Convert Softr to an Android App: Packaging a Softr Portal for Google Play

Can you convert a Softr app to an Android app?

You can convert a Softr app to an Android app, but Softr won't do it for you. You package the published Softr site yourself – as a WebView app such as WebViewGold or as a Trusted Web Activity – and publish it from your own Google Play Console account. After that, Google's own requirements apply, from website ownership to closed testing.

Softr is clear about its role. Its FAQ says Softr apps are PWAs that "cannot be published to the iOS App Store or Google Play", and that this "applies across all plans". The Android package, its Play Console listing and every policy answer are therefore your responsibility, and Softr's support won't troubleshoot them.

Before you start, ask whether you need Google Play at all. On Android, Softr's PWA (a paid-plan option) installs from Chrome with your icon and splash color and can send browser push notifications. It doesn't work offline and has no Play Store listing, but for an internal tool that can be plenty.

PWA, TWA or WebView: three Android routes for a Softr app

The TWA column hides a Softr-specific catch. A TWA proves that app and site belong together through Digital Asset Links, and if verification fails, Android falls back to a Custom Tab with visible browser UI. That verification needs a file on your domain – check whether your Softr domain setup lets you serve it before you reach for Bubblewrap or PWABuilder. A TWA also inherits the PWA's limits, so it adds neither offline support nor device features.

Want your Softr 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.

Free consultation call Book our service →

Play Console account first: personal, organization or private

A Play Console developer account costs a one-time registration fee. Its type then decides how fast you reach production:

• Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in for 14 consecutive days, then apply for production access. They also verify a physical Android device. Our guide to the 12 testers / 14 days rule has the details.
• Organization accounts need a D-U-N-S number and aren't covered by that testing rule. If a company runs the portal, it's usually the right account anyway.

Softr portals have an edge in closed testing: the future users already exist. Invite client contacts or colleagues who will really sign in a few times a week, hand them a short test plan and ship at least one update based on what they report.

Internal portal? Publish it privately

If the app is only for your company or one client, managed Google Play lets you publish a private app. In Play Console's Advanced settings, the Managed Google Play tab restricts the app to organizations by Organization ID (up to 1,000 per app), and Google says it becomes available in their EMM console within a few minutes of publishing. Permanently private apps are also exempt from Google's account deletion requirement. appsubmitter.io offers MDM consulting if you take this route.

Proving the Softr site is yours under the WebView spam policy

Google Play's Spam policy rejects apps whose primary purpose is to "provide a webview of a website without permission" from its owner. A Softr app is your site even though Softr hosts it – the reviewer just has to be able to see that. Make the connection obvious:

• Use your custom domain, not yourapp.softr.app. Paid Softr plans include one custom domain.
• Match the details: developer name, contact email, store listing website and privacy policy URL all point to the company named on the portal's imprint or About page.
• Link back from your website to the Google Play listing.
• Add Digital Asset Links if you can serve assetlinks.json on the domain – the strongest technical proof.
• Turn off the "Made with Softr" badge (Pro plan and up), so the app doesn't advertise a site builder.

Ownership only gets you halfway. Google's Limited Functionality rule also catches apps that are static and offer nothing app-specific, which is where native push, scanning or offline handling come in. Our WebView spam policy guide covers evidence and appeals.

Building the Softr Android app with WebViewGold

WebViewGold, the website-to-app product our team builds, ships an Android Studio project that you configure with your Softr URL and native modules – or you skip Android Studio with the separately sold Cloud Builder. Work through these points:

1. Choose the package name carefully. It can't change after the first upload, so use your company's reversed domain.
2. Load your custom domain as the start URL.
3. Add push via Firebase Cloud Messaging or OneSignal. On Android 13 and later, apps must request the POST_NOTIFICATIONS runtime permission; ask when users switch on alerts for something specific, not at first launch.
4. Enable the offline fallback with reconnect, since Softr pages don't load without a connection.
5. Test file uploads. Softr forms accept files up to 128 MB, and in an Android WebView, upload fields only work when the app implements WebChromeClient.onShowFileChooser. Try camera and gallery on a real device.
6. Check back navigation. The back gesture should step back through portal pages and leave the app only from the start page.
7. Add device features with a purpose: QR and barcode scanning for stock or check-ins, the document scanner for uploads, biometric authentication for quick re-entry.
8. Set a custom user agent so your pages can hide the PWA install button in the app.
9. Target API level 36. Since August 31, 2026, new apps and updates must target Android 16 – see our target API guide.
10. Build an Android App Bundle (AAB), enroll in Play App Signing and keep your upload key safe.

