Technology choice
Shared code with Flutter or React Native is quicker and cheaper. Native development gives full platform access and the smoothest interface.
An app earns its keep when people open it often and need what only a phone offers: the camera, location, notifications, or working in the field with no signal. If a well-built mobile website would do the same job, nobody will install the app, and we say so at the outset.
The key decision comes first: one shared codebase for both platforms or two native apps. It shapes the price, the timeline and what the app can grow into.
Shared code with Flutter or React Native is quicker and cheaper. Native development gives full platform access and the smoothest interface.
User journeys, screens and an interface that follows Apple and Google guidelines while respecting WCAG, text scaling and screen readers.
The app itself plus the server side that stores data. The backend runs in EU data centres, so personal data does not leave the EU without reason.
MitID through an approved broker, NemLog-in for citizen-facing public sector services, and Entra ID for internal staff apps.
Data is kept on the device and synchronised when a connection returns. Notifications are segmented so the app never turns into a nuisance.
Store listings, copy, screenshots, privacy details and the full review process with the App Store and Google Play.
A first version usually takes at least three months. On top of that comes store review, which can last anything from a couple of days to a week.
Who opens the app, how often and why. This is where it becomes clear whether an app is needed at all.
Clickable screens you can try on your own phone through TestFlight or an internal test track.
Sprints with test builds that your staff install and try out on real devices.
Release from your developer accounts, store approval and an agreed schedule for updates.
An app only stays alive while it is being updated. Apple and Google ship new operating systems every year and keep tightening their rules. After eighteen months with no maintenance, faults start to appear, and eventually the store removes the app. Maintenance is therefore a fixed budget line, not an optional extra.
Shared code is typically around a third cheaper and covers most business needs: customer portals, ordering, field registration. Native is the right call for demanding graphics, heavy use of the camera or Bluetooth, and wherever every millisecond of interface response matters.
Frequently it is, and we look at that option first. An app becomes relevant when users come back daily, need notifications, must work offline or rely on the phone's hardware.
Your company, and that needs to be settled before release. An app published from a supplier's account stays with the supplier if the partnership ends, together with every install and review.
Yes. Private companies integrate through a certified MitID broker, while public bodies use NemLog-in. We handle the technical side and help with the paperwork for the agreement.
Tell us who will use the app and how often. We will give you a straight answer on whether you need an app or whether a website would cover it.
Thank you for getting in touch
One of our consultants already has it. Expect a reply within the working day; anything urgent goes straight to an engineer.
That city is not on our list. Check the spelling or pick the nearest larger town.