Now that you know what your mobile application will do and look like, it’s time to get your various environments set up. Here’s our list of things we check off at Collective Idea for creating an iOS app.
Developing a mobile application that works on both iOS and Android takes a bit of work. Here are some best practices to get you going.
Realm is a good alternative to CoreData for your iOS apps. Setting up properties to be stored in the database is as simple as defining them in a model. But what about those properties that you don’t want persisted?
Databases don’t come with complex field types like an image. That doesn’t mean we can’t store them in our database anyway.
A few months ago, we built an iOS App for Dead Man’s Snitch. The drive behind making it a native application was to take advantage of the Apple Push Notification System. When the App went live to our customers via the App Store it quickly became clear that we were missing notifications sent from Dead Man’s Snitch.
One of the hurdles you have to overcome when building an app like Downside is how to handle network messages. Apple provides several different ways of adding networking to your apps including GameKit and the new Multipeer Connectivity framework in iOS 7. Each of them require you either send or receive an NSData blob.
Sure, making apps that communicate with a server somewhere is interesting, but what about your creative side?
One eventuality in the mobile development space is that you will, at some point, find yourself in need of a backend service for your app. In this blog post, I go over how to use Parse.com as your backend service.
Last week HipByte released RubyMotion and although I was originally skeptical, I’ve grown to really like it.
Adding named parameters to the CoffeeScript router
Refactoring your code is for more then keeping it DRY. It also gives you a chance to make it more efficient.
Using Stripe to take credit cards online.