Notifications
They arrive when there is a reason. Otherwise people switch them off.
● iOS/Android apps/ chapter · Apps
An app that uses the phone well.
Native with Swift and Kotlin when the app really has to use the phone, installable web when that is enough. We make that call together, before the quote, because it is the one that moves the cost most.
Tell us what it has to do A call, on us. You leave knowing what kind of app you need.
/ What it has to do well
The things an app has to be good at.
Each one weighs on the choice between native and web. That is why we look at what it has to do first, and how second.
Camera
A photo or a barcode, and the app does the rest on its own.
Offline
No signal, work goes on. It syncs when the network is back.
Payments
Purchases and subscriptions inside the app, by the stores' rules.
Languages
The app speaks the language of whoever opens it. Our own products already do.
Store
Publishing, reviews, updates. We have done it for our own products.
/ The choice
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.
/ Straight talk
What we WON'T do for you
/01
Native by default
If an installable web app is enough we say so, even though it is a smaller job for us.
/02
Your website, wrapped in an app
If it uses nothing of the phone you don't need one more icon. You need the site done well.
/03
Published and left there
Phones update and the stores change their rules. Whoever wrote it stays to keep it running.
/ The proof
We have already done it for ourselves.
A product of our own, with a real app on iPhone and Android. Recurring payments and store releases we learned there, before doing them on a project of yours.
/ What we work with
What an app needs to actually exist.
An app is not just the code: it's publishing on both stores, notifications that arrive, purchases inside the app. It's the part that stretches the timeline when nobody accounted for it.
- App Store
- Google Play
- Firebase
Store accounts stay in your name: the app is yours, and stays yours if you ever change supplier.
/ Frequently asked questions
The questions people ask.
You have products of your own: is there time left for my project?
Yes, and it is the same craft. Our products start from an idea of ours and we develop them end to end: interfaces, recurring payments, app-store releases. 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.
▸ We are here after the handover too
Tell us what's on your mind.
First call free. You leave knowing what's worth doing, and what isn't.