Installable apps without losing speed or control.
We build web apps and PWAs for work processes, communities, internal tools and digital products that must work well across mobile and desktop.
What we build
The right PWA reduces friction: it opens from the browser, can be installed, stays fast and lets you validate a product with more control than jumping straight to native, even when the audience expands beyond one country.
- Experiences that work with one hand and a mediocre connection
- Installs on the phone without the App Store — no waiting, no download
- Fewer steps for the things people do every day
- Interfaces the team still enjoys six months in, not just at the demo
Who it's for
- Companies digitizing a process
- Founders validating a product
- Teams that need access from every device and geography
Stack and standards
PWA vs native app: when a PWA is the right choice
A native app requires separate development for iOS and Android, app store review cycles, longer update timelines and a double codebase to maintain. A PWA runs in any browser, installs without a store, receives push notifications and updates instantly. For most use cases — bookings, orders, client portals, internal tools — a well-built PWA delivers the same value at a lower development cost and with fewer external dependencies. Our projects H501 Barber and Panzerotto Chic are production PWAs used daily.
What you need to start an app or PWA project
You do not need complete technical specs: the core flow, who uses it and what should happen in the first 30 days is enough. From there we map features, roles, database schema and necessary integrations. We work with Supabase for the backend, Vercel for deployment and React or Expo for the frontend. The visual prototype comes before the code: you see and approve every screen before a single line is written.
How we handle backend, database and notifications
Every app we build has a structured backend: Supabase with PostgreSQL, authentication, Row Level Security for permissions and serverless APIs on Vercel. Push notifications use Web Push — compatible with Android and iOS from version 17.4. We do not use off-the-shelf solutions that create hard-to-remove dependencies: the code we deliver is yours, documented and maintainable without us.
Frequently asked questions about app and PWA development
- Does a PWA work on iPhone?
- Yes. PWAs have worked on iOS Safari for years. Web Push Notifications are supported on iPhone from iOS 17.4 (2024). Our production projects already use push notifications on both platforms.
- How long does it take to develop a PWA?
- A PWA with a single core flow (bookings or orders) is delivered in 4–6 weeks. More complex systems with multiple roles, logic and integrations take 8–12 weeks. We give a precise estimate after mapping the flow.
- Can I add features after launch?
- Yes, that is how it works in practice. We launch the core — what is needed immediately — and add features based on real usage. It is the most efficient way to build a digital product: priorities always shift after the first month of real use.
- Can a PWA receive push notifications?
- Yes. We use Web Push, compatible with Android and iOS 17.4+. Our H501 Barber and Panzerotto Chic projects both use push notifications in production for booking reminders and order updates.
Have an app or PWA to build?
Tell us the core flow and what should happen in the first 30 days of use.