Seeker Context

Seeker is Solana Mobile’s flagship Android device. You do not need a Seeker in hand to build for it; testing on a regular Android device or emulator is enough for most workshop prototypes.

What makes Seeker different

• .skr domains: human-readable names mapped to Solana wallet addresses.
• dApp Store: a crypto-friendly app store for Android apps and web apps packaged as APKs.
• Mobile Wallet Adapter: the wallet connection layer for Android apps and compatible Android Chrome web apps.
• Seed Vault: hardware-protected key custody on Solana Mobile devices.
• Seeker Genesis Token: an NFT minted once per device as proof of verified Seeker ownership.

Mobile Wallet Adapter mental model

On desktop, users usually connect through browser extension wallets. On mobile, the app and wallet are separate apps on the same device. Mobile Wallet Adapter creates the local session between them so the dApp can request authorization, message signing, transaction signing, and transaction sending.

dApp -> MWA request -> wallet approval UI -> signed response -> dApp

Product prompts

• Can the core action happen comfortably on a phone?
• Does Seeker ownership change what the user can do?
• Is wallet signing part of the product instead of a bolted-on checkout step?
• What is the smallest useful loop a participant can demo in under two minutes?

Technical prompts

• Decide whether your first version is native Android, React Native, Expo, Flutter, Unity, Unreal, or PWA-to-APK.
• Keep the signing flow obvious and reversible.
• Test on a real Android device or emulator before optimizing for Seeker-specific polish.
• Write down your publishing path before the demo, even if you do not submit during the week.