Mobile App Development in the US

About Mobile App Development

We build cross-platform apps in Flutter and React Native, wire up the backend, push, and offline sync, and hand them to the App Store and Play Console for you. A senior team in Noida, flat quotes, and a written scope before any code.

What the engagement includes

• Senior engineers on your app from day one. No junior offshore team behind an account manager, no handoff after you sign.
• Direct access to the people writing the code. You talk to the developer, not a layer that relays your questions and loses half of them.
• Both app stores handled end to end, including signing, listings, and the review process, so you are not learning Play Console under deadline.
• Flat INR quotes against a written scope, turned around in 24 hours. We can invoice in USD to a foreign parent entity if you need that.
• 70 plus projects shipped for clients in India, the USA, Canada, the UK, and the UAE, so this is not our first launch.
• Honest scoping. If you need one app and not three, or a web app instead of a native one, we will tell you before you spend.

Purchase links, store age signals and COPPA in a US mobile app

On the US storefronts the in-app purchase question is now two separate rules, and both are still moving. Apple's App Review Guidelines exempt the United States storefront from the ban on buttons, external links and other calls to action that send a customer to buy outside in-app purchase, following Epic v. Apple. On 11 December 2025 the Ninth Circuit upheld the contempt finding against Apple, held that developers may use real buttons as well as links, and said Apple may stop a developer's call to action only from being more prominent in font, size or placement than Apple's own. It said Apple should eventually be allowed a commission on linked-out purchases limited to its genuine costs and some return on its intellectual property, but that none should apply until the district court approves one. Apple has since proposed a rate on remand, and on 30 June the Supreme Court agreed to hear its challenge to the contempt finding, so the number is open. Google Play has allowed alternative billing and external links for US users since 29 October 2025, through its own programmes: links go through the external content links APIs, which show an information screen, must be limited to users in the US and its territories, and carry transaction reporting and service fees from 1 October 2026. So we build the web checkout, one server that grants the entitlement from either path, and a storefront check that decides which buttons appear, with fee assumptions kept in configuration rather than code. Your obligations under each programme are for your own counsel.

The stores now also pass a user's age and a parent's consent to your app, and state law makes acting on that the developer's job. Texas SB 2420 requires a developer to give the app, and each purchase inside it, an age rating, to tell the store before a significant change such as new data collection or new monetization, and to run a system that uses the store's data to confirm each user's age category and, for a minor, that a parent consented. The personal data the store sends may be used only for those purposes and has to be deleted once verification is complete, so it cannot quietly become a profile field. The law was due on 1 January 2026 and was enjoined in December 2025; the Fifth Circuit then stayed that injunction, and on 6 July 2026 the Supreme Court declined to reinstate it while the appeal continues. Apple has applied the requirements to new Texas accounts since 4 June 2026, alongside Utah from 6 May 2026 and Louisiana from 1 July 2026. On iOS the work is the Declared Age Range API, the Significant Change API in PermissionKit, the new age rating property in StoreKit and a server notification for when a parent revokes consent; on Android it is the Play Age Signals API. The design questions are what a 13 to 15 year old sees when a parent says no, and which updates count as significant, which Apple leaves to the developer. Which of these state laws bind you is for your own counsel.

If any of those signals can come back as under 13, or the app is aimed at children at all, the amended COPPA Rule applies, and its compliance date passed on 22 April 2026. In a mobile app it lands on the SDK list more than on the privacy policy. A parent must be able to consent to the app collecting and using a child's information without consenting to its disclosure to third parties, unless that disclosure is integral to the service, and the disclosure needs its own separate verifiable consent. So an advertising or attribution SDK that starts on first launch is the problem, and the app has to work with those SDKs switched off. The rule also bans keeping a child's information indefinitely, requires a written retention policy with a timeframe for deletion and a written security program, and now counts biometric identifiers such as voiceprints and faceprints as personal information, which reaches voice and camera features. Age checks sit awkwardly beside this, since verifying age means collecting data about someone who may be a child. The FTC's policy statement of 25 February 2026 says it will not bring a COPPA case over data collected solely to determine age, provided it is used only for that, deleted promptly and kept secure, which is the same shape as the Texas deletion rule, so one short-lived code path can serve both. Whether a store's under-13 signal gives you actual knowledge under COPPA, and what the app must do from that moment, is for your own counsel before the API ships.

How we work with US clients

A US engagement gets agreed twice. Once with the person who wants the thing built, and then again with legal, security, procurement and finance, who arrive separately and rarely in the same week. That second round is where a supplier outside the country loses the calendar: a master services agreement to redline, a security questionnaire, a certificate of insurance, and a vendor portal that assumes everyone it onboards can sign a W-9. Send all of it while the scope is still being written rather than in the week you wanted to start, and where the honest answer to a row is that we do not hold something, we write that in rather than leaving it blank.

You are also buying from a company you cannot drop in on, so the evidence has to do the work an office would otherwise do. What we send is live production URLs rather than a deck, a written scope with one fixed number against it, and the names of the people who will do the work rather than a bench that changes after signature. What we will also tell you is the shape of what you are hiring: a small team in Noida that has been building since 2021, not a firm that can put four more people on your project next Monday. If that is what your timeline needs, we say so before the contract rather than after it.

Questions US clients ask

Mobile App Development: common questions

Other markets we work in