AllFrameworks.net has been in touch with a group of app developers based in Copenhagen, they’ve shared some of their insights to help guide fledgling developers or startups on their journey towards a successful app.
Nodes has developed apps for prominent clients such as Samsung, Adidas, LEGO, Unilever and BMW, as well as startups and smaller businesses, so they’ve experienced most of the common issues one can run into when publishing an app in the App Store. We think any first time app developer would benefit from having a quick read through of the following points, and Nodes themselves make sure to have all these issues checked ourselves before submitting any app on behalf of their clients.
From Daniel Baek, Co-founder of Nodes, a mobile app agency located in Denmark and the United Kingdom.
- Consider the monetization model from the very start, so that the development process will not have to change drastically while the project is underway.
- Aim for an early MVP (Minimum Viable Product) from the get go, and use that to iterate further development and upgrades, compared to building the ideal dream app and wait to launch it until you feel it is 100% ready.
- Ensure that the steering group is given a mandate to make decisions and won’t be slowed down by too many internal stakeholders and departments.
- It’s important that people working sedentary jobs get up and move about.
From Casper Rasmussen, Partner at Nodes
- In most cases hybrid app development frameworks aren’t the right way to go (we use it for some projects) as the cost of creating an just as exciting user experience will require as much time in the end as taking the native route from the start.
- Use open-source applications and packages for all standard tasks and processes.
- Use paid services for more complex part of the projects (payment, push etc) as opposed to developing them as part of the projects yourself
- Stick to standard UI elements, and use themes to develop brand identity.
- Always keep in mind Apple and Android Guide Lines before starting a project to ensure a low rejection possibility
Submitting an app to Google Play or Apple’s App Store
Since it can take anywhere from a few days to a few months to have a new app reviewed and approved in both Google’s Play Store, and Apple’s App Store, it is important to make sure all things are set-up correctly in the first attempt, since it can cost any startup or company valuable time if the app happens to get rejected the first time.
- Lacking app meta-data This is a simple fix, but surprisingly, one of the most common issues we’ve seen with regards to app store rejections. The meta-data should always be double checked for containing correct information and no broken links, since the moderators in the App Store are particularly keen on having correct meta-data.
- Don’t ask for specific personal information that is not needed Many times, we’ve seen our customers wanting to collect a wide array of user data for their analysis and marketing purposes, but if the app is not using these data for anything particular, odds are your app will be rejected due to collecting information not related to core functionality of the app.
There are other important issues, but we estimate that more than 80% of the apps we’ve dealt with that’s been rejected has been to one of these three.
Here’s some more things to check before publishing an app.
- Missing demo accounts
- Major bugs in the app
- The Concept or Functionality of the app is against Apple guidelines
- The app configuration (.plist) file not specifying correct background functionality
- Make sure your video preview sticks to functionality only
- Dummy data still in the app
- Moderating user-generated content
If you’ve still got time and energy for reading more about app development tips and tricks, perhaps you’ll enjoy this article about the latest mobile app trends for 2016. Otherwise, feel free to leave your comment, both positive and negative, we strive to provide useful content that our readers and users can benefit from!