Skip to content
Poland · Agentic mobile development

Mobile App Development for Teams Shipping in Poland

In September 2026, StatCounter put Android at 63.75% of the mobile operating system market in Poland and iOS at 36.2%. A launch on one store alone leaves out a large group of users either way. A team building for Polish users also has to write the interface in Polish, ask for consent before analytics SDKs touch the device under Polish electronic communications law, and meet the accessibility rules of a Polish act in force since 28 June 2025.

Curiosive is a studio in Ankara, Türkiye, and our apps are built with AI coding agents under senior engineer review. We work in React Native, so one TypeScript codebase ships to both the App Store and Google Play. Agents take the volume: screens, navigation, forms, tests and store listing drafts. Engineers keep the parts that can hurt users, such as token storage, session refresh and the privacy declarations each store reviews.

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

Android, iOS and the Polish language in apps for Poland

With Android at 63.75% of mobile operating system share in Poland in StatCounter's September 2026 figures, the device test matrix should lean towards Android hardware. Since 31 August 2026, new apps and updates submitted to 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. The iOS share of 36.2% still needs its own release care: since 1 May 2024, uploading a new or updated app to App Store Connect requires a privacy manifest declaring an approved reason for each listed required-reason API the code uses. Polish is the country's official EU language, so screens, store listings and permission prompts need Polish texts written to fit the layout and checked in context by a person.

Since 10 November 2024, storing information on a user's terminal equipment, or accessing information already stored there, has been governed in Poland by art. 399 of the Prawo komunikacji elektronicznej (Dz.U. 2024 poz. 1221). It requires prior clear and understandable information about the purpose and the user's consent, which may be given through the settings of software on the device or the service configuration. Storage or access necessary to transmit a communication or to provide a service the user requested falls outside those conditions. The Prezes UKE can fine a breach up to 3% of the previous calendar year's revenue (art. 446 ust. 1). In an app, attribution and analytics SDKs that write identifiers to the phone belong on the consent side, and the Google Play Data safety form must declare what they collect and share.

Payments in apps for Polish users: Apple's EU terms and BLIK

Apple says its EU terms, effective 1 October 2026, let iOS apps in the EU 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. As an EU Member State since 1 May 2004, Poland falls under those terms. Outside the stores' own billing, BLIK, the Polish mobile payment system used through banking apps, had 21.6 million active users at the end of June 2026, so any checkout the app runs through its own payment provider should plan for it. Either way, engineers keep entitlement checks on the server, so a paid feature never unlocks because the client says so.

Poland's accessibility act and what it means for consumer apps

Poland transposed the European Accessibility Act through the act of 26 April 2024 (Dz.U. 2024 poz. 731), in force since 28 June 2025. The directive covers consumer services including e-commerce, consumer banking, e-books and the mobile apps of air, bus, rail and waterborne passenger transport, other than urban, suburban and regional transport. The minister responsible for informatisation is the market surveillance authority for e-commerce services and the Rzecznik Finansowy for retail banking services, while the Prezes Zarządu PFRON monitors and supervises how the system works. A provider that fails the requirements faces a fine of up to ten times the previous year's average monthly salary in the national economy, capped at 10% of the previous year's turnover (art. 73). Labels, focus order and text scaling therefore go into each agent task's acceptance criteria.

What agents build and engineers own in a React Native app

Agents scaffold screens, navigation, list rendering, form validation, tests and store metadata drafts, including the Polish listing text, inside boundaries an engineer sets in each task. Every diff they propose has passed the type checker, linter and test suite, and none merges without a senior engineer reading it. Engineers own token storage in the iOS Keychain and Android Keystore, auth refresh, offline and reconnection behaviour, permission prompts and the consent gate that holds measurement SDKs back until the user agrees. Both stores require in-app account deletion when users can create accounts, and Google Play also wants a web link for deletion requests. Our React Native work includes TrendinChat (trendin.chat), real-time trending-topic chat rooms built in two weeks, and Coffict (coffict.com), coffee ordering and loyalty, both for clients in Türkiye.

Questions

The things people ask before starting.

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

Usually on both together. StatCounter measured Android at 63.75% and iOS at 36.2% of mobile operating system share in the country in September 2026, so a single-store launch leaves out a sizeable group. React Native keeps the two apps on one TypeScript codebase, so the second store is mostly release work rather than a second build.

Do apps in Poland need consent before analytics SDKs run?

Plan for yes. Art. 399 of the Prawo komunikacji elektronicznej requires prior information and consent before an app stores or reads data on the user's device, unless that is necessary to transmit a communication or to provide the service the user asked for. It is worth confirming a specific SDK setup with a lawyer.

Does Poland's accessibility law apply to a small app company?

Not if the service is offered by a microenterprise, which art. 4 pkt 1 of the Polish act exempts. The directive defines one as employing fewer than 10 persons with annual turnover or balance sheet total of no more than EUR 2 million. Larger providers of covered consumer services, such as e-commerce or consumer banking, have had to comply since 28 June 2025.

How do working hours line up between Ankara and an app team in Poland?

Closely. Poland sits one hour behind Ankara in summer and two hours behind in winter, so most of the Polish working day falls inside ours, which runs on Türkiye business hours. Decisions are written down, a releasable build arrives each week, and one short weekly call keeps the plan in step.

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