Your live site,
as an App Store + Google Play app
We put your existing site behind an app icon on your customers' phones — then let you send them push notifications (new menu, reminders, sales). You don't rebuild the site.
Free trial build · Starter from $19/mo
Where this pays off most
The real question isn't "can my site be an app?" — it's "once it's an app, can I push my regulars back in?" If any of these match, it pays off.
- 01
Cafe / restaurant loyalty
Push regulars about new menus, today's special, events. Higher delivery rate than KakaoTalk channel broadcasts, and the app icon stays on their phone even if they mute push.
- 02
Hagwon / lesson studios
Class schedules, cancellations, payment reminders go out as push. Parents and students tap the app icon instead of digging through a KakaoTalk room.
- 03
Clinics
Appointment confirmations and pre-visit reminders cut no-shows. Push at recheck time pulls regulars back for follow-up visits.
- 04
Online stores
Cart-abandon nudge, push the moment a sale opens. Re-visit rate and checkout conversion lift together.
- 05
Content sites / magazines
Every new article hits subscribers' phones as a push. You stop depending only on search traffic and get a direct "come back now" channel.
- 06
Heads-up — iOS App Store 4.2 risk
Apps that simply wrap a website can be rejected under Apple's 4.2 review guideline ("the app is just the website"). We say this upfront and give you a pre-flight risk score before you submit.
What happens after you pay
From URL in to store submission and first push out. Do it yourself, or hand the kit to your existing dev / agency.
- 01
Drop in your site URL (free trial)
Just the URL. We build one Android APK so you can sideload it on a phone and see exactly how your site looks inside the app shell — before you pay.
- 02
Starter $19/mo subscription
5 Android + iOS builds per month, push sending, 1 app slot. Builds and pushes for that one site keep flowing under the same plan.
- 03
Upload Firebase + Apple Developer keys (once)
Two keys, registered one time. After that you send push from the dashboard. Step-by-step guide included.
- 04
Build → store submit → push
Android goes to Google Play, iOS to the App Store. Submit yourself, or pass the kit (screenshot specs, 4.2 reviewer-response template) to your agency.
Between full native rebuild
and PWA-only — the pragmatic move
Two fresh codebases (iOS + Android). Every site change requires touching both apps. Quarters pass before you ship.
Your site, wrapped in a native shell. Site updates ship to the app immediately. Push and deep links run native. You only need to clear Apple 4.2.
One URL in,
store-ready app out
Register once and the pipeline — pre-flight → build → push → store — flows end to end.
- 01
Drop in your URL
Three fields: HTTPS URL, app name, reverse-DNS app id (com.brand.app). The pre-flight check returns a 0–100 Apple-4.2 risk score immediately.
- 02
Android & iOS builds
Both Android and iOS dispatch to Codemagic cloud workers. Builds typically finish in 4–8 minutes; the dashboard polls every 3 seconds for status updates.
- 03
Push + store submission
Drop in your FCM service account and APNs .p8 once, then send pushes from the dashboard. Ships with screenshot specs and Apple-4.2 reviewer-response templates.
We can't see your keys
AES-256-GCM vault + HMAC gating
FCM service-account JSON and APNs .p8 keys are encrypted on the elabhub side before they hit the database. They're only briefly decrypted inside a per-build worktree or per-request scope, then destroyed. Every request between elabhub and the build runner is HMAC-SHA256 signed.
- ·AES-256-GCM (96-bit IV, 128-bit tag)
- ·HMAC-SHA256 request signing · 5-min replay window
- ·Each build artifact under an 8-byte random id
- ·Plaintext keys never leave the request scope
The free pre-flight runs once you sign in. No card required to see your risk score.