Build Tracks

Pick one track for the week. You can switch, but switching after Wednesday should be treated as a scope cut.

Track checklist

• Choose the path
  • Pick Android Native, Expo / React Native, Mobile Web / PWA, or Seeker Feature Spike.
  • Write the Friday proof for that track in your repo.
  • Identify the first command that proves the app runs on Android.
• Scope the demo
  • Define one core user loop.
  • Keep a demo script in the repo.
  • Name the risky integration that could block Friday.
• Protect the fallback
  • Prefer devnet until a mainnet action is necessary.
  • Record a fallback demo video if the app depends on live network conditions.

Android Native

Use this track if you are comfortable with Kotlin, Android Studio, and platform APIs.

• Best for: hardware-adjacent UX, native Android polish, direct SDK usage.
• Friday proof: an installable APK that runs on a phone or emulator.
• Watch out: spending too long on architecture before the wallet flow works.

data class DemoTarget(
    val apkRuns: Boolean,
    val userLoop: String,
    val walletConnects: Boolean,
)

Expo / React Native

Use this track if you want a native app surface with fast iteration and JavaScript or TypeScript.

• Best for: app prototypes, cross-platform teams, UI-heavy demos.
• Friday proof: a custom Android development build with the core flow working.
• Watch out: Expo Go does not support every native module needed for Solana Mobile SDKs.

yarn create expo-app --template @solana-mobile/solana-mobile-expo-template seeker-week-demo
cd seeker-week-demo
yarn android

Mobile Web / PWA

Use this track if your product already lives on the web or you need the fastest UI iteration.

• Best for: existing web apps, content-heavy products, fast product experiments.
• Friday proof: a PWA that runs well on Android Chrome and has an APK wrapping plan.
• Watch out: Android Chrome is the primary mobile web target for Mobile Wallet Adapter.

{
  "display": "standalone",
  "name": "Seeker Week Demo",
  "scope": "/",
  "start_url": "/"
}

Seeker Feature Spike

Use this track if your product depends on Seeker-specific identity, distribution, or ownership.

• Best for: .skr domains, dApp Store discovery, Seed Vault Wallet flows, Seeker Genesis Token gating.
• Friday proof: a narrow proof that the Seeker-specific feature changes the user experience.
• Watch out: do not block the whole app on an integration you cannot test during the week.

Scope rules

• Build one core loop before adding secondary screens.
• Keep a demo script in the repo.
• Prefer devnet until the mainnet action is genuinely necessary.
• Record a fallback video if the demo depends on live network conditions.