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?
Make thousands of unique 64 bit identifiers at every millisecond without the need of global synchronization.
Deciding when to pre-populate a Core Data store is a real headache when you need to sync that data store across many devices. However you can learn from my experience and save you the headache that I had to went through.
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.
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.
Cocoa’s document architecture envisions that a window should only handle one document. However library-type applications may need one window to handle multiple documents so that the user can easily switch between libraries without restarting the application. Here’s how you can hack AppKit so that a single window handle multiple documents.
Core Data now officially supports concurrency and I/O in background threads since OS X 10.7 and iOS 5. In the same release, Apple also brought the document architecture to iOS that leverages this new capability of Core Data. However OS X didn’t get the same level of multicore love. In this post, I’ll show you how to create a multi-core supporting document architecture application for OS X.
The pervasive use of blocks and new nested context in iOS 5 and Mac OS X Lion paved the path to a whole new way of multithreading. Apple has lifted yet another barrier to use Core Data for applications that needs to run on multiple threads. This article teach you how to effectively write multi-threaded apps that uses Core Data as it’s backing store.
Core Data isn’t thread safe and Apple recommends to use multiple contexts instead to handle concurrency. However Apple seems to have forgotten that on Mac OS X, there are hooks like the undo manager that can cause havoc in multi-threaded Core Data applications, even each thread having its own context.