Google Sign-in, invitations and the reviewer login on Android

Google stopped allowing its OAuth sign-in in embedded WebViews on September 30, 2021, so a Softr app that offers Google Sign-in fails inside a WebView app with a disallowed_useragent error – and Google's policy rules out workarounds inside the WebView. Google's recommended Android routes are Custom Tabs and native sign-in through Credential Manager. Both deliver the result outside the WebView: Custom Tabs keep the session in Chrome, and Credential Manager hands a token to your app code, not to Softr's hosted sign-in.

For a wrapped Softr portal, the practical choice is therefore email and password or an emailed code. If Google sign-in is essential for your users, a TWA is the route where it keeps working, because the pages run in Chrome.

Emailed invitations and Softr's admin magic links open in Chrome unless the app handles them as verified App Links, which again needs assetlinks.json on your domain. Without it, tell invited users to open the app and sign in with their email.

For review, enter sign-in details under App content > App access in Play Console. Google expects them to be reusable and valid at all times, so give each Softr user group a password login instead of a one-time code, and describe which pages each account sees. Never give reviewers a different version of the portal than users get – Google's Deceptive Behavior policy expects the same behavior for both.

Data safety, account deletion and payments for a Softr app

Data safety

The Data safety form covers what your app collects – including pages in a WebView whose code you control, which is exactly what a Softr portal is. List user profiles, form entries, uploads and what your data sources (Softr Databases, Airtable, Supabase and the like) store about users, plus SDKs such as Firebase or OneSignal. Our Data safety guide shows how to audit it.

Account deletion

If users can create an account, Google requires a way to request deletion inside the app and on a web page whose URL goes into the Data safety form. A public Softr page with a deletion request form can serve as that web resource if it loads without signing in, names your app and leads to real deletion rather than deactivation. Details: Google Play account deletion requirement.

Payments

Stripe Checkout and PayPal are fine for physical goods and services. Digital goods and subscriptions sold in the app generally need Google Play Billing, which WebViewGold supports with the Extended license. Some countries allow alternative billing, so check the current rules for your markets.

From the first AAB to production

1. Upload the AAB to internal testing and check the pre-launch report for browser error pages and crashes.
2. Complete App content: privacy policy, App access, content rating, target audience, Data safety.
3. Prepare the store listing with screenshots of the app – no browser bars, no desktop layouts.
4. Run the closed test if your personal account needs one, then apply for production access with concrete feedback and fixes.
5. Release to production, ideally as a staged rollout, and watch Android vitals.

appsubmitter.io runs this Play Console side for you: a CI/CD pipeline that builds signed AABs, the upload key and Play App Signing, the listing, the Data safety form, the closed-test plan and the communication with Google's review team – all in your own developer account. Book the Android package or start with a free consultation call. The iPhone side is covered in converting Softr to an iOS app, and our Softr 5.6 article explains why user groups need care in any review.

Checklist before you submit

• Your account type is clear: organization, personal with a closed test, or private distribution through managed Google Play.
• The app loads your custom domain, and developer name, contact email and website match it.
• You chose WebView or TWA deliberately, and a TWA verifies the domain via assetlinks.json.
• Users sign in inside the app with email and password or an emailed code.
• Push uses FCM or OneSignal and asks for POST_NOTIFICATIONS at a meaningful moment.
• File uploads from Softr forms and the back gesture work on a real device.
• The AAB targets API level 36 and uses Play App Signing.
• Data safety answers cover Softr pages, data sources and SDKs.
• Account deletion works in the app and through a public web page listed in Play Console.
• Reusable reviewer logins for each user group are entered under App access.

Frequently asked questions

Sources and further reading

• Softr Docs – FAQ: mobile publishing is not supported
• Softr Docs – How to create a mobile app (PWA) from a Softr app
• Play Console Help – App testing requirements for new personal developer accounts
• Google Play Policy Center – Spam (Webviews and Affiliate Spam)
• Play Console Help – App account deletion requirements
• Managed Google Play Help – Publish private apps
• Android Developers – Trusted Web Activities
• Google Developers Blog – OAuth changes for embedded webviews (2021)

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.