Launching today
Launchplate
Ship iOS & Android apps with your web stack!
7 followers
Ship iOS & Android apps with your web stack!
7 followers
Launchplate wraps any web app (React, Vue, Svelte, or plain JS) into a real iOS and Android app, with the native layer pre-wired: Supabase login (email/Google/Apple), RevenueCat subscriptions and in-app purchases, Firebase push, and a setup script that patches the native projects for deep links and Firebase. You edit two files: your keys and your app! Built for the "last 10%" (the auth deep links, payments, push, and store config that stall every web-to-mobile project).
How does this handle App Store review when the wrapper is mostly webview content? Have you seen any pushback from Apple or Google on apps that are essentially a web shell with native auth and payments bolted on?
@lknur289838 great question! Google Play is a lot more relaxed about this than Apple, I have feedback from friends which published wrapped apps on Play Store with this and they've had no problems so far.
Keep in mind, I haven't personally pushed one through App Store review yet (I've been upfront in the post that live iOS is the one thing I haven't verified on real hardware), so this is from lots of research + how Capacitor works, not from a stack of approvals: the thing you're reffering to (Apple's 4.2) is aimed at apps that are just a repackaged website with nothing native. Capacitor apps that actually use native capabilities (push, native sign-in, in-app purchases, camera, etc.) are generally cleared of it, because that native functionality is exactly what 4.2 wants to see. There are a ton of Ionic/Capacitor apps that are in the store, so the wrapper itself isn't the issue; a thin wrapper with zero native features is the risky case.
Which is honestly part of why the product wires native auth/IAP/push in the first place. The more your app leans on real native features, the safer you are on 4.2. A plain simple webview with only a login and barebones features is what gets flagged. If you have a good app, you'll most likely be fine.
two files and a script handling the auth, payments, and push stuff sounds way too good to be true, but i actually got a react app running on my phone in under an hour without touching xcode. the firebase setup script saved me from the usual config nightmare.
@muhammet0yfj Hahaha, "too good to be true" was exactly the reaction I braced for!
Capacitor just loads your existing web build inside a native shell, so it's not a rewrite, not a new framework. The setup script handles the firebase / gradle / Info.plist native config. It reads the deep-link scheme from one value in your config so you're not hand-editing four files hoping you got it right.
The auth/payments/push side is separate, and honestly pretty simple: each one lives in its own module and only initializes if its keys are in the config. So you pick what you want (leave the RevenueCat key empty and payments just never spins up, same with push.) That's the whole trick!
Really appreciate you taking the time to comment 🙏 happy to go deeper on any of the wiring if you're curious!