Flutter & React Native Apps in Singapore

About Flutter & React Native Apps

Our React Native and Flutter development services take a cross-platform iOS and Android app from first screen to store release. We use Flutter when polish and 60fps animations matter, and React Native when speed-to-market and shared code with the web matter more. From MVP launches to enterprise apps with 100k+ users, we handle the full lifecycle: design, native module integration, App Store and Play Store submission, push notifications, analytics, and ongoing version updates.

What the engagement includes

• Flutter app development (iOS + Android)
• React Native app development (iOS + Android)
• Native module development for platform-specific features
• Push notifications (FCM, APNS, OneSignal, Firebase)
• In-app purchases and subscription billing (RevenueCat, native IAP)
• Real-time features via WebSockets or Firebase
• Offline-first apps with sync (SQLite, WatermelonDB, Realm)
• Maps and location services (Google Maps, Apple Maps, Mapbox)

Platform worker rules and HSA's software device rules in a Singapore cross-platform app

Ride-hail and delivery are the classic cross-platform build here, a customer app and a worker app sharing one codebase over a dispatch backend, and since 1 January 2025 the Platform Workers Act has turned some of that backend's design choices into legal ones. Whether the people doing the work are platform workers, with the protections that follow, turns on management control, and MOM's test has two limbs that must both be met. The first is that the operator uses data from workers and service users in an automated way to decide whether a worker may provide the service, which tasks they may perform, or how much they are paid for a task. The second is that it imposes requirements, prohibitions or restrictions not required by law: rules on when, how or to what standard the service is delivered, stopping workers from negotiating fees with customers or building their own client base, controlling their working hours or the number of tasks they take, or performance-based incentives and penalties. Read as a product specification, that list is the dispatch algorithm, dynamic per-task pay, acceptance-rate thresholds, rating-based penalties and the in-app rule that a rider may not take a customer's number. Few platforms here could drop all of those and still work, so most should plan on being in scope, and a decision to add one of those controls is also a decision about classification, which is cheaper to take while the feature is a ticket than after it ships. An entity that becomes a platform operator has to notify MOM within 14 days. Operators must also provide work injury compensation insurance for their platform workers and file an injury report within 10 days, and that report draws on job records and earnings data, so the task log, the earnings and the time and place of each job need to be retrievable from the backend rather than reconstructed from a worker's phone. Whether your service meets both limbs is for your own counsel.

The money is where the worker app changes most. Operators deduct the worker's CPF contribution from earnings as and when they are earned and pay it to the CPF Board every month together with the operator's own share, compulsorily for workers born on or after 1 January 1995 and for older workers who choose to opt in, with rates rising in steps towards employee and employer levels by 2028. So every payout is computed per task with a CPF line inside it, the date of birth and the opt-in election sit on the worker record as inputs to that calculation rather than as profile decoration, and the earnings screen shows gross, deductions, CPF and net instead of a single figure. Since 1 January 2025 operators have also had to issue earnings slips, in soft or hard copy, no later than two months after the task, or after the earliest task where one slip covers several. Each slip carries the worker's name, date of birth and NRIC number, the earnings period, the gross amount, deductions, CPF contributions, the net amount and the slip date, together with the operator's name and a statement that it is an earnings slip for a platform worker, and the same items are kept as records for two years, and for two years after a former worker's last task. In a cross-platform build the slip is generated once on the server as a document both apps display and download, rather than rendered separately on each platform, so the figure a worker sees on Android and the one on iOS cannot disagree. Because the Act makes the NRIC number a required record, it is stored in its own encrypted field, appears on the slip because it has to, and is never used to sign the worker in. Rate tables change on a published schedule, so they are configuration with effective dates rather than constants in the app. Which workers and payments fall in scope is for your accountant and counsel.

If the app measures, monitors or advises on a patient's health, settle early whether it is a medical device, because the Health Sciences Authority's guidelines for software medical devices, revised in December 2025, list mobile applications that remotely monitor a patient's vital signs among their examples, and three of their requirements bear directly on how cross-platform apps ship. The first is versioning. Software supplied without a physical form has to show its registered Singapore version in the user interface. A Dart patch through Shorebird or a JavaScript bundle through EAS Update changes the running software without changing the version number the store shows, so the version on the about screen is computed from the binary and the patch together, and a patch that touches a diagnostic or therapeutic function goes through HSA's change notification guidance, GN-21, rather than straight to phones. The second is the operating system. HSA's change flowchart asks whether a change moves the software to a different operating system from the registered version, which makes shipping the Android build of an app first registered on iOS a regulatory step to check rather than a routine store release. The third is end of support. Software running on an operating system that has lost vendor support, with cyber risks that cannot be adequately mitigated, will not be permitted for supply in Singapore, and labelling must state the operating system requirements and must not recommend unsupported versions. The frameworks move that floor themselves: as of Flutter 3.47, iOS 14 and Android API 23 and earlier are unsupported, so a framework upgrade can change what the labelling has to say. For a team that ships often, HSA's Change Management Program for software as a medical device lets pre-specified changes approved in advance be made under your own quality system, with a declaration due within a year of approval and annually after. Classification and registration are for your regulatory adviser.

How we work with Singapore clients

Singapore is the one market we serve where the working day is simply shared. We are two and a half hours behind you and neither country moves its clocks, so our morning starts partway through yours and the whole of your afternoon is live time for both sides. That changes the shape of an engagement more than anything technical does: a call is booked for the same afternoon rather than the same week, a question raised before your lunch is answered after it, and the written-first method we run for North American clients is a courtesy here rather than a necessity. We keep the written record anyway, with a default chosen on every open decision, because it is the thing an auditor or a new hire can read later and a call is not.

Invoicing is worth stating plainly because the GST position confuses buyers on both sides. We are outside Singapore, so no GST appears on our invoice. Whether you account for it yourself is the reverse charge question, and IRAS's own guidance is that a GST-registered business making only taxable supplies is not affected, while a partially exempt one accounts for it in its own return. We quote in Singapore dollars, the figure holds for the project whatever the rupee does, and payment by bank transfer or Wise avoids the card fees a five-figure invoice does not need. The contract can sit under Singapore law with Singapore courts, and unusually among our overseas markets that clause has teeth: Singapore is a reciprocating territory under section 44A of India's Civil Procedure Code, so a judgment of the Singapore High Court can be executed in India directly rather than re-litigated.

Indicative pricing in SGD

Converted from our published Indian rates and rounded. Exchange rates move, so the figure on your quote is calculated on the day it is issued.

Questions Singapore clients ask

Flutter & React Native Apps: common questions

Other markets we work in