Sanvio for Android
Download the signed native 2.0 beta from the Sanvio download page. Open it from Downloads, approve installation from that source when Android asks, and open Sanvio.
Android versions
The native 2.0 beta requires Android 9 or later. It uses Android screens, a native chart, dedicated trading forms and a Rewards tab. Google sign-in opens the provider's browser handoff. The main native workspace uses Kotlin and Jetpack Compose screens.
The previous hosted 1.0 APK remains available for existing installations, including Android 8 devices. It opens the web workspace and depends on the device's available browser version.
The native client shares the same verified account and transaction services. Sign into the same account to access its wallets. Google sign-in uses the provider's browser handoff. Private key import/export uses a separate secure wallet window with account verification; private keys are not sent to Sanvio's API. The main native workspace does not open the website as its app interface.
Native NEAR capabilities are enabled separately. Supported signing paths still require a fresh owner-specific review and the provider's supported verification methods. A closed integration keeps its history and checks available. App installation and interface checks do not establish Google/MFA completion, every external wallet handoff or funded settlement.
Native beta status and updates
Install version 2.0 over an existing Sanvio installation. Both releases use package xyz.sanvio.app and the same signing certificate. Sign in to the same Sanvio account after updating; a browser session does not automatically become a native session. Wallet and transaction records remain tied to the verified account in the shared services.
Interface checks have passed. Complete native Google sign-in, provider MFA and funded settlement still need acceptance verification. Native limit/TP-SL execution is still being integrated. Supported actions and current integration availability are shown in the app; the website has its own supported execution paths. Rewards displays Coming soon and has no active reward claim contract.
Previous hosted 1.0 accounts and features
The public 1.0 APK opens the hosted workspace and uses the same Privy application and server profile. Sign into the same account to access your recorded wallets and activity. The web release's supported assets, venues, transaction limits and provider availability also apply to that release.
The installed Android view hides Android download promotions in the navigation and landing page. If you open the download address inside the app, Continue to your workspace returns to the terminal. Ordinary browser visits keep the APK download links. This display choice grants no wallet or account permissions.
Connection requests for an external wallet share its public address; they do not authorize trading. Mobile Solana connections can use Mobile Wallet Adapter through Privy's picker. EVM connections use supported Privy connectors. MyNearWallet opens its existing wallet site and returns through the wallet callback flow. Installed-wallet support can differ by browser and wallet version.
Previous hosted 1.0 device compatibility
The hosted 1.0 APK requires Android 8.0 or later. Current Chrome releases require Android 10 or later. Android 8/9 can use their available compatible browser versions; those devices do not receive current Chrome releases. Installation compatibility does not guarantee every browser/wallet combination supports current authentication and cryptography.
If the app opens with a browser toolbar, website/app verification or fullscreen browser support was unavailable. The official HTTPS site remains accessible. Keep the browser updated where supported.
On supported Android browsers, Back first dismisses the on-screen keyboard. A further Back closes the login dialog and keeps the app open. The app preserves normal page history. The CloseWatcher path and older-browser history fallback have been verified on the Android 17 emulator; physical-device login, MFA and installed-wallet acceptance remain outstanding.
Connection and interrupted transactions
Internet is required for login, current prices, quotes and transactions. The offline screen only helps reconnect. Private account responses, prices and transaction requests are not saved in the service worker's offline cache.
When a wallet request is interrupted or the app closes, check Activity and the transaction's recorded status before repeating it. Existing nonce, hash and one-send recovery rules remain in effect. Closing the APK does not grant the server a new signing permission. Browser-closed orders still require the supported explicit owner authorization.
Authentic downloads and updates
The download page lists the exact version, APK SHA-256 checksum and app signing certificate. A future APK update must use the same package and certificate. Website updates become available through the hosted workspace. Native Android interface changes require an APK update; current data and server integrations use the shared service.
The Android application signing key is separate from your blockchain wallet keys. Installation never requires your seed phrase, private key or API credentials.