PWA iOS for a fitness studio: 1.2 MB vs 47 MB native, no App Store
A chain of 4 fitness studios wanted a mobile app for booking group classes, but didn't want to wait 4-6 weeks for App Store review and pay 30% Apple commission. Built a PWA with iOS Add to Home Screen, offline mode, and push notifications.
Native iOS = 4 weeks of review + 30% Apple commission + 47 MB install
The studio chain wanted a mobile app: group class schedule, booking, reminders 24 hours / 2 hours before training, visit history and memberships. Competitors built native iOS — but 30% Apple commission on in-app payments, $99/yr developer fee, and 4-6 weeks of App Store review for every update.
Second pain point: clients didn't want to "install yet another app". A competitor's native app got 2,100 installs in 14 days, but only 47% activated (opened more than once). Half the installs "lived" in the apps folder and were never opened.
The studios wanted to test new features quickly (e.g. video workouts), but the native flow required a fresh App Store review for every meaningful change — which blocked product velocity.
PWA with iOS-specific tuning for Add to Home Screen
- PWA manifest + Service Worker (Workbox 7) — the app installs with one tap via "Share → Add to Home Screen" with full icon and splash screen
- iOS-specific meta tags — apple-touch-icon for all iOS widths (180/167/152/120 px), `apple-mobile-web-app-status-bar-style`, `viewport-fit=cover` for notch on iPhone X+
- Onboarding tour for iOS — iOS Safari doesn't show the install banner automatically, so we added a custom "Install for notifications" prompt with a 2-screen instruction
- Offline-first via IndexedDB — schedule, profile, training history, and membership cached locally. Viewable on the metro without network
- Background sync — booking a class even offline. Service Worker saves the action and sends to the server as soon as network is available
- WebPush + iOS 16.4+ support — push notifications for bookings and reminders 24h / 2h (with iOS 16.4 Apple finally supported WebPush in installed PWAs)
- YClients embed + YooKassa — booking via YClients API, membership payment directly via YooKassa without 30% Apple commission
What's under the hood
PWA numbers vs native iOS
Saved: ~₽890,000 in the first year on Apple commission (vs native) with the same UX and push notifications. New-feature deploys — 30 seconds via CI/CD, no blocking App Store review.
Who benefits from PWA over native
- · Booking services (fitness / salons / SPA / clinics) — UX like native, no App Store review, no 30% commission
- · E-commerce — push notifications for order status, offline catalog, fast install straight from the browser
- · B2B tools for teams — no App Store distribution needed, central deploy for all employees
- · EdTech / online schools — assignment delivery, offline lesson viewing, no App Store review for every update
- · Performance campaigns with PWA landings (iGaming / sweepstakes / affiliate) — instant install, no native SDK fingerprint issues
From technical brief to production PWA with App-Store-like UX — 3-5 weeks. Pricing from ₽150,000 for MVP (booking + offline + push), from ₽350,000 for a full-featured PWA with integrations.
Discuss a PWAАудит за 5 000 ₽ — с конкретным отчётом и сметой
Расскажу что внедрить в вашем бизнесе в первую очередь, какая будет окупаемость, и нужен ли вообще AI для вашей задачи (иногда — нет).
Или просто напишите свой вопрос — отвечу в течение 2 часов