Skip to content
Estonia · Agentic mobile development

Mobile App Development for Users in Estonia

In September 2026, StatCounter put Android at 62.14% and iOS at 37.85% of the mobile operating system market in Estonia. Launching on either platform alone leaves at least a third of those users waiting, and two separate native codebases mean building most features twice. The other catch is legal rather than technical: consumer information has to be in Estonian unless the user agrees to another language, and the age at which a child can consent alone is 13, not the GDPR default of 16.

Curiosive builds from Ankara, Türkiye, with AI coding agents doing the volume under senior engineer review. Our mobile work is React Native, so one TypeScript codebase reaches the App Store and Google Play. Agents scaffold screens, navigation, list rendering, form validation, tests and first drafts of store metadata. Engineers own token storage in the iOS Keychain and Android Keystore, auth refresh, server-side entitlement checks, offline and reconnection behaviour, permission prompts and the privacy declarations that store review reads.

24
published portfolio projects
5+
years building for production
12
countries the work runs in
100%
of code read by a senior engineer
1 day
to hear back, from the engineer

Estonian language and consumer information inside the app

Estonian is the country's official EU language, and § 4(3) of the Consumer Protection Act requires information given to consumers, including pre-contractual information on a service's characteristics, conditions of use and contract, to be in Estonian unless the consumer has agreed to another language. For an app that sells subscriptions or goods to people there, the screens that matter most are the paywall, the terms screen, the order summary and anything describing what someone is about to buy. We set up the string catalogue from the first screen so the local language is a complete locale rather than a late patch. Agents wire strings into components and write tests that fail when a translation key is missing, while an engineer checks every screen where contract terms appear. Hard-coded English spread across a finished app is slower to unpick than a catalogue planned in the first week.

GDPR Article 8 sets 16 as the age from which a child's own consent makes processing lawful for information society services offered directly to children, and lets Member States go as low as 13. The country chose 13: under § 8 of its Personal Data Protection Act, where such a service relies on consent, a child's data may be processed only if the child is at least 13, and below that only to the extent the legal representative has consented. An app aimed at children that relies on consent therefore needs an age step, a parental route and reasonable efforts to verify it. Tracking is the second point. The Data Protection Inspectorate (Andmekaitse Inspektsioon) classes analytics and advertising cookies as additional cookies that need prior, voluntary consent, as easy to withdraw as to give. In an app, the cautious reading is to start analytics and advertising SDKs that store or read data on the device only after consent, with an engineer checking what each one sends.

Google Play and App Store release rules that apply to every build

With Android holding the larger share there, Google Play rules carry the most weight. Since 31 August 2026, new apps and updates must target Android 16 (API level 36) or higher, and every Play app must complete the Data safety form and keep it accurate, including apps that collect no user data. Play also requires both an in-app path and a web link for deleting an account and its data. Apple has required apps that support account creation to let users start account deletion inside the app since 30 June 2022, and temporary deactivation does not count. Apple's age ratings now include 13+, 16+ and 18+, with extra required questions for each app; a store rating is a label and does not replace the consent route under § 8. Agents draft the Data safety answers and store listings, and an engineer checks them against what the code and its SDKs actually collect, because a mismatch can lead to blocked updates or removal.

Payments and login in Estonia: Apple's EU terms and Smart-ID

Estonia has been an EU member since 1 May 2004, so Apple's EU terms apply to iOS apps there. Apple says that under those terms, effective 1 October 2026, iOS apps in the EU may offer alternative payment processing alongside In-App Purchase at a 20% commission, or 10% for program participants and for subscriptions after their first year. Apps can also be distributed through alternative app marketplaces or Web Distribution, subject to a 5% Core Technology Commission. Whether that beats In-App Purchase depends on your margins and how many of your users are on iPhone. Login is the other local question. On 5 October 2026, id.ee listed 797,320 Smart-ID users in the country, and the free app is used to log in to e-services, confirm transactions and bank transfers, and sign documents. If you offer it as a sign-in option, that integration stays with engineers alongside token handling and server-side entitlement checks, because a mistake there reaches users directly.

Questions

The things people ask before starting.

Should we build our app for Android or iPhone first in Estonia?

Usually both at once, with React Native. In September 2026 StatCounter put Android at 62.14% and iOS at 37.85% of the local mobile market, so either platform alone leaves a sizeable group out. One TypeScript codebase serves both stores, and coding agents take on most of the repeated screen work.

Does our app need to be in Estonian for consumers?

Yes, for consumer information, unless the consumer agrees to another language. § 4(3) of the Consumer Protection Act covers information about the service, its conditions of use and the contract, so the screens where people buy or accept terms need an Estonian version at launch rather than in a later update.

At what age can a child consent to an app in Estonia?

At 13, where the service is offered directly to children and relies on consent. That is below the GDPR default of 16. Under 13, the child's legal representative has to consent, so an app aimed at younger users needs an age step and a parental consent route. Check your own case with a lawyer before launch.

Can we work with a studio in Ankara on our app from Estonia?

Yes. Tallinn's clock is one hour behind Ankara in winter and level with it in summer, so the two working days overlap almost entirely. The work is remote by default, and every week ends with a releasable increment, so progress shows up as working software rather than a status report.

How it starts

What happens after you write to us.

  1. 01

    You describe the product

    One paragraph on what you are building, roughly when you need it, and who it is for. No brief, no form with fifteen fields.

  2. 02

    You get a reply within a day

    From the engineer who would do the work, not a sales team. If we are not the right fit we say so, and where possible we point you somewhere better.

  3. 03

    You get a scoped plan

    Scope, price and timeline in writing before anything is committed. You decide with the numbers in front of you.

No long contract to begin, no lock-in to our tooling, and the code is yours from the first commit.

Start a conversation
Contact

Looking for an engineering partner for the long haul?

A short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.

Ankara / Türkiye · Working across European and US time zones