Skip to content
Hungary · Agentic mobile development

Mobile App Development for Hungary's Android-First Users

In September 2026, StatCounter put Android at 72.69% of mobile operating system share in Hungary and iOS at 27.3%. A team that tests mainly on iPhones is checking the minority of its users. The app also has to read naturally in Hungarian, the country's official EU language, ask for consent before storing or reading data on the phone, and support the payment options open to people in Hungary, which now include qvik transfers from their own banking app.

Curiosive builds these apps from Ankara, Türkiye, with AI coding agents doing the volume and a senior engineer reviewing every change. We use React Native, so one TypeScript codebase reaches Google Play and the App Store. Agents scaffold screens, navigation, lists, form validation, tests and store metadata drafts. Engineers own token storage, auth refresh, entitlement checks, offline behaviour, permission prompts and the privacy declarations each store asks for before an app or update goes out.

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

What Hungary's Android and iOS split means for your app

With Android at 72.69% and iOS at 27.3% in Hungary in September 2026 by StatCounter's count, the Android build is the one most of your users will open. React Native lets us ship both from one codebase, but each store has its own release rules. Since 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36) or higher, and existing apps must target Android 15 (API level 35) or higher to stay available to new users. Every Google Play app also needs an accurate Data safety form that covers what third-party SDKs collect, and apps that let users create accounts must offer deletion both in the app and through a web link. We plan the Android build as the primary target from the first slice, not as a port at the end.

Hungary's cookie rule is not limited to websites. Section 155(4) of Act C of 2003 on Electronic Communications allows data to be stored on, or read from, a user's terminal equipment only with consent given after clear and comprehensive information that also covers the purpose of the processing. In an app, that reaches analytics and attribution SDKs that write identifiers to the phone, so we place the consent screen before they initialise. Hungary did not lower the GDPR Article 8 threshold, so it stays at 16. If an app offered directly to children relies on consent from younger users, the holder of parental responsibility must give or authorise it, and the controller must make reasonable efforts to verify this. Apple's updated age ratings now include 13+, 16+ and 18+, and the rating questions should be answered from what the app actually does.

Accepting qvik payments in a Hungarian app

qvik is the Magyar Nemzeti Bank's family of transfer-based payment methods built on the Instant Payment System. Since 1 September 2024 it has been available free of charge to all retail customers with a bank electronic channel, inside the mobile banking apps they already use, and free payment for consumers is written into section 36/E of Act LXXXV of 2009. Merchants accept it through qvik-QR, qvik-NFC, qvik payment requests or qvik-link, a payment link integrated into a merchant's or biller's mobile app. The QR, NFC and link formats are issued through payment service providers contracted with GIRO as sub-aggregators, so choosing a provider is an early decision, as is the return path from the banking app back into yours. Payment confirmation is checked on the server, never trusted from the client, and an order is marked paid only once that check passes.

Hungarian copy, DÁP login and public sector accessibility

Hungarian is the official EU language, so screens are laid out with Hungarian strings from the start rather than translated at the end. Identity is another local layer. Hungary's Digital Citizenship Programme (DÁP) is opening framework services in phases to state bodies and market players such as financial institutions, utilities and telecoms, and businesses can join the Digitális Állampolgár app's Data Wallet (Adattárca) for password-free login, identity verification and data sharing. If the client is a public body, Act LXXV of 2018 has required its mobile apps to be accessible since 23 June 2021, with an accessibility statement checked by a government-designated monitoring body. In that case screen reader labels, focus order and contrast are acceptance criteria written into each agent task, not polish added before launch.

Where agents work and where engineers decide in a mobile build

Agents take the repetitive mobile work: screens, navigation, list rendering, form validation, tests and first drafts of store metadata, each from a scoped task that a senior engineer reviews before it merges. Engineers keep what can hurt users. Tokens live in the iOS Keychain and Android Keystore, auth refresh and reconnection after a dropped connection are designed by hand, and permission prompts appear only when a feature needs them. Release paperwork is engineering work too. Since 1 May 2024, App Store Connect uploads must declare approved reasons in the privacy manifest for each required-reason API the code uses, and since 30 June 2022 apps with account creation must let users start account deletion inside the app. We built TrendinChat (trendin.chat), real-time trending-topic chat rooms, in React Native in two weeks, and the Coffict (coffict.com) order-ahead and loyalty app, both for clients in Türkiye.

Questions

The things people ask before starting.

Should an app for Hungary launch on Android or iOS first?

Usually on both from one React Native codebase, with Android treated as the primary build. StatCounter recorded Android at 72.69% and iOS at 27.3% of mobile share in Hungary in September 2026. One codebase avoids maintaining two separate apps, while testing priority follows the larger share.

Do apps in Hungary need consent before loading analytics SDKs?

Yes, when the SDK stores or reads data on the device. Section 155(4) of Hungary's Electronic Communications Act requires consent given after clear and comprehensive information that covers the purpose. We gate SDK initialisation behind that consent and declare the same data collection in the Google Play Data safety form.

How much does it cost to build a mobile app for the Hungarian market?

Work runs as AI-accelerated development, starting from $2,000 per month, with scope agreed in writing. Both are published US dollar starting points rather than quotes; the real figure comes from a written scope after a discovery call.

What are the working hours between Hungary and an app studio in Ankara?

Most of the day is shared: 7 hours of a standard 09:00 to 18:00 day in winter, when Ankara is two hours ahead, and 8 in summer, when the gap is one hour. We work Türkiye business hours and send a releasable build every week, with decisions kept in writing around one short weekly call.

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