One codebase, real store app
The Android app loads your published Blink.new URL inside a native WebView. There is no second project to maintain and no code export.
Why wrapping beats rebuilding for Blink.new apps
Blink's native route starts from a separate React Native + Expo template chosen with the first prompt, so turning a finished Blink web app into a store app that way means building a second project with its own screens. WebViewGold wraps the production URL you already have and keeps Blink Auth, the Turso database and Stripe exactly as they are. Publish in Blink and the installed apps show the update on the next launch.
Keep shipping from Blink.new
Click Publish in Blink and production updates in under a minute; the app shows the new version on the next launch. Changes that only exist on the preview never reach the app. Only changes to the native shell itself (icon, new native feature) need a store update.
Native features on top
Push notifications, offline screen, native sharing, biometric login, QR scanner, in-app purchases and deep links are single settings or one-line JavaScript calls.
Google Play approval guarantee
Google Play Store approval guarantee – or your money back within 14 days. 96.4% of all WebViewGold apps get approved by the review teams on the first attempt.
What you need
- A published Blink.new app on a public HTTPS URL (yourapp.blinkpowered.com or, better, your own domain)
- An Google Play Console developer account ($25 one-time) to submit to the Google Play Store
- Android Studio on Windows, macOS or Linux – or the WebViewGold Cloud Builder in your browser
- WebViewGold for Android ($109 one-time, free updates)
- A privacy policy page, a 1024 × 1024 px icon and 30 to 60 minutes
Great work! Never coded anything but managed to work with this. Easy and fast! Also with great help from the creators!
Blink.new to Google Play: the walkthrough
Eight steps, no coding. Most people finish the native part in under an hour.
Publish your Blink.new app to a production URL
Every project gets a preview at yourapp.sites.blink.new that changes with each save. Click Publish (top right of the editor) to push the active version to production at yourapp.blinkpowered.com; production hosting needs the Starter plan or higher. The yourapp.sites.blink.new preview updates with every save and is not a permanent production environment. Never put it into your app: publish to blinkpowered.com or your custom domain. Custom domain: On Starter or higher, open Workspace, Domains, click Add Domain, add a CNAME record pointing to cname.blink.new at your DNS provider and click Check Status (or buy a domain inside Blink). SSL is issued automatically and the blinkpowered.com address stays active as a backup. See why a custom domain before submission is worth it.
Make it store-ready
Add a privacy policy page, an account deletion option (if users can sign up), and remove builder badges or "download our app" banners. Run the free Google Play readiness check on your URL: it flags mixed content, missing viewport tags, builder preview domains and other blockers in seconds.
Get WebViewGold for Android
One-time payment, free updates. You receive the ready-made Android Studio project, or activate the WebViewGold Cloud Builder and skip the IDE entirely.
Insert your URL and brand the app
Open Config.java (or the Cloud Builder form), paste your published URL, set the app name, choose your package name, upload the icon and pick the splash screen. No coding needed.
Switch on native features
Enable push notifications, the offline screen, pull-to-refresh, biometric login, the QR scanner or App Links with single settings. Everything is optional.
Build the signed App Bundle
In Android Studio: Build → Generate Signed Bundle. In the Cloud Builder: click Build and the signed .aab is prepared and uploaded for you.
Create the Play Console listing
Create the app in the Play Console, fill in the store listing, upload icon, feature graphic and screenshots, complete Data safety, content rating and app access.
Test, then submit
New personal accounts run a 14-day closed test with 12 testers first. Then promote the release to production and submit for review. Our approval guarantee covers you.
Blink.new-specific checks before you submit
These are the points that come up most often with Blink.new projects (React + Vite + TypeScript + Tailwind CSS + shadcn/ui for web apps, a Hono backend at the edge and a Turso (SQLite) database, with Supabase as an optional Postgres alternative).
- Blink builds native apps from a separate React Native + Expo template that you pick with your first prompt, and its App Store and Google Play publishing needs the Max plan. If your product is a Blink web app, wrap the published URL instead of starting a second project.
- Google sign-in from Blink Auth is blocked inside an embedded WebView ("disallowed_useragent"). Enable WebViewGold's Social Login Helper for the Google step; Sign in with Apple is detected and handled automatically.
- Magic-link emails open in the phone's browser, not in your app, unless you set up Universal Links (iOS) and App Links (Android) in WebViewGold. Give the reviewer a demo account with a password so review does not depend on an inbox.
- Connect your custom domain before you submit. The blinkpowered.com address keeps working as a backup, but your own domain is the one to use for the app URL and for Universal Links and App Links.
- Add a privacy policy page and an in-app account deletion action before you submit; both stores ask for them when users can sign up.
- Made with Blink: Blink apps show a small "Made with Blink" badge in the corner by default. On a paid plan, open Workspace Settings, Overview, Privacy & sharing and switch on Hide "Made with Blink" badge before you build the app. More on builder badges.
Let Blink.new do the store-readiness work
Paste this into Blink.new and let it apply the changes reviewers look for. Review the result, then publish.
Prompt to paste into Blink
Prepare this web app for publishing as a native iOS and Android app (it will run inside a native WebView wrapper that loads the published URL): 1. Add /privacy and /terms pages with editable placeholder text and link them from the footer and the account settings. 2. Add a "Delete my account" action in the account settings that deletes the user's data and Blink Auth account after a confirmation dialog. 3. Make sure email and password login is enabled next to magic links, so a test account can sign in without an inbox. 4. Make every page responsive from 320px to iPad widths, with no horizontal scrolling and tap targets of at least 44px. 5. Remove "Download our app" banners and external promotional links from the main navigation. 6. Show a friendly retry state when a request fails instead of an empty screen. 7. Set the <title> to the app name (max 30 characters) and add a meta description.
Google Play review: the rules that matter for Blink.new apps
Google reviews behavior, not tooling. Nobody is rejected for using Blink.new; apps are rejected for the points below.
- Minimum functionality
Spam and minimum functionality policy
Google rejects apps that only wrap a website without the website owner's permission or that offer no real functionality. Wrapping your own product with added native features is fine.
- Data safety
User Data policy
Every app needs a privacy policy URL and a completed Data safety form that lists what the app and its SDKs collect.
- Account deletion
User Data policy
Apps that let users create accounts must offer account deletion inside the app and via a web link you provide in the Play Console.
- Testing requirement
Personal developer accounts
Personal accounts created after November 2023 must run a closed test with at least 12 testers for 14 continuous days before they can request production access.
- Target API level
Target API requirements
New apps must target a recent Android version. WebViewGold updates keep the template current; just build with the latest version.
- Payments
Google Play Billing
Digital goods and subscriptions sold in the app generally must use Google Play Billing (WebViewGold supports RevenueCat). Physical goods and services may use other payment methods.
Native features your Blink.new app gets in the Android app
Every feature is optional and documented step by step in the WebViewGold for Android documentation.
Push notifications
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call.
DocumentationApp Links and deep links
https links to your domain and custom schemes open directly in the app.
DocumentationIn-app purchases
Google Play subscriptions and one-time purchases via RevenueCat, triggered from your web app.
DocumentationOffline screen and fallback
A native "Try again" screen when the user is offline, or a local HTML fallback.
DocumentationSplash screen and loading indicator
Minimum and maximum splash duration with fade-out, or a native spinner while loading.
DocumentationBiometric login
Fingerprint / face unlock gate from a JavaScript call.
DocumentationQR and barcode scanner
Native scanner that returns the result to your web app.
DocumentationNative share and haptics
Share intent and haptic feedback from your web app.
DocumentationCustom CSS and JavaScript
Hide website-only elements and inject code when loaded inside the app.
DocumentationFile and camera uploads
Native file picker and camera for your upload forms.
DocumentationPre-flight checklist for Google Play
Tick these off and the review is a formality. The free readiness check verifies the technical half automatically.
- HTTPS everywhere: Android blocks cleartext http:// traffic by default on current versions.
- Responsive layout from 320 px to tablet widths, with predictable back-button behavior (WebViewGold maps the back button to the web history).
- Privacy policy URL ready and the Data safety form answered truthfully.
- Account deletion inside the app plus a web deletion link if users can sign up.
- App access credentials for the reviewer if content is behind a login.
- A unique package name (for example com.yourcompany.yourapp) set before the first upload: it can never change afterwards.
- A 512 × 512 px icon and a 1024 × 500 px feature graphic.
- At least two phone screenshots taken from the real app (tablet screenshots recommended).
- For new personal accounts: 12 testers lined up for the 14-day closed test.
- Signed Android App Bundle (.aab) built from the latest WebViewGold version.
Example: from Blink.new project to approved app
Say you built an event companion for a regional tech conference with Blink: attendees sign in with Apple or Google, see the agenda and their personal schedule, and show a ticket QR code at the entrance. Tickets are sold on the conference website through Stripe, which is fine because they pay for a real-world event. You publish to production, connect app.yourconference.com and wrap it with WebViewGold. At the door, staff open the check-in page and scan tickets with qrcode://; each code encodes a check-in URL that opens inside the app. A OneSignal push announces room changes during the day. The demo attendee in the review notes holds one ticket, both stores approve the app, and every Publish in Blink reaches it on the next launch.
Your first week after launch
- Publish fixes from Blink and check them on your own domain, not on the sites.blink.new preview, which the app never loads.
- Keep the plan that includes production hosting active; the app depends on blinkpowered.com or your domain staying online.
- Test the ticket scan with the phones your staff will use, at the venue entrance, a day before the event.
- Send pushes for room changes and session starts only; attendees switch notifications off when every sponsor message gets one.
- Ask for a rating with rateapp:// after the last session of the day, when attendees have used the app the most.
What you get with WebViewGold
A complete native app project, not a subscription. Everything below is included in the license and switched on with a setting.
- Complete Android Studio project
- Push notifications
- Offline screen
- App icon & splash screen
- Share sheet & haptics
- Deep & universal links
- In-app purchases
- Free updates, white-label
Frequently asked questions
Can a Blink.new app be published in the App Store and on Google Play?
Yes. Publish the web app to production, enter the blinkpowered.com address or your custom domain in WebViewGold and build both apps. Do not use the free sites.blink.new preview: it changes with every save and is not meant as a permanent address.
Blink can build React Native apps. Should I rebuild my web app as a mobile project?
Only if you want two codebases. Blink's mobile route starts from its own React Native + Expo template and needs the Max plan for store publishing. Wrapping the web app you already published keeps one project, one backend and updates that go live without a store review.
Do I need Android Studio?
Either Android Studio (free, runs on Windows, macOS and Linux) or the WebViewGold Cloud Builder, which builds and uploads the signed App Bundle from your browser.
What is the 12-tester rule?
Google requires personal developer accounts created after November 2023 to run a closed test with at least 12 opted-in testers for 14 continuous days before the first production release. Friends, colleagues or a Discord community are enough; organization accounts are exempt.
What if Google rejects the app?
Google names the policy in question and you can fix and resubmit. WebViewGold comes with a Google Play approval guarantee: if Google rejects the app for a non-content reason, you get your money back within 14 days of purchase.
Blink Auth offers Sign in with Apple. Do I need it in the iOS app?
If your login screen shows Google, GitHub or Microsoft, yes: Guideline 4.8 asks for an equivalent option that limits data to name and email and lets users hide their email, and Sign in with Apple is the safe way to provide it. An app that only uses email and password or magic links does not need it. WebViewGold detects the Apple sign-in page and handles it automatically.
Can I stay on Blink's free plan for the store app?
Not for production. Free projects only have the sites.blink.new preview, which changes with every save and is not meant as a permanent address; production hosting on blinkpowered.com or your own domain needs the Starter plan or higher. Hiding the Made with Blink badge also needs a paid plan, so plan the upgrade before you build the app.
Do I have to resubmit the app every time I change something in Blink.new?
No. The app loads your published URL, so content and feature changes you publish in Blink.new are live in the app immediately. A new store version is only needed when the native shell changes, for example a new app icon or an added native feature.
What does it cost in total?
$109 one-time for WebViewGold for Android (free updates) plus the Google Play Console developer account ($25 one-time). Optional: the Cloud Builder add-on ($349 per license, one-time) if you want to build in the browser without a Mac, or the Full Service package (from $698 per platform) where our team configures, builds and submits the app for you.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.