codigeeks.com

Mobile app development in Singapore: the whole process

From brief to store release to upkeep: what building a mobile app in Singapore involves, which rules apply, and what to settle before work starts.

GuidePublished Updated

A mobile app is three things at once: software on a phone, an entry in someone else’s store, and usually a server that holds your data. Each comes with its own rules and its own running costs. This page walks through them in the order you meet them.

1. Decide what the app is for

Write down the one job a user opens the app to do, and how you will know it worked. That sentence decides almost everything later: which features are in the first release, whether you need accounts, payments or notifications, and how much the build costs.

Check early that an app is the right tool at all. Apple’s App Review Guidelines say an app should include features, content and UI that lift it beyond a repackaged website (guideline 4.2). If everything you plan would work as a web page, a website may serve you better.

2. Pick platforms and open the accounts

Many apps ship on both iOS and Android. Each store needs a developer account, and the account should be opened in your company’s name, not your developer’s:

The platform guides cover the details: iOS and Android.

3. Settle data protection before design

If the app collects names, phone numbers, locations or anything else about people, the Personal Data Protection Act applies. The PDPC lists the obligations: among them, telling people why you collect their data, getting consent, protecting the data, keeping it only as long as needed, designating a data protection officer, and notifying the PDPC and affected people of a significant breach. These shape screens and databases, so they are cheaper to design in than to bolt on.

4. Agree ownership in writing

Under Singapore law the author of a work generally owns its copyright, and IPOS notes this includes commissioned work, unless a written agreement says otherwise. Source code is a work. If you are paying for an app, the contract should say who owns the code, the designs and the store listings. The consultancy guide lists what else to put in writing.

5. Budget, and check grants against current rules

Cost depends on scope, platforms, back-end work and the developer’s rates; this cost guide explains what moves the number. On grants, note a 2026 change: GoBusiness states that PSG and EDG under Enterprise Singapore ceased on 29 September 2026 and that support now goes through the EDGE Grant. Check whether a specific solution is supported before relying on it.

6. Test with real people, then release

Both stores have test channels. Apple’s TestFlight lets you invite up to 10,000 external testers once the first build passes review. On Google Play, personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 days in a row before production access. Plan those two weeks into the schedule.

7. Keep it running

Apple and Google change their requirements every year, and an app that is not updated can drop out of reach of new users. Budget for upkeep from the start; the maintenance guide explains what that work is.