The authentication challenge — and why Capacitor solves it
Most Softr apps use password login, magic link, or SSO to gate content. In a standard Trusted Web Activity (TWA), session cookies are shared with Chrome's browser storage — which can cause sessions to expire unexpectedly when the app is backgrounded on certain Android versions.
SaasToStore's Capacitor mode solves this with a persistent, isolated WebView that maintains its own cookie store. Users log in once and stay logged in across app launches — exactly the behavior your Softr clients expect from a native app.
Why Softr apps pass Play Store review
Google's policy 4.3 rejects apps that provide minimal functionality — essentially blank webview shells with no real content. Softr apps are the opposite: structured data from Airtable or Google Sheets, role-based access, filtered views, forms, and real workflows. Reviewers see a functional product, not a wrapper.
The key is your store listing. Screenshots should show the app in use with real data — client portal dashboards, directory listings, form submissions — not empty states or placeholder content.
Before you start — what you need
- Your Softr app's published HTTPS URL (custom domain strongly recommended)
- A Google Play developer account (25 € one-time, 24–48h verification)
- A 512×512 px icon PNG — or use SaasToStore's AI icon generator
- A privacy policy URL (SaasToStore can auto-generate a GDPR-compliant one)
- At least 2 phone screenshots showing your Softr app with real content
- A 1024×500 feature graphic (no device mockups, no store badges)
Step 1 — Check your Softr app's PWA compatibility
Run a free PWA scan on your Softr URL. For apps with authentication, the scanner will flag cookie management considerations and recommend the appropriate build type.
→ Run the free PWA check on your Softr URL
Step 2 — Set up your Google Play developer account
Navigate to play.google.com/console, sign in with a Google account, and pay the one-time 25 € registration fee. Google verifies your identity within 24 to 48 hours. Start this step in parallel with your build.
com.yourcompany.portalapp). This ID is permanent after the first upload and appears in your app's Play Store URL.Step 3 — Build your signed Android App Bundle
SaasToStore generates a 2048-bit RSA keystore, compiles your Softr URL into a signed .aab, and emails you the artifact with an encrypted keystore backup.
Paste your Softr URL
Configure app identity
com.acme.clientportal.Upload your icon
Launch the build
Step 4 — Configure your Play Store listing
For Softr apps, the listing is especially important. Be specific about what your app does — "client portal for [industry]", "directory of [niche]", "internal tool for [use case]". Vague descriptions increase rejection risk.
- Store listing — Short description (80 chars), full description (4,000 chars), screenshots (min. 2 phone showing real data), feature graphic (1024×500)
- Content rating — IARC questionnaire (~5 minutes). Select the appropriate audience for your Softr app
- Data safety form — Declare what your app collects. Softr apps with login collect email addresses — declare this and link to your privacy policy
Step 5 — Upload and submit
In the Play Console, go to Production → Releases → Create release. Upload your .aab. Submit for review. First-time reviews take 1 to 3 business days. Subsequent updates are processed within 24 hours.
After launch — live data and updates
Your Softr app's data — Airtable records, Google Sheets rows, user submissions — is always live. Add a new record in Airtable and it appears in the app within seconds. No rebuild. No Play Store review.
Design changes in Softr (new blocks, updated colors, new pages) also reach users immediately. Only structural app changes (new icon, new package name, new permissions) require a new .aab build.
With the LAUNCH plan, the same pipeline generates a Windows .msi, macOS .dmg, and Linux .AppImage from your Softr URL — plus Amazon Appstore and Samsung Galaxy Store slots.