Part of the online course that I took from Stanford on iPhone app development involved choosing a final project. My top-level criteria for choosing a project included:
- Incorporate several different iOS technologies.
- Make use of an external web service and API.
- Interaction with an external web site.
What I eventually settled on was a concept for allowing a user to view and edit their iPhone Address Book contacts both within an app as well as in a full web browser.
This functionality is already available as a service now at iCloud.com. My plan was to start with this capability and over time begin to add new functionality (social sharing, etc).
The Contacts2Web app is now available in the App Store. In this document, I will cover some of the details that went into developing the app.
Posted in iOS
Tagged address book, code coverage, core data, core foundation, debugging, google analytics, instruments, iOS, leak, memory allocations, parse, singleton
I ran across a nice intro article to using assertions in iOS Working with Assertions to Debug your Apps. It describes the macros NSAssert, NSAssert1, NSAssert2, etc. and how to use them. One item mentioned in that article is different in XCode now – the macro NS_BLOCK_ASSERTIONS is defined by default for Release builds.
The article started me thinking about how one might report crashes and user-generated assertions in a production app. I came across the article Handling crashes and NSAssert gracefully in a Production App. Not only does it talk about how to continue using assertions in a Release build by subclassing NSAssertionHandler, but it also makes reference to using a service such as Flurry or Google Analytics to log them as well.
Web searches showed that Flurry and Google Analytics are both nice choices for getting app metrics and logging errors/exceptions. I spent some time looking through the Flurry web site and documentation and was impressed with what I saw. I found a nice article that talks about Flurry and includes a video on how to get started with it – Find errors in your iOS app before your users do!