// service · pwa · install without the play store

PWA: an app installable straight from the browser, no Play Store

An icon on the home screen, push notifications, offline features. Faster than a native app and no Apple/Google approval needed.

starting tier

Profile + Blog

starting price

From IDR 3M

duration

3–5 weeks

category

build

You need users to install your 'app' on their phones — but building a native iOS + Android app is too expensive (IDR 30-100M) and complicated (you have to submit to the App Store and Play Store, with reviews taking days). A Progressive Web App (PWA) is the middle ground: a website installable like an app, appearing as an icon on the home screen, running in its own window (no address bar), capable of push notifications, and with offline features for pages already opened. The investment is just a tenth of a native app, and it can be updated anytime without users having to download again. From IDR 3M, usually 3-5 weeks. Perfect for online stores with repeat customers, an internal employee app, or a product that needs push notifications without the Play Store drama.

// why this matters

Context & rationale.

Many small businesses and startups are stuck in a dilemma: a 'mobile app' becomes a perpetually deferred dream because building a native iOS+Android app is too costly. Meanwhile, their competitors who have an app gain a big advantage — push notifications that land instantly, fast access from the home screen, and a 'truly serious' perception. A PWA closes this gap at 10-20% of native cost. Famous case studies: Twitter Lite, Pinterest, Tokopedia Lite — all used a PWA with surprising results (engagement up 70%, retention up 40%). For the Indonesian context, where many users have entry-level phones with limited storage, a PWA is even more favored because of its small size (< 5 MB) compared to a native app (50-200 MB). Modern PWA push notifications are now supported on Android and iOS 16.4+, so practically every smartphone user can be engaged. For businesses focused on repeat customers (online stores with subscriptions, internal apps, daily services), a PWA often becomes a significant retention unlock.

// what you get

Full deliverables.

A manifest and service worker that make the website installable to the home screen
A custom icon, splash screen, and theme color — it feels like a native app
Push notifications (Android & iOS 16.4+) for re-engagement
Offline mode: pages already opened can be accessed without internet
An app shell that loads instantly after install
An Add to Home Screen prompt that appears at the right time
Background sync to send data when the connection recovers
Automatic updates without users having to download again
A standalone window view (no browser address bar)
A 90+ performance score — required for the install prompt to appear automatically
Integration with your main website — sharing data and auth
PWA-specific analytics: install rate, retention, push CTR

// our process

How we work.

01

Audit the Existing Website

If you already have a website, we audit its readiness to become a PWA: performance, structure, and caching needs. Many are already 70% ready, with just the PWA layer left to add.

02

Caching & Offline Strategy

Determine which pages are cached aggressively (homepage, catalog) and which must always be fresh (cart, checkout). A wrong caching strategy = stale data stuck on the user, with no updates.

03

Build the PWA Layer

Building the manifest, service worker, a complete icon set (192px, 512px, maskable), splash screen, and offline page. Setting up push notifications with a server backend to send broadcasts.

04

Optimize the Install Prompt

Not just throwing up an install prompt — we trigger it at the right moment (after the user engages for 30 seconds, or after the first purchase). Studies show prompt timing determines install rate by 5x.

05

Multi-Platform QA

Testing on Chrome Android, Safari iOS, Edge Windows, and Chrome desktop. PWAs behave differently on each platform — we make sure the experience is consistent.

// technical approach

How it works under the hood.

A PWA isn't a single technology, but a collection of modern web standards assembled to mimic the native app experience. The key is the service worker — a script that runs in the background and can intercept network requests. With a service worker, we can cache assets aggressively (HTML, CSS, JS, images) so pages already opened load instantly even offline. Our caching strategy uses a 'stale-while-revalidate' approach for content that can tolerate slight staleness, 'network-first' for content that must always be fresh, and 'cache-only' for static assets. The manifest.json defines the look when installed: icon, app name, theme color, and display mode (standalone so there's no address bar). Push notifications are implemented with Firebase Cloud Messaging or the native Web Push API, with an opt-in that requests permission at a high-value moment (not the instant the user lands). For iOS, we use specific workarounds (apple-touch-icon, viewport meta) so the look when installing from Safari stays tidy. The PWA auto-detects updates the next time the user opens it, and we prepare a user-friendly 'a new version is available, click to update' prompt.

// perfect for

Ideal if you...

  • Online stores with repeat customers who visit frequently
  • Businesses with a daily service (delivery, news, fitness tracker)
  • Internal employee apps without deploying to an internal Play Store
  • Communities/forums with high engagement
  • Startups that need a 'feels like an app' without native app cost

// not a fit for

Maybe not you if...

  • ×Apps needing heavy hardware features (AR, advanced camera, sensors) — native is better
  • ×Games with high-end graphics — a native engine fits better
  • ×Apps that strictly need Play Store/App Store distribution for credibility

// real example

Dapur Bunda — A Weekly Catering Ordering App

Dapur Bunda sells weekly catering packages for office workers. Customers have to order every Sunday night for a Monday-Friday package. They previously used a WhatsApp group, often missing messages and getting orders mixed up. We converted the ordering website into a PWA: customers install it on their home screen, get a push notification reminder every Sunday at 6 PM, and choose a menu for the week on an easy interface. After 3 months, 78% of regular customers had installed the PWA, push CTR averaged 42% (far above email's 12-15%), and weekly orders rose 23% thanks to consistent reminders.

outcome

78% install rate, 42% push CTR, orders up 23%, cost 1/8 of a native app

// faq · installable pwa

Common questions.

What's the difference between a PWA and a native app?

Native app: written specifically for iOS/Android, distributed via the Play Store/App Store, higher cost, deeper hardware features. PWA: a web that behaves like an app, installed straight from the browser, far lower cost, with features sufficient for most business use cases.

Can a PWA be installed on an iPhone?

Yes, since iOS 11.3 (Add to Home Screen). For push notifications, full support is on iOS 16.4+. Most iPhones in Indonesia already run iOS 16+, so it's not an issue.

Can a PWA appear in the Play Store?

Yes, using the Trusted Web Activity (TWA) technique. We help submit it if you need a Play Store presence. But most of a PWA's value is in installing straight from the browser, without the Play Store.

Can a PWA work offline?

Yes, for pages already opened (cached). If you need full offline mode for all features, that requires additional configuration and IndexedDB storage — which falls under a custom scope.

How much extra time does building a PWA take compared to a regular website?

The PWA layer usually adds 2-3 weeks on top of an existing website. If you build a new site as a PWA from the start, the total is 3-5 weeks (vs 2-3 weeks for a regular website).

What about storage size on the user's phone?

A PWA uses just 2-5 MB compared to a native app's 50-200 MB. The browser also automatically clears the cache of PWAs not used for a long time (each OS's storage policy).

Can I send mass push notifications?

Yes, with a Firebase Cloud Messaging or OneSignal backend. You can segment the audience (e.g.: send to those who ordered in the last 7 days), schedule, and track CTR.

// ready to start?

Build Your Business a Website
Right Now!

Free consultation via WhatsApp. We review your needs, give you a time & price estimate, then start together — no drama.

→ See examples of our work