Publishing

You do not need to submit to the dApp Store during Seeker Week. You should leave with a clear publishing path.

Publishing checklist

• App metadata
  • Draft the app description.
  • Prepare the app icon, screenshots, and preview assets.
  • Review the Publisher Policy and Developer Agreement.
• Publisher readiness
  • Create or confirm the publisher account.
  • Complete KYC or KYB.
  • Fund the publisher wallet for fees and upload costs.
• APK readiness
  • Choose the APK build path for your app type.
  • Build a release-ready APK.
  • Sign the APK with your release key.

App submission checklist

Before submitting a new app, prepare:

• App description, icon, screenshots, and preview assets.
• Publisher account and completed KYC or KYB.
• Publisher wallet with enough SOL for fees and upload costs.
• Release-ready APK signed with your release key.
• Reviewed Publisher Policy and Developer Agreement.

APK paths

App type	Path
Android native	Build and sign a release APK from Android Studio or Gradle
Expo / React Native	Build a release APK locally or through EAS
Flutter / Unity / Unreal	Build and sign the Android release artifact from that toolchain
Mobile Web / PWA	Wrap the PWA in a Trusted Web Activity with Bubblewrap, then sign the APK

PWA to APK outline

For web apps, the dApp Store path is PWA to Trusted Web Activity to signed APK.

npm install --global @bubblewrap/cli
bubblewrap init --manifest https://your-site.example/manifest.json
bubblewrap build

Keep the generated signing key safe. If you lose the release key, you cannot publish updates for that app with the same package identity.

Friday publishing note

Add this to your demo README before the final walkthrough:

## Publishing path

- APK build command:
- App type:
- dApp Store blockers:
- Next submission step:
- Signing status:

Review expectations

After submission, the app enters review before it appears in the dApp Store. Plan time after the workshop for review feedback, metadata cleanup, and follow-up releases.