Superhero Wallet: Mobile
On a phone there are three ways to hold an account for Superhero: the Superhero app's built-in wallet, the standalone Superhero Wallet app, and Superhero installed as a PWA.
Two different apps
| App | Stores | What it is |
|---|---|---|
| Superhero — Web3 Communities | App Store (opens in a new tab) · Google Play (opens in a new tab) | The Superhero social app, with a wallet built in |
| Superhero Wallet | App Store (opens in a new tab) · Google Play (opens in a new tab) | The standalone multi-chain wallet, which signs for other æpps too |
To use Superhero, install the first. If you already have an æternity account elsewhere, or you want one wallet across several chains, install the second and connect it.
Install Superhero as a PWA
Superhero is also installable straight from the browser. The installed app gets a home-screen icon, a full-screen experience, an integrated wallet and push notifications.
iOS
Safari only. Chrome and Firefox on iOS cannot install a PWA.
- Open superhero.com (opens in a new tab) in Safari.
- Open the page menu: the ⋯ menu in the top right, or the Share button on older iOS versions.
- Scroll and tap Add to Home Screen.
- Tap Add in the top right. The icon appears on your home screen.
- Launch it from the home-screen icon, not from Safari. The extra capabilities only exist in standalone mode.
Android
- Open superhero.com (opens in a new tab) in Chrome.
- Tap the ⋮ menu in the top right.
- Tap Add to Home screen or Install app.
- Confirm with Install.
- Launch from the home screen.
On desktop, the same install is available from the install button in your browser's address bar.
What changes once it is installed
| Behaviour | Browser tab | Installed app |
|---|---|---|
| Create a built-in wallet (passkey or new phrase) | Yes | Yes |
| Import an existing seed phrase or private key | No, Connect instead | Yes |
| In-page signing by the built-in wallet | Not installed as the signer | Yes |
| Token community chat entry points | Hidden | Shown |
| Location sharing on iOS | Not available | Available |
| Push notifications | No | Yes |
In a browser tab the answer to "I already have a wallet" is Connect, which hands signing to the extension or the wallet app through a redirect and never asks for your secret. A redirect out of an installed app does not come back cleanly, which is why the installed app takes the key directly.
The built-in wallet on mobile
Tapping Connect in the installed app offers a passkey option first. On a phone that means Face ID, Touch ID, a fingerprint or your device PIN, and it creates a real æternity account in one ceremony. There is no seed-phrase screen, because the seed is derived from the passkey rather than stored beside it.
That is a backup only if the passkey syncs (iCloud Keychain, Google Password Manager). There is no phrase reveal or export screen in the app. Enroll the recovery code the flow offers you, and read The Built-In Wallet for what each factor does and does not survive.
Push notifications
Push is standard Web Push (VAPID), opt-in, and enabled from a control in the app. The permission prompt requires a tap, so it never appears on load.
- Exactly one permission is requested: the browser's notification permission. No location, no
contacts, no background-refresh grant. Subscriptions are
userVisibleOnly, so the browser will not deliver a push that does not show a notification. - It can be unavailable through no fault of yours. If the server has no VAPID key configured, the app reports "Browser push is not configured on the server (no VAPID key)" and stops before prompting.
- If the server's VAPID key is rotated, the app detects the mismatch, unsubscribes and re-subscribes rather than leaving you silently unnotified.
The standalone Superhero Wallet apps vs the installed web wallet
Installing wallet.superhero.com to your home screen is not the same as installing the
Superhero Wallet app. An installed PWA is still the web build:
| Installed PWA of the web wallet | Native app | |
|---|---|---|
| Where the seed lives | Site localStorage, encrypted under your password | OS keychain, accessible when unlocked, encrypted with a per-install key |
| Unlock | Password (or none, if you turned protection off) | Biometrics (Face ID, Touch ID, fingerprint) or the device credential |
| Default auto-lock | 5 minutes of inactivity | Immediately |
| In-app dæpp browser | No | Yes |
| QR scanning | Browser camera | Native scanner |
| Ledger over WebUSB | Yes, on Chromium | No |
| AirGap pairing | Yes | Yes |
| Deep links | https://wallet.superhero.com/... only | Also the superhero:// scheme, and universal links on wallet.superhero.com |
| Survives "clear site data" | No | Yes |
The native app is the stronger place to hold value on a phone (keychain storage and biometrics), and the PWA is the convenient one. Neither changes your backup obligation, which is the seed phrase in both cases.
Connecting the standalone Superhero Wallet app
On a mobile browser there are no extensions to detect, so the app uses a deep link. Pressing
Connect tries the superhero:// scheme first; if the native app does not take over within about
1.5 seconds, it falls back to opening wallet.superhero.com. The wallet signs and returns to the
app through the transaction queue route, described in Connecting a Wallet.
Related
- The Built-In Wallet: what the "wallet built in" is, and where its keys live.
- Connecting a Wallet: the deep-link path mobile uses instead of extension detection.
- Choosing a Wallet: built-in versus standalone, decided by recovery model.
- Backup & Recovery: especially the passkey-sync rule.
- Web Wallet: what an installed PWA of
wallet.superhero.comcan and cannot do. - Superhero Wallet on the æternity docs hub (opens in a new tab): the standalone wallet's documentation.