Choosing the stack
With Flutter or React Native you maintain one codebase for both platforms and usually cost less. We go with Swift and Kotlin when deep hardware access and a flawless feel are the priority.
Before anything else we settle the architecture: a single cross-platform codebase or separate native builds for iOS and Android. Budget, schedule and room for future growth all follow from that choice.
With Flutter or React Native you maintain one codebase for both platforms and usually cost less. We go with Swift and Kotlin when deep hardware access and a flawless feel are the priority.
Screens built to the iOS Human Interface Guidelines and Material Design and remain readable with enlarged text and screen readers. Whether the European Accessibility Act applies to your app is worth checking with a lawyer.
The server that stores data and runs business logic, hosted in an EU data centre and connected to your ERP, CRM or web shop so the app does not become yet another island.
Staff apps sign in with Entra ID; email, Apple or Google sign-in for customers; BLIK and card payments through Przelewy24, PayU or Stripe.
Records are stored locally on the handset and sync once the connection returns. Push messages are segmented so nobody deletes the app after a week.
Store listings, screenshots, the privacy questionnaire and app review in the App Store and Google Play, followed by regular new releases.
How long a first version takes depends on the number of screens and integrations, and we give a schedule after analysis. Store review comes on top, and its length is outside our control.
Who will launch it, in what situation and for what purpose. This step often reveals that some features belong in a web admin panel instead.
Clickable screens installed through TestFlight or a Google Play internal testing track, tried out in real conditions.
After every sprint a new test build lands on the phones of your pilot users.
Publication from your company developer accounts and an agreed release rhythm, including adjustments for each new iOS and Android version.
An app with no updates has a use-by date. Each autumn brings a fresh iOS and Android release, and store rules tighten along with them. Left without care, bugs creep in over time, and the app may drop out of search or out of the store. Budget for maintenance from day one, the same way you budget for hosting.
Your company's, set up before the first release. For an organisation account Apple may ask for a D-U-N-S number, and obtaining one takes time, so start early. If the app lives in a contractor's account, it remains theirs after you part ways, together with every rating and download.
It depends on the number of integrations and how often things change. The minimum is adapting to new OS versions and updating libraries a few times a year. We bill this hourly at PLN 190 excl. VAT or as a fixed monthly pool of hours if you plan further development.
For citizen-facing services run by public bodies, sign-in through the national identity node is possible and we integrate it. Whether a private company can use them depends on the current access rules, so we check that at the outset. If not, we use our own login or bank-based identity when a verified identity is really required.
That has to be designed together with your DPO or lawyer. Technically, location is collected only during working hours and for a stated purpose, the app tells people it is happening, and your processing register gets a new entry. For broader monitoring a data protection impact assessment (DPIA) is advisable.
Describe your future users and how frequently they would open it. You will get an honest verdict: native app, or a well-built mobile site.
Your enquiry has reached us
You will hear back within one working day, and if you have reported an outage that is holding up work, it goes to the front of the queue.
No match for that name. Try a different spelling or pick a bigger town nearby - all our support is delivered online, so your choice has no effect on the service.