Cilantrobyte.

Tech Stacks · Mobile

Progressive Web Apps

Installable web apps for when the App Store is overkill.

Category

Mobile

At the studio

Since 2020

Projects shipped

Numerous

Status

Active

(01) Our take

PWAs are the right answer for a specific class of application: one that needs installability, offline support, and push notifications, but doesn't benefit from the discoverability or platform capabilities of the app stores. For internal tools, B2B SaaS, and content-heavy applications, a PWA often ships in half the time of a native equivalent.

We build PWAs on top of Next.js or a similar framework, with service workers for offline, Web Push for notifications, and manifest files for installability. The ceiling is lower than native — no background sync of the kind iOS offers, no deep OS integration — but the floor is much higher than most clients expect.

(02) What we build with it

Typical work

  • Internal tools with offline-first requirements
  • B2B SaaS applications where app-store distribution is unnecessary
  • Content applications with Web Push engagement needs
  • MVPs that want app-like experience without App Store review cycles

(03) How we engage

Engagement shape

Usually part of a web-app engagement rather than a separate line item. PWA-focused retainers run 4–8 weeks for retrofitting an existing web app.

(04) Pairs with

Works well with

Technologies we reach for alongside Progressive Web Apps in most engagements.

Frontend

Next.js

The default for serious React applications.

Frontend

React

The UI library we'd still pick today.

Frontend

TypeScript

Strict mode, no exceptions.

Mobile

Firebase

The fastest path from zero to a mobile MVP.

Thinking about a Progressive Web Apps project?

Start a project →back to all stacks