You need a customer area
Users sign in and see their own data, orders or file, with a notification when something changes.
Services
App development
An app for iPhone and Android that does something a website cannot.
The first question about an app is not what it looks like but why it has to be an app. Notifications, camera, offline use, a customer area on the home screen — that is what apps are for. For showing information, a good website is usually better, faster to ship and cheaper to keep.
When it genuinely should be an app, we build for iOS and Android together and make sure it passes review. Apple rejects apps that are no more than a repackaged website, so that conversation happens at the start rather than after the rejection.
Who this is for
Your product leans on the phone
Camera, location, offline use or biometric sign-in. Those only exist inside an app.
You want to be in the stores
Findable in the App Store and Google Play, with an icon on your customer's home screen.
What is included
iOS and Android
One codebase for both platforms, so a change is not built twice and paid for twice.
Design per platform
Navigation, gestures and the back button behave the way people on that platform expect, not the way a website would.
Accounts and sign-in
Secure sign-in, password recovery, and access enforced at database level so users only reach their own data.
Push notifications
Notifications for what matters, with permission handling, multiple devices per user, and opting out per type.
Offline behaviour
What happens when the connection drops is designed, not accidental. No white screen.
Store submission
Signed release builds, store listing, privacy policy and the disclosure forms Apple and Google require. We submit; you keep the accounts.
How a project runs
- 01
Intake
We start with what you want to achieve, not with what you want built. Who has to use it, what happens next, and where it breaks down today. Scope follows from that, and only then does a price.
- 02
Design
Structure first: which screens exist, what sits where, and the route someone takes from arriving to getting in touch. Visual design comes after. You see and approve it before a line of code is written.
- 03
Build
We build in short rounds and put every round online behind a private URL. So you are looking at the real thing on your own phone, not at pictures of it.
- 04
Launch and after
Going live, measurement and maintenance. Security updates, backup checks and changes as your business changes — a site that cannot move with you is a liability in two years.
What we build with
This site runs on exactly this stack. That is deliberate: we do not put anything in front of a client that we do not use ourselves.
Next.js and React
Pages are assembled on the server and sent as finished HTML. That is what makes a site fast and what lets a search engine read it without running anything.
TypeScript
A mistake is caught at build time instead of by your first visitor. Fewer surprises after launch.
Supabase
Database, authentication and file storage. Access is enforced at row level, so one customer's data is technically out of reach for another.
Vercel
Hosting on a network that serves your pages from the nearest location, with HTTPS and certificates handled for you.
Related work
Common questions
What does an app cost?
An app is almost always a bigger investment than a website, because two platforms, a backend and a store process are involved. What it comes to depends on the number of screens, whether accounts and notifications are needed, and whether it has to connect to existing systems. After the intake you get a fixed price for a defined first version.
How long does it take to build an app?
Expect three to six months for a first version that can go to the stores, plus review time: Apple usually takes one to three days, Google often less. A new Google Play account can carry a mandatory two-week testing period.
Do I need an app or a website?
Ask one question: does someone need to do something that only works on a phone? Receive notifications, take photos, work offline, sign in with a fingerprint. If the answer is no, a good website is faster, cheaper to maintain and easier to find. If it is yes, an app earns its keep.
Will it work on both iPhone and Android?
Yes. One codebase runs on both, so a change is made once. Where the platforms differ — navigation, the back button, notifications — we follow the conventions of each.
Is my app guaranteed to be accepted by the App Store?
Not automatically, and nobody can guarantee it. The most common rejection is guideline 4.2: an app that is no more than a wrapped website. That is why we agree at the start what justifies the app. If a submission is rejected, we resolve the objection and resubmit.
Tell us what you want to build
An intake takes about fifteen minutes and gives you a concrete picture of scope, timeline and price — including if you decide afterwards not to go ahead.