Your website is no longer enough
When users need to sign in, manage appointments, check status or enter data, you need an application rather than a page.
Services · E-commerce & development
App development
A practical approach to app development: web apps or PWAs first. Native apps when app stores and specific hardware features are really needed. This gets version 1 live sooner.
- Approach
- Web app / PWA first
- Typical projects
- Bookings, portals, tools
- Stack
- For example, Supabase & Vercel
- Reference
- heyHelp
An app solves a problem. It is not an end in itself.
Before discussing technology, we establish who will use the app, what task it should solve, when and how often. The answer defines the smallest useful scope: version 1.
I focus on web apps and Progressive Web Apps (PWAs). They run in the browser, can be installed like an app and share one codebase across mobile and desktop. A native iOS or Android app makes sense when store presence, specific device features or offline operation are essential.
Does this sound familiar?
Two codebases cost too much
Maintaining iOS and Android separately doubles effort and potential errors. A web app or PWA covers many scenarios with one codebase.
Projects get lost in scope
Without boundaries, the feature list grows and nothing launches. I keep scope focused so version 1 gets released.
What I build
Booking and appointment flows
Online appointments for studios, practices and service providers: calendars, confirmations, reminders and administration.
Customer portals
Login areas for documents, orders, status updates or communication.
Internal tools & dashboards
Administration, reporting and workflows for your team instead of spreadsheets and email.
Authentication & roles
Secure login, permissions for each user group, password resets and session management.
APIs & integrations
Connections to payments, calendars, email or existing systems. More about integrations.
Mobile-first UI
Interfaces that work on phones, with touch controls, loading states and clear error messages.
Decisions in app projects
Web app, PWA or native app?
Web app: runs in a browser, quick to develop, with immediate updates for everyone. PWA: an installable web app with offline features and notifications on supported devices. Native app: full device access and store presence, but more development work and store procedures. I recommend the simplest approach that meets your goal.
Data model first
What data exists, who may see it and what happens when it changes? A clear data model prevents later rebuilds. This includes privacy and retention periods.
Prototype the core flows
A clickable prototype of the key workflows comes before the full build. It lets you test the idea early, while changes are still inexpensive.
Proportionate technology
I use proven, maintainable components, including authentication, databases and hosting on established platforms such as Supabase and Vercel. This saves development time and reduces ongoing maintenance.
From idea to first version
-
Use case & data model 1–2 weeks
Define users, tasks, data and permissions to scope version 1.
-
Prototype 1–2 weeks
Test clickable core flows, gather feedback and make decisions.
-
Development 4–8 weeks
Build in short steps with regular progress reviews.
-
Testing 1–2 weeks
Functional and device testing, plus security and performance checks.
-
Deployment & operation Ongoing
Launch, monitoring, handover and planning the next release.
When an app makes sense
A good fit if
- You have returning users who sign in or manage data.
- You want to digitise appointment booking, enquiries or status updates.
- You are ready to start with a small first version and expand later.
Probably not a fit if
- You only need to publish information: a website is enough.
- You expect an app with every feature of a large provider from day one.
An app project
„For our heyHelp project, finding a partner who understood our mission rather than just writing code was important. es.design did exactly that. App development went smoothly, and the feel for intuitive user journeys exceeded our expectations. Technical precision makes the app a reliable tool.“
- App project heyHelp
Intuitive user journeys and reliable technology for a mission-driven app project.
- See all cases
App development questions
Costs vary widely with features, roles, integrations and design. I therefore start with a clearly scoped version 1 at a fixed price. The price calculator provides an initial guide.
A Progressive Web App is a web application you can install on your home screen like an app. It loads quickly and can partly work offline. It does not require an app store.
Usually not. Native apps are useful when you need store presence or deep access to device features. Booking, portals and tools often work well as web apps or PWAs.
A clearly scoped first version can usually be delivered in 8 to 12 weeks. More complex projects are planned individually.
I use established authentication, role permissions, encrypted transmission and data-minimising storage. We plan privacy and deletion policies together.
Yes, after reviewing its code and architecture. We then decide whether extending or rebuilding makes more sense.
Why es.design
01
Custom-built, never off the shelf
Every website is built for your business and your people – no themes, no templates, no 08/15. Powered by Storyblok, Vercel and Supabase.
02
100% personal
One contact for strategy, design and build – no account-manager ping-pong.
03
Fixed price, clear scope
You know what you get and what it costs before we start.
04
Local, digital everywhere
Studio in the Odenwald, projects across the region and beyond.
Ready for a first-class web project?
Free 30-minute intro call – no pitch deck, no obligation.
Book an intro call