01
App design
Screens, flows and states. Before writing code we build a clickable prototype so you can see how it is used and tell us what to cut.
We design, build and publish apps on the App Store and Google Play. One codebase for both systems when that fits, and native development when the project calls for it.
We own the whole path, including the boring store paperwork.
Screens, flows and states. Before writing code we build a clickable prototype so you can see how it is used and tell us what to cut.
With Flutter or React Native we keep a single codebase for Android and iOS. Lower development cost and, more importantly, lower maintenance cost over time.
If the app needs users, data or payments, we build the server: Node or Python, PostgreSQL, authentication and a documented API.
Listings, screenshots, privacy policy, Apple and Google review. We handle the back and forth until the app is approved.
Segmented push, usage events and reports. Knowing which screen people use and where they drop off beats any opinion voiced in a meeting.
Android and iOS change every year. We keep the app current with each new system version so it does not quietly stop working.
The question that shows up in the first meeting. Here is how we answer it.
If the app is about content, management, catalogue, bookings or commerce, Flutter or React Native are more than enough. Built once, running on both systems, updated in one place.
If you need heavy graphics performance, deep hardware access or features that land on one system first, Swift or Kotlin is the right call. It costs more and we say so beforehand.
Sometimes you do not need an app at all. A PWA installs from the browser, does not depend on store approval and costs a fraction. When that is the better option, we tell you, even though it pays us less.
A stack proven on projects that are published and in use, not on lab experiments.
It depends on how many screens it has and whether it needs its own server. A catalogue app with login is a very different project from one with payments, geolocation and chat. We send the fixed quote within 48 hours of the first call.
Between 6 and 12 weeks for a first published version, depending on scope. Every two weeks you get a build you can install on your phone and actually use.
Yes. The Apple and Google developer accounts belong to your company and you own them. We publish with delegated access, so the day you want to continue with another team, you are not tied to us.
Yes, and those are their costs, not ours: Apple charges an annual developer subscription and Google a one-time registration fee. We tell you the current amounts before we start.
You can, and sometimes you should. Google Play approves faster and costs less to register, so it works well to validate with real users before facing Apple review.
Projects continue with a monthly maintenance agreement or with blocks of hours. You pick whichever fits the pace of change your app has.
Almost no project fits one category only. These are the other fronts we cover.
Corporate sites, landing pages and online stores that actually ship.
Chatbots over your data, document reading and internal assistants.
We connect your systems and take the manual work out of the middle.
Subscription products, from MVP to the production release.
Two or three lines about what you want to build is enough for us to come back with scope, timeline and price.