First: is it actually needed?
Before a line of code we look at whether the app solves a problem someone has, and whether that someone would use it. Often a single page and a form are enough to find out, at a fraction of the cost.
An app that uses the phone well.
Native with Swift and Kotlin when the app has to use the phone, installable web when that is enough. We decide together, before the quote.
Tell us what it has to do A call, on us. You leave knowing what kind of app you need.
From the idea to the store, and after.
An app is not just the code: it is what comes before and what comes after. We follow all of it, and where nothing is needed we say so.
The screens, before the code
We draw the whole journey — what opens, what you tap, what happens — and put it on your phone to try. Changing your mind here costs nothing; later it costs weeks.
The build, iPhone and Android
Native with Swift and Kotlin when the app really has to use the phone, installable web when that is enough. One codebase where it makes sense, two where it is needed.
Testing on real phones
Not just the simulator: we try it on different devices and versions, and put it in someone's hands before the store with TestFlight and Google Play internal testing.
Publishing on the stores
Accounts, listings, descriptions, screenshots, privacy notices and Apple's review: we handle it, and the accounts stay in your name. This is the part that stretches the timeline when nobody plans for it.
The first users
A listing written to be found on the stores, and campaigns for the first installs. We start small and watch what brings people who stay, not what brings numbers.
How the app earns
Subscriptions, in-app purchases, payments or advertising: we pick the model with you and wire it to the stores, which have their own rules and their own cuts.
After it is published
The stores change their rules and phones change their system every year: we stay on updates, rejections and new versions, the way we do for our own products.
Native, or installable web.
It is the decision that moves the cost most. It gets made after we know what the app is for, not before.
Let's talk A call, on us. You leave knowing which of the two you need.
Native, with Swift and Kotlin: it talks to the phone directly, and comes from the store.Installable web: it opens from the browser, gets its own icon, and updates without going through the store.
The questions people ask.
You have products of your own: is there time left for my project?
Yes, and it is the same craft. We develop our own products end to end, and they are where we try ideas out before taking them to a client. If there were no room for your project, we would tell you on the first call.
Do you build iPhone and Android apps?
Yes, native with Swift and Kotlin when the app has to use the phone, or as an installable web app when that is enough. We make that call together after working out what the app is for, because it is the decision that moves the cost most.
Do I need an app, or is the website enough?
If it has to use the phone, notifications, camera, working with no signal, you need an app. If it does what the site does, you need the site done well for a small screen.
Does an installable web app come from the store?
No: it opens from the browser and is added to the phone's home screen with its own icon. It updates on its own, with no store review in between.
How much does an app cost?
There is no price list. What weighs most is the choice between native and installable web, and we make it together before the quote, which comes in writing after the first call, free.
Tell us about your project.
The first call is free of charge: you leave knowing what is worth doing, and what is not.