We have six apps of our own on the Solana dApp Store. Most of them started as web apps. Wrapping a web app into an Android app is now the easy part: Solana Mobile ships a free tool that does it in one command. What takes the time is everything that behaves differently once your site runs inside an app on a real Seeker. This post is the list we wish we'd had.
The wrap itself is one command
Solana Mobile's CLI builds a WebView shell around your site and signs an APK:
npx solana-mobile@latest webshell init my-app --manifest https://your-app.com/manifest.json
npx solana-mobile@latest webshell build my-app
init reads your web manifest for the name and icons and creates a signing keystore if you don't have one. build produces app/build/outputs/apk/release/app-release.apk. Solana Mobile now recommends this WebView shell over a Trusted Web Activity (the older Bubblewrap route): the shell needs no Digital Asset Links setup, and it handles Solana wallet requests natively, while browser network restrictions can break wallet connections inside a TWA.
If your app uses Mobile Wallet Adapter through @solana-mobile/wallet-standard-mobile, update it to 0.5.1 or later so it detects the shell.
So far, so quick. We tried it on a live dApp that offers Google sign-in, and on a Seeker it loaded perfectly. Then we tapped "Continue with Google".
1. Google and other social log-ins leave the app and never come back
In the shell, any link outside your app's own host opens in the system browser. That is the right default: it keeps unknown sites out of your app. But a Google sign-in is exactly such a link. What we saw on a Seeker:
- The user taps "Continue with Google".
- Chrome opens Google's account chooser. The user picks an account in Chrome.
- The sign-in finishes in Chrome, not in the app. Back in the app, the page sits on "Logging in…" forever.
You can't fix this by keeping the Google page inside the WebView: Google blocks its sign-in in embedded WebViews. The fixes that work:
- Bring the result back to the app. Open the sign-in in a Custom Tab and have it return to the app through a deep link or an Android App Link, which your auth provider must accept as a redirect. This is native work in the shell, not a web change.
- Make the wallet the main sign-in on Seeker. Every Seeker has a wallet (Seed Vault). Sign In With Solana through Mobile Wallet Adapter opens the phone's wallet to approve and comes straight back to your app, and for crypto users it is the expected way in. Keep e-mail sign-in as the fallback: a one-time code typed into the app doesn't need the browser.
If your web app only offers Google and e-mail, test this first. It's the difference between a working app and one that loses every Google user at the door.
2. Pop-ups and new tabs go to the browser too
The same rule applies to window.open and target="_blank". Pay-with-card widgets, on-ramps, "share on X" buttons and help-desk chats often open that way. Some of that is fine (a share link should open X). Some isn't: a payment window that completes in Chrome leaves your app not knowing it happened. Go through every flow that opens something and decide: in the app, or out with a way back.
3. Wallet connections: test on the device, not in a desktop emulator
Wallet behaviour is the part desktop testing can't show. On a Seeker, check:
- that connecting picks up the phone's wallet without a QR code or a browser hop;
- that signing a transaction and a message both return to the app;
- that a declined signature is handled, not left spinning;
- that the app still works after the phone locks during a signature.
4. Things that make the app feel like a website
- Back button. Android's back button should go back in your app's history and only leave the app on the first screen. Check it on every screen, including modals.
- Start page. Point the app at your app's main screen (
/play,/app), not your marketing home page. - Splash, icon and status bar. Generated from your manifest; a white
theme_coloron a dark app shows as a white bar. - Your site is live. The shell loads your live site, so web changes reach users without a new APK. That also means a broken deploy breaks the app instantly.
5. Publishing details that catch teams out
- The publisher account is yours, with an identity check. The dApp Store publisher portal asks for KYC (a person) or KYB (a company) before you can add an app. Have the person or company that should own the app do it.
- Keep the signing key forever. Every update must be signed with the same key. Lose the keystore or its passwords and you can't update the app. Use a different key from your Google Play one if you're on both.
- The package name is permanent. Choose it once, like
com.yourteam.app. - Every update needs a higher version code. In the shell, edit
SOLANA_MOBILE_VERSION_CODEingradle.propertiesand rebuild. - Review time. Solana Mobile quotes 3 to 4 business days for a new app and 1 to 2 for an update. The store takes no commission.
A checklist before you submit
- Every sign-in method works on a real Seeker and returns to the app.
- Wallet connect, sign transaction, sign message and decline all work.
- Every link or pop-up that leaves the app is one you meant to leave.
- Back button behaves on every screen.
- Icon, banner, screenshots and description are ready.
- Keystore and passwords are backed up in two places.
If you'd rather not
This is the work we do for other teams: the wrap, the sign-in and wallet fixes, real-device testing, the store listing and help through the publisher portal, published under your own account. Prices start at US$750; see our services page.