Mobile App Development in Singapore

No GST is charged on our invoice, and the invoice says so. Whether you account for it under reverse charge depends on your input tax position: IRAS's guidance is that a GST-registered business making only taxable supplies is not impacted, a partially exempt business or one with non-business receipts accounts for GST on imported services in its own return, and a business that is not registered should ask its accountant, because an exempt business importing more than S$1 million of services in a year can be required to register. We would rather your accountant confirmed your position before the first invoice than reconciled it at year end.

We build to it rather than claiming a certificate. The consent, purpose limitation and notification obligations shape the forms and the data model; retention limitation means records are deleted on a schedule rather than kept indefinitely; access and correction requests are features with a queue behind them rather than a manual database job. Processing happens in India, so the transfer limitation obligation applies, and the processor agreement we sign sets out the comparable standard of protection the Act asks for. The obligation to design for early is breach notification: an organisation has three calendar days from determining a breach is notifiable, which means one likely to cause significant harm or one affecting 500 or more people, to tell the PDPC, and answering what was in the breach is only possible if the logging existed beforehand. Appointing a Data Protection Officer is your obligation rather than ours, and we will say so if a design choice would make that person's job harder.

Not PSG. The Productivity Solutions Grant funds pre-scoped packages from pre-approved vendors for Singapore-registered companies, and a custom build from an overseas team is not that shape, so we will not pretend it is. The Enterprise Development Grant is assessed project by project against its own criteria, and whether a build like yours qualifies is a question for Enterprise Singapore or your grant consultant to answer before the scope is written rather than after a budget has assumed it.

We can supply what a due-diligence pack asks for, accept audit and access rights in the contract, and name every sub-processor that touches your data. What we will also tell you in the first conversation is what we do not hold: we are not SOC 2 or ISO 27001 certified, and our security page says so in those words. Whether an engagement with us is a material outsourcing arrangement under the MAS guidelines, and what that requires of you, is your compliance team's determination, and it changes the contract before it changes the code, so it belongs in week one.

Flutter if your UI is custom and you want it to look and behave identically on iOS and Android from one codebase; it is what we used for both Jai Shri Balaji apps. React Native if you already have a React web team or depend on JavaScript libraries, because the skills and some code transfer. For most first apps we lean Flutter. On our call we pick based on your team and your UI, not a house preference.

We build cross-platform in Flutter or React Native, which compile to real native iOS and Android apps from a single codebase. For the vast majority of business apps that is the right call: one team, one codebase, both platforms, lower cost. We are not the right studio if you specifically need fully separate Swift and Kotlin native codebases or a heavy native game engine.

Yes, end to end. That includes developer account setup if you do not have one, app signing, store listings, screenshots, privacy and data-safety declarations, and the review back-and-forth with Apple and Google. First submissions often get bounced for small reasons, and we handle that so your launch does not slip.

A flat quote against a written scope, never an hourly meter. Send us the brief, we write the scope, and you get back one flat INR number, with the exact figure inside 24 hours. If you have a foreign parent company, we can invoice that entity in USD. What moves the number is how many screens, integrations, and platforms you actually need, not a clock.

It depends on the build, so the real timeline goes in the written scope rather than a stock number here. We work in short sprints with a working build at the end of each, so you see progress the whole way instead of waiting months for a big reveal. The backend and the integrations, not the number of screens, are what move a timeline most.