Architecting applications to meet today’s challenges and be ready for tomorrow’s problem is not an easy feat. The principles of clean architecture may be sound, but separating the signal from the noise is tough. Here is a sample VIPER project for iOS that you can tinker to learn about the principles of clean architecture.
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.
Make thousands of unique 64 bit identifiers at every millisecond without the need of global synchronization.
Have you been asked to do a sample project as part of a hiring process? I’ve done it, not only once but **twice** as part of the same process. Here are those projects. You should be able to learn a thing or two from it Either learn the iOS programming techniques behind these two 40-hour projects or learn how to hunt for purple squirrels.
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.
Today I have just made the world a slightly better place. Better for Mac developers, that is. That’s because I have made an open-source Google Reader library for Cocoa. You can download the library from Github: GReader-Cocoa and hopefully you’ll like it enough to contribute patches. Why yet another Google API library? Two reasons why,…