The data persistence stack that is an appropriate decision today may not be an optimal solution when your app has grown. You would need to design your app to withstand the test of time and be extensible for as it grows. Read more to learn how.
Choosing a database to use for your iOS app is no simple feat. But what if you have the tools to make an informed decision for your app? What if you can decide for today and design for tomorrow?
Programming Cocoa apps with Swift has it’s many caveats. Many of these are derived from the fact that there are two language runtimes at play, the incumbent Objective-C runtime which is used by system frameworks and the Swift runtime as a newcomer. Here is one hard lesson learned (and workaround) when dealing with state restoration problems in a Swift app.
Futures/promises are great to coordinate persistence and views to ensure responsiveness in today’s native apps. However bringing thousands of lines of foreign code just to have this small functionality may not be cool. Here’s a hundred-line implementation of futures/promises in Swift 3.1
It’s high time you update your macOS app to support the Touch Bar. You’ll need to have some strategy on how to design your Touch Bar interface – don’t just pour any buttons into it. Here’s some tips on how to work this new hardware.
Here is a document class replacement for managing your library-style app based on Core Data. All the goodness of NSDocument / UIDocument with just the right functionalities when you don’t need to expose document-management functionality to your users.
If your users needs a precomposed e-mail with attachments, now you can easily do it on the Mac with a few lines of code
How to share common code between OS X and iOS and architect your app to dance around each platform’s similarities and differences.
Supporting state restoration in iOS often requires you to make your app just like a hollywood house where the front porch looks nice but there’s really nothing beyond that. Read more to find out why.
Are you yearning for Flurry Analytics or Google Mobile Analytics for your Mac OS X application? Seek no more as your day is saved!
Do you know why it’s so hard to gain access to an SQL database from a Mac App? Here’s why and the solution to your database access woes. Warning: it’s slightly off-beat and rad.
Is your Cocoa app plagued by “unrecognized selector sent to instance” exceptions when consuming JSON data? Is your app not resilient to minor server-side JSON API changes? Here’s how to fix your JSON woes in your Objective-C project.
Cocoa stores cookies on its own and this makes it hard to implement a web client that appears as more than one user at the same time to the web server. To do this you’ll need to make your own cookie storage and this article teaches you how.