Does the name Itty Bitty Apps ring a bell? No? What about Reveal? Itty Bitty Apps is the company behind Reveal. Reveal is a powerful view debugger for iOS and tvOS development. It’s Xcode’s built-in view debugger on steroids. It comes with a gorgeous user interface, powerful controls, and support of iOS, tvOS, and application extensions. It’s a must-have for every Apple developer. Earlier this year, I sat down with Sean Woodhouse, CEO of Itty Bitty Apps, to talk about software development, running a software business, and building developer tools for the Mac platform.
Every now and then, I take some time out of my day to explore something about the Swift language that I don’t yet. There’s a lot left to explore. I document my findings in a series I named “What The Swift”. If you’re curious about the more subtle details of the Swift language, then this series is for you.
A few weeks ago, I got in touch with Tobias Günther, CEO of Fournova. Fournova is best known for Tower, one of the best Git clients for macOS and Windows. The company has been around for more than a decade and it seems to be doing well. I wanted to ask Tobias a few questions about running a software business in today’s economy.
Last year, I wrote about the difference between private and fileprivate in Swift 3. With the impending release of Swift 4, it’s time for an update. Access control underwent several important changes since the introduction of the Swift language, several years ago.
This is the third and last installment of a series that teaches you how to mock and stub system classes in Swift. In this tutorial, we unit test the AddLocationViewViewModel class.
Remember from the previous installment of this series that our goal is to mock the Core Location framework and stub the responses of any geocoding requests we send to Apple’s location services. This is necessary if we want to create a fast and reliable test suite. Being in control of the test environment is key if your goal is creating a robust test suite.
Speed and reliability are key elements of a robust test suite. But for a test suite to be fast and reliable, you need to be in control of the environment in which the test suite is run. You don’t want to write a unit test that depends on the response of an API request. Right? For such a unit test to be fast and reliable, the API your application interacts with needs to be mocked and its response stubbed.
Last week, I wrote about weak and strong outlets. But there’s another question about outlets that comes up frequently. Should outlets be declared as optionals or implicitly unwrapped optionals? This tutorial zooms in on the pros and cons of each of these options.
Running a successful software company has always fascinated me. To run a thriving business selling software, you need more than a solid understanding of software development. A few weeks ago, I got in touch with Peter Krajcik from PixelCut to talk about running a software company focused on the Apple ecosystem. While the name may not sound familiar, you may be familiar with PaintCode, PixelCut’s flagship product.
If you’re reading this, then I assume you are new to Core Data. You may have heard about Core Data and you’d like to find out whether it’s a good fit for you or the project you’re working on. If this description fits you, then take a seat. This Core Data tutorial teaches you everything you need to know to better understand what Core Data is and isn’t.