When the work does not happen at a desk
An app earns its place when you need something a browser cannot do: work without a connection, use the camera or GPS, send a notification that actually arrives, sit in one hand while the other does something else. If what you need is a site that works well on a phone, we will say so and save you time and budget. If you do need an app, we design it around the gesture someone will repeat a hundred times a day.
Native or cross-platform, no dogma
The network is not always there
Before writing code we tell you whether you actually need an app. Plenty of problems are better solved by a site done well, and it is worth knowing that first.
The stores have their own rules
An app lives on updates
Do you really need an app?
We check whether the problem is better solved by an app or a site. Sometimes the honest answer saves months.
The central gesture
We identify the action the user will repeat every day and build everything else around it.
Native or cross-platform
We choose on performance, device integration and how long the app has to last.
Interaction design
We design screens and gestures respecting iOS and Android conventions, which differ from each other.
Build and integrations
We build app and backend, with offline sync and connections to the systems you already run.
Testing on real devices
We test on real phones, old and new, on slow networks and none. An emulator is not enough.
Publication and updates
We handle store listings, reviews and later releases, including the yearly platform changes.
Most of the time a site is enough. An app is justified when you need things the browser does not offer: offline work, reliable push notifications, heavy use of camera, GPS or hardware, or when the user opens it daily and the icon on the phone has real value. If the analysis says site, we will tell you, even though it is the smaller project.
Cross-platform covers iOS and Android from one codebase and costs less to build and maintain: good for apps made of screens, data and forms. Native is worth it when you need high graphics performance, deep OS integration or unusual hardware. The choice follows the use case, not a rule set in advance.
Developer accounts carry an annual fee on Apple and a one-off fee on Google. Those stay with you and in your company name: it matters that the accounts belong to you, not to us. Preparing listings, screenshots and privacy policies is work we do as part of the project.
If the use case calls for it, yes. We design the app to store locally and sync when the network returns, resolving conflicts between changes made offline by different people. It is not free in terms of complexity, so we do it where it genuinely matters: warehouses, building sites, vehicles in motion.
The long part begins. iOS and Android ship new versions every year and periodically raise the minimum requirements for staying on the stores: an app left un-updated eventually gets removed. We monitor crashes and performance on real devices and plan regular updates, rather than only acting when something breaks.
Gotanideaforanapp?Letustalkbeforeyoustart
We work out together whether an app is the right route and what the first version genuinely needs.