Key takeaways
- Framer has no app or HTML export, so a Google Play app is always a native Android shell around your hosted Framer site, published from your own Play Console.
- Host assetlinks.json through Framer's well-known files (Pro and above, custom domain). It shows Google that the site in your app is yours and enables verified App Links.
- A Trusted Web Activity is a poor fit: Progressier notes that a service worker can't be added to a Framer site, so offline support has to come from a native wrapper.
- Plan the Play Console path: an AAB targeting API level 36, Play App Signing, internal testing and – for new personal accounts – 12 testers over 14 days before production.
- WebViewGold, made by our team, adds FCM push, offline fallback, App Links and Play Billing; appsubmitter.io runs the Play Console side for you.
Our recommended solution
Turn your Framer app into a real Android app with WebViewGold
WebViewGold wraps the Framer web app you already have in a native Android Studio project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at Google Play look for. Built by our own team, and we submit WebViewGold apps all the time.
Convert Framer to an Android app: does Google Play accept it?
Yes – you can convert Framer to an Android app by wrapping your published Framer site in a native Android project and releasing it from your own Google Play Console. Framer won't produce the app: it hosts websites and offers neither an app export nor an HTML export. Google Play accepts website-based apps when the site is demonstrably yours and the app offers more than the site in Chrome.
That second condition decides most Framer cases. Google's Limited Functionality and Content rule targets apps that are "static without app-specific functionalities", and by its own description Framer is a tool for brand, campaign, editorial and product-marketing sites. A launch page in a WebView won't turn into a useful app. A Framer project with recurring content – an editorial site, a catalog, a members' library, a venue or event program – can, if the Android shell adds what a browser tab can't.
What Google Play checks in a wrapped Framer site
Google Play has no back-and-forth messaging with the reviewer, so the app has to make its case on its own. These are the checks that matter for a Framer site:
| Google's question | How a Framer app fails it | What answers it |
|---|---|---|
| Is the website yours? (Spam policy: Webviews and Affiliate Spam) | The app loads a framer.app address, the developer name doesn't match the site, an agency publishes a client's site under its own account | Custom domain, assetlinks.json, matching developer details, the client's own account or written permission |
| Does it do more than the site? (Limited Functionality) | A landing page in a frame whose main action is a waitlist form | A project with recurring use, plus push, offline pages and App Links |
| Does everything work? (Broken Functionality) | Embedded forms whose upload buttons do nothing, links that open blank screens, a login the reviewer can't pass | File chooser support, link handling, valid sign-in details |
| Is the listing honest? (Metadata, Deceptive Behavior) | Store text copied from the landing page, promising features the app doesn't have | A listing that describes the app, and the same behavior for reviewers and users |
| Is data use declared? (Data safety) | Analytics and marketing scripts in the site's custom code left out of the form | A Data safety form that covers the WebView content you control |
Our WebView spam policy guide and the Broken Functionality guide cover the first and third rows in depth.
Want your Framer app in Google Play without the trial and error?
Book a free consultation call: we check your web app, tell you which native features it needs and what to fix before review. Or hand it off – our App Specialists set up signing and CI/CD, prepare the store listing and submit the app for you.
Verify your domain with Framer's well-known files
- Connect your custom domain on a paid plan. It is the address your app loads, your store listing names and your developer details should match – not the auto-generated
framer.appaddress. - Put the site on Pro or higher. Framer allows well-known files – and Static Files in general – on Pro plans and above.
- Write
assetlinks.json: one statement with the relationdelegate_permission/common.handle_all_urls, the namespaceandroid_app, your package name and the SHA-256 fingerprints – the Play app signing key from Play Console, plus your upload key if you test locally signed builds. - Upload it under Well-Known Files in the site settings, or as a Static File with the path
/.well-known/assetlinks.json, and publish the site. - Verify the link: open the file in a browser, add an App Links intent filter with
android:autoVerify="true"for the domain, then confirm the state on a device (adb shell pm get-app-linksplus your package name) or in the Deep links report in Play Console.
Framer has supported these files for app linking since August 2024, with apple-app-site-association as the iOS counterpart – so one Pro site can serve both stores.
Why a TWA is the wrong shortcut for most Framer sites
A Trusted Web Activity looks tempting: Chrome shows your site full screen, Digital Asset Links prove the connection, and tools such as Bubblewrap generate the Android project for you. But a TWA is built for progressive web apps, and that is exactly where Framer falls short.
- No built-in PWA. Framer documents no PWA feature. Static Files can serve a manifest, and the third-party service Progressier offers a Framer integration that generates one.
- No service worker. Progressier states that with Framer "it's not possible to add a service worker to your PWA". Without one, nothing on the web side can make pages work offline.
- No native features. A TWA displays your site and little else, so on its own it doesn't answer Google's Limited Functionality question.
A WebView wrapper moves those missing pieces into the native layer: an offline screen and bundled pages, native push, App Links and scanning. For a Framer site, that is the practical route to an app Google can approve – and the same approach carries over to the iOS version of your Framer app.
The Play Console path, phase by phase
| Phase | What you do | Framer-specific note |
|---|---|---|
| Account | Sign up as a person or an organization and pay Google's one-time registration fee. Organizations register with a D-U-N-S number; new personal accounts also complete a device check on an Android phone | Use the business name that appears on your Framer site |
| Build | Produce an Android App Bundle that targets API level 36 – required for new apps and updates since August 31, 2026 – and enroll in Play App Signing | The start URL is your custom domain, and app mode is live on the site |
| Internal testing | Install the Play-signed build and read the pre-launch report | Google's test robot doesn't type into login forms rendered by a WebView, so walk through the member flows by hand |
| Closed testing | New personal accounts: at least 12 testers opted in for 14 consecutive days, then apply for production access – Google says that review usually takes seven days or less | Recruit testers from your newsletter or community; many Framer sites already have an audience |
| App content | Privacy policy, sign-in details, Data safety, content rating, target audience, ads declaration | Host the privacy policy and the account deletion page on the Framer site |
| Production | Roll out in stages and keep an eye on crash and ANR rates in Android vitals | Keep publishing content; ship new features with a new version code |
Each phase has its own pitfalls, covered in our guides to closed testing with 12 testers and the target API level requirement.
The shortcut from Framer to Google Play
WebViewGold: your Framer app, native on Android
Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:
- Push notificationsOneSignal or Firebase, for real, personal events
- Native offline screenNo browser error pages when the connection drops
- Native splash screenApp-like start instead of a loading web page
- Deep linksLinks open the right screen inside the app
- QR & barcode scannerDevice features the website alone can't offer
- In-app purchasesNative purchase flows where the store requires them
No tool guarantees an approval: Google still judges what your app offers. Use the native features in your main user journey and keep proving that you own the website – our App Specialists review your WebViewGold app before it goes to Google Play.
Android details that trip up Framer sites
- Animation load on mid-range phones. Android System WebView renders your Framer site, and parallax, scroll reveals and autoplaying videos that run smoothly on a laptop can drop frames on a budget phone. Test on one and reduce motion in app mode.
- Insets. Targeting API 35 and above makes layouts edge-to-edge, so sticky Framer headers can slide under the status bar. Test both navigation modes – gestures and the classic three buttons.
- The back gesture. Predictive back is on by default once you target Android 16. Back should step through the pages people visited and leave the app only from the start page.
- Uploads in embedded forms. File fields stay dead until the wrapper implements
onShowFileChooser. - Notification permission. From Android 13, users grant
POST_NOTIFICATIONSat runtime – ask when someone subscribes to a topic, not at first launch. - Outbound links. Social profiles, calendars and third-party booking tools open in Custom Tabs or the browser, not inside your WebView.
Members, payments and Data safety on Android
Sign-in
Outseta and similar plugins sign members in with email and password, which works inside the app, or with Google, which doesn't – Google's OAuth pages refuse to load in embedded web views (disallowed_useragent). On Android, Google recommends Custom Tabs for this flow; a native implementation with Credential Manager works as well. Either way, test that the member lands back in the app signed in. If people can create accounts, Google requires a deletion option inside the app plus a web page for deletion requests without reinstalling – see the account deletion guide.
Payments
Framer has no native payments, so memberships run through plugins with Stripe behind them. Digital access sold inside an Android app generally needs Google Play Billing, with country-specific alternatives under Google's programs; tickets, reservations and physical goods can keep the Stripe checkout. If you need Play Billing, WebViewGold's Android project includes it.
Data safety
Data collected through a WebView counts when you control the content – and you control your Framer site. List Framer form submissions, member data held by your plugin and whatever your analytics and marketing scripts send. The Data safety guide shows how to audit it.
Build it with WebViewGold – and let appsubmitter.io publish it
WebViewGold is the website-to-app solution built by our own team. For Android, it is a ready-made Android Studio project: enter your Framer domain in the configuration, switch on modules and build. The modules that matter most for a Framer site:
- Push through Firebase Cloud Messaging, OneSignal or Pushwoosh whenever a CMS item goes live
- An offline fallback with reconnect, so a lost connection never ends on a browser error page
- App Links and deep linking on your verified domain
- A custom user agent that switches your site into app mode
- QR and barcode scanning for venues and events, biometric login for members' areas, Google Play Billing, AdMob for ad-funded publications and the native Google Play review dialog
You pay once, own the project and publish in your own Play Console. No Android Studio on your machine? The Cloud Builder, a separate product, produces the build in your browser – or our team does the setup. Whether Google approves the app is Google's decision, and no tool can promise it, but a Framer site with these features is a different proposition from a bare WebView.
appsubmitter.io then runs the Google Play side inside your own developer account: we manage the upload key and Play App Signing, automate AAB builds in a CI/CD pipeline, guide your listing and screenshots, fill in the Data safety form with you, plan the closed test and handle the submission plus any exchange with Google's reviewers. Custom code work is quoted upfront rather than included, and booking doesn't require a finished app. Book the Android service or bring your questions to a free consultation call. Shipping the same Framer site to iOS? Apple looks at other things – above all Guideline 5.6 for Framer apps.
Checklist before you submit
- Your Framer project has a reason to be an app – recurring content, members, events or a catalog.
- The app loads your custom domain, and the developer name, email and website match the site.
- assetlinks.json is published through Framer's well-known files (Pro or higher) with the Play app signing fingerprint.
- App Links verify on a test device, and links from email or social media open the app.
- The AAB targets API level 36, is uploaded with your upload key and uses Play App Signing.
- Animations, sticky elements and the back gesture behave on a mid-range phone running Android 15 or 16.
- Notification permission is requested at a useful moment and tied to content people chose.
- Google sign-in runs in Custom Tabs or natively; account deletion exists in the app and on the web.
- Digital access is sold through Google Play Billing; tickets and physical goods keep their checkout.
- The Data safety form includes Framer forms, plugin data and every analytics or marketing script.
- For a new personal account, at least 12 engaged testers stayed opted in for 14 days before you apply.
Frequently asked questions
Do I need Android Studio to convert Framer to an Android app?
Can I turn my Framer site into a TWA with Bubblewrap or PWABuilder?
Which Framer plan do I need for an Android app?
assetlinks.json through Framer's well-known files – the strongest ownership signal for Google and the basis for verified App Links. Pro sites can also use staging to prepare changes away from live users. Check Framer's pricing page, as plans change.How long does Google Play review take for a new Framer app?
Does Google Play allow apps that are basically a website?
assetlinks.json answers the first part; push, offline pages, App Links and scanning in the main user journey answer the second.Can I keep editing my Framer site after the Android app is live?
Recommended solution
From Framer to Google Play: WebViewGold + appsubmitter.io
- 1 Build with WebViewGold Turn your website into native iOS and Android projects.
- 2 Add native value Push, offline screen, deep links or scanning in your main flow.
- 3 We submit it Our App Specialists submit and talk to the review team.
WebViewGold is made by our team (jocapps GmbH). It is a tool, not a guarantee – approval decisions are made by Apple and Google.
Sources and further reading
- Google Play Policy Center – Spam (Webviews and Affiliate Spam)
- Google Play Policy Center – Functionality, Content, and User Experience
- Play Console Help – App testing requirements for new personal developer accounts
- Play Console Help – Target API level requirements
- Framer Help – Well-known files
- Framer Updates – Static Files (March 23, 2026)
- Progressier – PWA integration for Framer
- Chrome for Developers – Trusted Web Activity overview
Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.