In 2024 when I decided to move Member Kitchens away from hybrid app-store apps and toward a universal Progressive Web App, my fear of losing revenue was real. Customers had built businesses around an icon on the home screen. I worried they would read "no more App Store" as "no more app" and walk away.
That did not happen the way I expected. Here is what did — and why I would double down on the decision today.
The problem I was trying to escape
A few years into building Member Kitchens, we shipped a hybrid mobile app alongside the responsive web platform. It worked, but it split our attention in ways that hurt everyone:
Two codebases, one product. Every meaningful feature had to exist in two places. Time on the mobile app was time away from the web app — and many features never made it to the store build at all.
App-store overhead. Certificates, profiles, review cycles, policy changes, and white-label build/release work for every tenant. We were beholden to reviewers and timelines we did not control.
Acquisition economics that never made sense. Most creators drive traffic to the app store; the store rarely drives traffic to them. Marketing on the web is still less expensive and more direct than fighting for ASO.
Search vs. silo. Store apps live behind a download wall. A PWA is still the web — content can be indexed, shared, and discovered the way members already find you.
I was spending roughly half my engineering time maintaining app-store versions. That was time I was not spending on the platform customers actually used every day.
The approach: one universal app, powered by Progressier
A universal app — a fully responsive web app with installable, app-like behavior — was the bet. Members still get what they want from an "app": an icon on the device, a fast standalone experience, and push notifications they control. Business owners still get engagement without surrendering discovery to a store listing.
Timing finally made it viable. PWA support has matured across platforms, and iOS push for installed web apps (iOS 16.4+) removed the last major gap. We paired that with Progressier, which makes install prompts, manifests, service workers, and push delivery robust without rebuilding native infrastructure for every tenant.
The result: code once. What we ship on the web is what members install. No lagging hybrid build, no "coming soon to the app."
Before and after: what actually happened
Before (hybrid app-store era)
Feature rollouts were uneven — web moved fast, the store build lagged.
Engineering time went to certificates, releases, and reviewer feedback loops.
PWA was not an option for most tenants; an App Store presence was a high bar.
I lived with a constant background fear that any platform shift would trigger churn.
After (universal PWA)
Most customers stayed — even those who were nervous about leaving the stores.
Two customers left completely — but notably, neither launched an App Store app afterward. They shifted business strategy in other directions. Removing the store version clearly influenced those decisions, but it was not the only driver.
Customers who stayed and adopted the PWA have grown. Once installed, members love the app feel and push notifications.
Dozens of creators now have an installable app who never could have done the app-store path. That reach alone justified the bet, and I doubled down by lower the monthly fee so more people could adopt it.
I redirected that reclaimed engineering time into the web platform itself — effectively reinventing it into something roughly 10× what the original native app ever delivered. The Page Builder, richer member hubs like My Stuff, and deeper community tooling are direct results of that focus.
The remaining friction is honest and specific: iOS install still requires guided steps (we cannot programmatically install the way Android and desktop often allow), and habit — people still search the App Store out of reflex. Once they are installed, the experience holds. Marketing on the web remains cheaper and more controllable than store campaigns.
I would make the same call again. The fear was real; the outcome was better than I modeled. If you are weighing app stores against a universal app for your nutrition or coaching business, I hope our numbers and your members' lived experience after install are useful data points — not just the theoretical trade-offs.
And it Looks like I'm not alone
These are independent case studies from founders, coaches, and small teams who either skipped the app stores entirely or replaced native apps with a Progressive Web App. Each link goes to the primary source.
Solo founders and bootstrapped builders
Jobtable — bootstrapped SaaS founder
After shipping Jobtable as a PWA and also wrapping it for the Apple and Google app stores, founder Mike concluded the native listings were unnecessary overhead. Customers installing the PWA could not tell it apart from the store build. He argues one codebase, instant updates, and iOS push (since 16.4) make PWAs the rational default for a bootstrapped SaaS — and that “Do you have an app?” should be answered with a confident yes, pointing to the installable web app.
Venture Crane — iPad-first writing app
A solopreneur-style product studio shipped a nonfiction writing app (rich text, AI rewrites, Google Drive sync, PDF/EPUB export) as a PWA instead of an App Store native app. The thesis: before product-market fit, App Store review cycles and dual codebases are capital misallocation. They deployed 14 changes in two weeks — each in minutes, not days of review. Native is deferred until measurable retention and explicit requests for native-only APIs justify it.
Lucavera — solo financial app builder
Building alone, the Lucavera founder chose a PWA to stay cross-platform without the 30% app-store cut and without spending cycles on store submissions. The product is a personal finance OS with Gemini-powered transaction categorization and 150+ currencies — focused on shipping features, not platform gatekeepers.
Bulls & Cows — indie game developer
A solo developer turned a vanilla-JS logic game into an installable, offline-capable PWA and deliberately skipped Apple ($99/year) and Google Play ($25) fees. With 1.3K+ players and ~2-minute sessions, the story is proof that a side project can reach real usage without store distribution — updates ship instantly, no review queue.
ToolKnit — solo developer (72 browser tools)
Zihang Dong built 72 privacy-first tools in 77 days on a $5/month VPS with no backend processing. The entire suite is a PWA: a service worker precaches tools and blog posts for offline use and instant repeat loads. Not an app-store migration story, but a solopreneur pattern — one web codebase, installable shell, zero store dependency.
Coaches, creators, and practitioner-led businesses
Smartbody.pro — nutrition coach
A nutrition coach serving ~20 one-on-one clients commissioned a web platform to escape manual 1:1 delivery. The result scaled to 6,000+ participants, cut admin time per client from hours to minutes, and moved revenue from hundreds per month to six figures annually — all through a responsive web app with push, subscriptions, and automated daily content, not an App Store app.
Challenge Yourself — fitness programme creator
A fitness creator needed native-app functionality (12-week programmes, video-guided workouts, progress tracking, coaching) without iOS/Android store overhead. The brief explicitly called for a Next.js PWA installable from the browser on iOS and Android — “the functionality of a native fitness app without the distribution overhead of the app stores.”
Fitness content creator — custom workout PWA
One creator replaced a stack of generic fitness subscriptions with a purpose-built PWA: home-screen install, offline support, sub-second loads on cellular, AI coach chat grounded in the user’s real workout data, and a spreadsheet as the system of record (no vendor lock-in, no recurring app fees). The architecture is positioned as replicable for other solo coaches with bespoke programming.
Impact Personal Training — trainer + client platform
A small training facility wanted trainers and clients connected without mandatory app downloads. Codica built a fitness PWA from scratch: clients open it from the home screen; trainers use desktop dashboards for workouts, nutrition plans, and progress metrics. Large data volumes, fast loads, no store install required — a practitioner-scale version of the same pattern nutrition and coaching businesses use.
Small teams that replaced native apps with PWAs
MishiPay — retail checkout startup
MishiPay launched with separate iOS and Android apps for in-store scan-and-pay. Users loved the idea but resisted downloading another app at the checkout line. After switching to a PWA (QR-code entry in stores, camera scanning in the browser), transactions increased roughly 10× and shoppers collectively saved an estimated 2.5 years of queue time. The majority of transactions moved to the web.
BookMyShow — ticketing (India)
India’s largest ticketing brand saw users uninstall the native app over storage and data concerns, then get a worse experience in mobile Safari. Their PWA replicates the app UI at 54× smaller than Android and 180× smaller than iOS, loads in under three seconds, and drove an 80%+ conversion lift versus the old mobile web flow — reaching users who would never download another app.
Flipkart — e-commerce (app-only strategy reversed)
Flipkart briefly went app-only, then rebuilt as Flipkart Lite, a PWA combining web reach with app-like speed. Home-screen users convert 70% more than average; the PWA uses 3× less data than the native app for a first purchase. A cautionary tale for anyone who assumes store apps are the only “serious” mobile channel.
Goibibo — travel booking
Goibibo’s lightweight mobile web matched search-to-detail conversions with native apps but lost users at payment. After investing in a full-featured PWA aligned with iOS/Android UX, conversions jumped 60% versus the prior mobile web flow; logged-in users (who convert 6× more) rose 20%. Leadership stated that not investing in the PWA would have cost a fortune.
TradeZing — founder with 400+ native apps built
CEO Jordan Edelson had built hundreds of native apps professionally but chose to center TradeZing on a WordPress PWA for the web-first experience. A prior Flutter cross-platform app still left web and mobile disconnected and maintenance-heavy. The team refocused on the PWA as the flexible core and used wrapping only where a store listing was unavoidable — describing native-from-scratch as high-risk compared to web-first.
Patterns that repeat across these stories
Download friction beats feature lists. MishiPay, BookMyShow, and Flipkart all saw users abandon native installs even when the product was good (MishiPay, BookMyShow) or shift strategy after an app-only dead end (Flipkart).
Solopreneurs optimize for iteration speed. Venture Crane, Lucavera, and Bulls & Cows explicitly traded store presence for deploy-in-minutes feedback loops.
Coaches scale through the web, not the store. Smartbody.pro, Challenge Yourself, Impact PT, and the Parameter Strategies creator story share one thread: personalized delivery at scale without asking members to find you in an app marketplace.
“Native later” is a valid path. Jobtable and Venture Crane both treat app stores as optional distribution — not prerequisites for having a real app.
iOS install education remains the gap. Several sources (Jobtable, Challenge Yourself, BookMyShow) still invest in guided install flows — the same friction Member Kitchens customers report today.
Sources are third-party articles, portfolios, and Google web.dev case studies. Metrics quoted are as reported by each author at time of publication; your mileage will vary by audience and onboarding.
Enterprise and large-brand case studies show the same pattern at scale: remove download friction, unify the codebase, and treat the installable web app as a first-class product surface — not a fallback to native apps.
Global retail and e-commerce
Flipkart
After a brief app-only phase, Flipkart rebuilt as Flipkart Lite, a PWA that merges web reach with app-like performance. Home-screen users convert 70% more than average; time on site tripled (70 seconds → 3.5 minutes); re-engagement rose 40%; data use for a first purchase dropped 3×. Roughly 60% of visits now launch from the home-screen icon.
AliExpress
AliExpress built a cross-browser PWA so mobile web users get app-like performance without a mandatory download. New-user conversions rose 104% (82% on Safari); users viewed 2× more pages per session and spent 74% more time per session. Leadership framed it as investing in web across all browsers rather than funneling everyone into the native app.
BookMyShow
Users loved the native app but hated the storage and data cost — and uninstalling left a broken mobile-web experience. The PWA is 54× smaller than Android and 180× smaller than iOS, loads in under three seconds, and drove an 80%+ conversion increase versus the previous mobile site.
Lancôme — L’Oréal
Mobile traffic passed desktop, but mobile converted at 15% vs 38% on desktop. Lancôme shipped a PWA instead of a thin site refresh: time-to-interactive fell 84%, bounce dropped 15%, mobile sessions rose 51%, and conversions increased 17%. Push notifications on abandoned carts lifted recovery conversions 8% with an 18% open rate.
Technodom
Technodom explicitly replaced its native iOS and Android apps with a Magento PWA (ScandiPWA), citing single-codebase maintenance and sub-second mobile loads. Reported results: 26% higher conversion, category pages 12× faster, product pages 8× faster, and one of the largest Magento PWA deployments globally.
Starbucks
Starbucks built a PWA for ordering and store locator with offline menu browsing and cart building before connectivity returns. The web app is 233 KB vs 148 MB for the iOS app (99.84% smaller). Reported outcomes include 2× daily active users and desktop ordering approaching mobile volume — rare proof that PWAs matter beyond phones.
Travel and hospitality
MakeMyTrip
With two-thirds of traffic on mobile, MakeMyTrip’s PWA tripled mobile-web conversion rates, cut page-load time 38%, increased shopper sessions 160%, and reduced bounce 20%. First-time PWA shoppers were 3× more likely to convert than first-time native-app visitors with similar booking values.
Goibibo
Goibibo matched native apps on early funnel steps but lost users at payment until it invested in a full-featured PWA aligned with iOS/Android UX. Result: 60% higher conversions vs the prior mobile web flow and 20% more logged-in users (who convert 6× more). Leadership said skipping the PWA “would have cost us a fortune.”
Trivago
Trivago prioritized offline access, push, and home-screen install over a big-bang native rebuild. 500,000+ users added the site to their home screen; engagement for installed users rose 150% (0.8 → 2 repeat visits); click-outs to hotel offers increased 97%. When sessions dropped offline, 67% of users continued browsing after reconnecting (web.dev analysis).
Weekendesk
Weekendesk prompts PWA install on the second page visited (after intent is clear). Users who launch from the home screen were 2.5× more likely to complete a booking — a clean enterprise example that install prompts work better after demonstrated interest, not on first landing.
Media, publishing, and social platforms
Forbes
Forbes rebuilt mobile as a PWA to fix slow loads and weak engagement. Reported gains: homepage loads in 0.8 seconds (vs 3–12 seconds before), 100% engagement increase, 43% more sessions per user, 6× page-completion rate, and 20% higher ad viewability.
Nikkei
With 450M+ monthly digital visits, Nikkei replaced a slow legacy mobile site with a multi-page PWA. Lighthouse score jumped 23 → 82; organic traffic rose 2.3×; subscription conversions 58%; daily active users 49%; page views per session 2×.
After going “all-in” on native apps, Pinterest found unauthenticated mobile web converted only ~1% to signup/login/install. Rebuilding mobile web as a PWA produced 40% more time spent, 60% more core engagements, 44% higher ad revenue, and within a year 843% more signups and 370% more logins year-over-year on mobile web — which became the top signup platform.
Twitter / X
Twitter Lite became the default mobile web experience worldwide for users on slow networks. The PWA is ~600 KB vs 23.5 MB for the native Android app. Reported results: 65% more pages per session, 75% more tweets sent, 20% lower bounce rate, with sub-3-second repeat loads on 2G/3G.
The Washington Post
With ~70% of traffic on mobile (mostly mobile web, not the native app), WaPo’s PWA beta showed users reading 5× more pages per visit and cut load times from ~3 seconds toward ~1 second. Leadership framed the web — not app-store distribution — as the growth surface. (AMP case study on web.dev documents related mobile retention gains.)
On-demand and global platforms
Uber
As Uber expanded into markets with low-end devices and 2G networks, it rebuilt the rider experience as m.uber — a viable alternative to the native client. Core ride request is 50 KB gzipped with ~3-second time-to-interaction on 2G. Service workers keep the experience usable through intermittent connectivity.
Gravit Designer (Corel)
Gravit shipped a desktop PWA on ChromeOS and beyond. PWA users are 24% more active, 31% more likely to return, and 2.5× more likely to purchase Gravit Designer PRO than users on other install types — enterprise proof that installable web apps can drive paid conversion, not just page views.
Re-engagement at retail scale
Carrefour
Cited by Google’s PWA business guide: Carrefour used web push notifications (enabled by PWA/service-worker infrastructure) for abandoned-cart recovery and multiplied conversion on that flow by 4.5×. (Insider case study reports a 350% conversion uplift on cart-recovery push in the first month.)
What large-company stories have in common
Native apps did not disappear overnight — but the web/PWA became the primary acquisition and conversion surface (Flipkart, AliExpress, BookMyShow, Pinterest, Washington Post).
Explicit native replacement happens at scale — Technodom retired iOS/Android apps; BookMyShow built for users who uninstalled the native app.
Install prompts work after intent — Weekendesk on page two; Flipkart/Trivago on home-screen cohorts outperform casual browsers by large multiples.
Push + offline extend the funnel — Lancôme, Carrefour, Trivago, and Goibibo all tie PWA infrastructure to re-engagement revenue, not just faster page loads.
Size and data efficiency matter in emerging markets — Starbucks, BookMyShow, Twitter Lite, and Uber all cite KB-scale web clients vs 100MB+ native apps.
Primary sources: Google web.dev case studies, company engineering blogs, and published vendor case studies. Metrics are as reported at time of publication.