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
- Browser access and, on supported devices, installation without an app-store download
- Fewer steps for the things people do every day
- Interfaces designed around the team's recurring tasks, not just the demo
Who it's for
- Companies digitizing a process
- Founders validating a product
- Teams that need browser access across supported devices and locations
Stack and standards
PWA vs native app: when a PWA is the right choice
Native apps may involve platform-specific work and app-store review cycles. A PWA uses a web codebase, opens through a browser and can be installed on supported devices; capabilities such as push notifications and background behaviour vary by browser and operating system. For bookings, orders, client portals and internal tools, we compare those limits with the actual flow before recommending PWA or native. H501 Barber and Panzerotto Chic are documented production PWA cases.
What you need to start an app or PWA project
You do not need complete technical specifications: the core flow, users and first-release priorities are enough for an initial assessment. We then map features, roles, data and integrations. Depending on the project, our stack may include Supabase, Vercel, React or Expo. The agreed critical flows are prototyped before implementation begins.
How we handle backend, database and notifications
Where the scope calls for it, we use PostgreSQL, authentication, database-level policies and server APIs. Web Push support depends on browser and operating-system conditions; on iOS it applies to supported Home Screen web apps. For custom work, code, documentation and access handover are defined in the contract, while third-party services retain their own licences and terms.
Frequently asked questions about app and PWA development
- Does a PWA work on iPhone?
- A PWA can run on iPhone, but capabilities vary by iOS version and browser conditions. Web Push is available for supported web apps added to the Home Screen from iOS 16.4; compatibility is checked against the project's target devices.
- 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. The first release can focus on the agreed core flow, with later features prioritised from actual usage and business needs. Whether this phased approach is more efficient depends on the product, dependencies and release constraints.
- Can a PWA receive push notifications?
- Yes, where Web Push is supported and the user grants permission. On iOS it applies to supported Home Screen web apps from version 16.4; exact behaviour is verified for the target browsers and operating systems.
Have an app or PWA to build?
Tell us the core flow and what should happen in the first 30 days of use.