1. Before you write a line of code do your research. Find some of the people who you think will use the app and talk to them to make sure your app idea is one that solves their most important problems.
2. Keep it simple. Think of the simplest version of the product that you can build and launch that meets the biggest needs of your users. This is often called a Minimum Viable Product (MVP).
3. Developing an app is not about a perfect 1.0 version. It's a continual process of shipping, listening to customers, adding the next most important feature, and then releasing an update. To support this, make it really easy for customers to send you feedback.
4. If you choose to hire an iOS development firm, make sure you communicate with the developer on a daily basis on progress. Prioritize all of the things that need to get done, communicate these priorities clearly to the developer, and make sure they get properly finished before moving on to the next item in the list.
TIP: See the top iOS Developers, ranked by real people that have used their services.
5. Don't forget to market your app. ‘If you build it, they will come’ is not a viable strategy. Think about how you are going to tell people about your product long before you launch.
6. Build a great app. The standard on iOS is very high. Users have high expectations of easy-to-use apps with attention to detail in the design and interactions. Apple makes this easy to do if you follow their guidelines and use their frameworks.
- David Brittain, Co-founder of TopHatch, Developer of Concepts
7. Apple also does a much more rigorous quality control than Google Play for Android app development. Accordingly, I would recommend thoroughly testing your new app before submitting it to Apple for the app store. This includes testing on a variety of devices such as the iPhone and iPad.
8. Learn various methods for making their code more efficient, like object pooling or compressing graphics or sound. Try not to use more CPU or memory than absolutely necessary. Nothing is worse for a new user of your app than having the app crash or act sluggish.
9.Be aware of intellectual property, regardless of whether they are developing for iOS or Android. Be aware of how to license images, music, and sound effects for your app.
10. Make use of storyboarding. This is a great way for developers to gain an understanding of how the transitions between various screens will work. Storyboarding also allows developers to realize what goals they want the app to achieve.
11. Understand the fundamentals. Take the time to dive into the algorithms, data structures, inheritance, and polymorphism. Software fundamentals carry over from platform to platform, language to language, library to library.
12. Learn the hotkeys. No matter what tool you use, once you start using it, you are going to save so much time. Everything has shortcuts, including XCode.
13. Cocoapods is your friend. Cocoapods is a great package manager for iOS that allows you to plug existing libraries to extend your app. Most of the pods even come with an example. (Apparently, it’s everyone’s friend because it’s rated 4.4 stars out of 5 on G2!)
23. Beginner coders who apply what they learn in small-scale iOS projects are the most successful learners. Don't try to build the next Facebook app as a first project, though!
24. Should you learn Swift or Objective-C? I recommend new coders to learn Swift, because it's easier and more intuitive compared to Objective-C.
25. It's smart to start with fundamental iOS development topics, such as variables, functions, object-oriented programming, arrays, and dictionaries.
26. A great first project is building a Contact Info app, with a table view controller and detail view controller that has more information. If you spend an hour a day, or a few hours a week, and if you're having fun – you'll master iOS development in no time.
27. If you’re building an app that you plan to bring to market for your product or service, avoid third-party libraries like the plague. While they may save time in the development stage, it will cost you later when your app or feature stops working because the library changed or is no longer supported for the latest hardware or software update.
Bridget Poetker is a former content team lead at G2. Born and raised in Chicagoland, she graduated from U of I. In her free time, you'll find Bridget in the bleachers at Wrigley Field or posted up at the nearest rooftop patio. (she/her/hers)