What should become an app?
Some sites don't allow previewing here.

A simple, smooth way to create real apps with working features like push notifications, camera and location – without expensive subscriptions or recurring fees.
Works with web apps built in Lovable, Bolt, v0, Replit, Bubble, Webflow, WordPress and Framer – or any mobile-friendly website.
One-time fee – no subscriptions or monthly costs. No account needed to get started – you only sign in when it's time to pay and download your files.
Some sites don't allow previewing here.
Yes. Anything with a published https address works – including web apps built with Lovable, Bolt, v0, Replit, Bubble, Webflow, Framer or WordPress. No need to rewrite anything in React Native: paste the address and you get ready files for Google Play and an iOS project for the App Store. When you update your web app, the changes show up in the app instantly.
No. NativeBundle has no subscriptions and no monthly fees. You pay once per build, and the app keeps working with no ongoing cost to us. You own your files, your source code and your key file.
Yes. Before buying you can see the app in the phone frame and open your site in full screen on the device you're using. After the build you get a finished Android app (APK) that you download and install directly on your phone – the same app that goes to Google Play. For iPhone, Apple only allows test installs through their TestFlight tool, which you reach with your Apple developer account. We explain how.
Important: NativeBundle adds the OneSignal receiver to the Android app when you provide a valid App ID. It does not automatically connect your web app’s events to notifications. You can send manual broadcasts to subscribers from OneSignal without changing your web app. Automatic personal notifications, such as “You have a new message”, require changes to your web app: its server must send the event and notification text through OneSignal, and the app must link the correct signed-in user to the correct phone. This is not included in the NativeBundle build. An App ID, notification permission or existing web push alone is not enough. A web push button on your website may therefore still say “unsupported”; it needs adapting for app notifications. The user must also allow notifications on their phone. For iPhone you additionally need an Apple Developer account, an APNs connection, and OneSignal and push support configured in the iOS project (see README).
The app always shows your website, so changes to text, images and design appear in the app instantly – without a new build or a new store review.
No Mac needed – we build the files for you. You do need your own accounts: Google Play Console (25 USD once) and Apple Developer Program (99 USD/year).
Then you aren't charged. The amount is only reserved on your card and charged once both the Android and iPhone packages are done. If the build fails, the reservation is released immediately.
Yes, if you enable them. The phone always asks the user for permission first, and your website needs to use the features (e.g. image upload or a map).
Yes. Sign in under My apps to download your files again. If Apple or Google raise their technical requirements (e.g. new Android or iOS versions), you regenerate the app here with the latest settings. You keep the same app ID and key file, so the update is uploaded as a normal new version – nothing needs to be recoded. A new build is a new one-time fee, never a subscription.
The app is technically store-compliant, but the stores review the content. You are responsible for your website following their guidelines.