Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(play): add the Google Play submission kit, listing copy and the account-type timeline

nirholasf07fb54b0613
diff --git a/solana-mobile/README.md b/solana-mobile/README.md
index 8cb77546d..63ef2b87e 100644
--- a/solana-mobile/README.md
+++ b/solana-mobile/README.md
@@ -1,6 +1,8 @@
-# `solana-mobile/`: three.ws on the Seeker dApp Store
+# `solana-mobile/`: the three.ws Android app
-Everything needed to package three.ws as a Solana Mobile (Seeker / Saga) app and publish it to the Solana dApp Store: the Mobile Wallet Adapter (MWA) wallet that signs through the on-device Seed Vault, the Trusted Web Activity (TWA) wrapper, the release pipeline, and the listing copy for the Publisher Portal.
+Everything needed to package three.ws as an Android app and publish it: the Mobile Wallet Adapter (MWA) wallet that signs through the on-device Seed Vault, the Trusted Web Activity (TWA) wrapper, the release pipeline, and the listing copy for both stores.
+
+**One package id, two channels.** `ws.three.app` ships to the Solana dApp Store (Seeker and Saga, listing copy in `publish/`) and to Google Play (every Android phone, listing copy and submission runbook in [`publish-play/`](publish-play/README.md)). Same build, same app, two store listings that must describe the same product. The Play path has one trap with no local symptom, and it is documented in `publish-play/README.md` step 6: Play re-signs the bundle with Google's own key, so Google's certificate fingerprint has to be added to `twa/extra-fingerprints.json` or every Play install loses full-screen mode.
## Layout
@@ -14,16 +16,22 @@ solana-mobile/
│ ├── mwa-errors.js # normalizes MWA errors (user decline -> code 4001)
│ ├── index.js # single-import boot; sets window.solana when on Seeker
│ └── package.json # declares MWA peer/runtime deps
+│ └── extra-fingerprints.json # certificates OTHER than our keystore that may sign the app
├── scripts/
│ ├── setup-android-sdk.sh # headless machines: stage JDK 17 + Android SDK for Bubblewrap
│ ├── build-apk.sh # generate keystore (if needed), build + sign release APK
+│ ├── assetlinks.mjs # build the Digital Asset Links file from every signing certificate
│ ├── make-media.mjs # generate icon/banner/feature listing assets from the live product
│ ├── update-assetlinks.sh # refresh /public/.well-known/assetlinks.json from the keystore
│ └── publish.sh # upload the APK to the Publisher Portal (dapp-store-cli 1.x)
-├── publish/ # Publisher Portal worksheet + listing copy + media
+├── publish/ # Solana dApp Store: Publisher Portal worksheet + listing + media
│ ├── config.yaml # every value the owner enters in the portal, in one place
│ ├── listing/ # description, short description, what's new, Seeker features
│ └── media/ # icon, banner, feature graphic (screenshots need a real Seeker)
+├── publish-play/ # Google Play: submission runbook, worksheet, listing, declarations
+│ ├── README.md # the account-type decision that sets the timeline, then the steps
+│ ├── config.yaml # every value the owner enters in Play Console
+│ └── listing/ # title/short/full copy, data safety, content rating, financial features
└── docs/
├── ASSETS.md # exact pixel specs for icon/banner/screenshots
├── CHECKLIST.md # end-to-end submission checklist with verification dates
diff --git a/solana-mobile/publish-play/README.md b/solana-mobile/publish-play/README.md
new file mode 100644
index 000000000..d9672caea
--- /dev/null
+++ b/solana-mobile/publish-play/README.md
@@ -0,0 +1,86 @@
+# `publish-play/`: three.ws on Google Play
+
+Everything the owner types or uploads into Play Console, kept in git so the console never
+drifts from what was reviewed. The Solana dApp Store worksheet is next door in
+[`../publish/`](../publish/); this is the Play twin of it.
+
+**One app, one package id, two channels.** `ws.three.app` is the same APK content on both
+stores. Do not fork the package name, and do not let the two listings describe different
+products.
+
+## The one decision that sets the timeline
+
+Everything else here is a checklist. This is a fork in the road, and it is worth ten minutes
+before anything is created.
+
+| | Personal account | Organization account |
+| --- | --- | --- |
+| Requires | Government ID | A D-U-N-S number and business documents |
+| Closed testing before production | **12 testers opted in continuously for 14 days** | **Exempt** |
+| Realistic time to live | About 4 weeks | About 2 weeks, if the D-U-N-S already exists |
+| The catch | The 14-day clock cannot be shortened or bought | A new D-U-N-S is free but can take up to 30 days |
+
+The 12-tester rule applies to personal accounts created after 13 November 2023, per
+[Play Console Help](https://support.google.com/googleplay/android-developer/answer/14151465).
+Invited testers who never install do not count, the same twelve people can cover every future
+app, and once an app has production access its updates never need testers again.
+
+**Do this first:** look up three.ws at <https://www.dnb.com/duns/get-a-duns.html>. If a D-U-N-S
+already exists or is issued immediately, take the organization account and skip fourteen days
+of waiting. If it would take weeks, take the personal account and start the tester clock the
+same day, because that clock is the critical path and nothing else in this file is.
+
+## Steps
+
+1. **Create the account** ($25 one time) and complete identity or business verification. Set
+ `developer.account_type` in `config.yaml` to whichever you chose.
+2. **Create the app** with the title in `listing/title.txt` and the default language in
+ `config.yaml`.
+3. **Fill the App content forms.** Every answer is written down already: `listing/data-safety.md`,
+ `listing/content-rating.md`, `listing/financial-features.md`. Read the blocking issue at the
+ top of the data safety file before starting; it needs a privacy policy change that only the
+ owner can approve, and Google cross-checks the two.
+4. **Build the bundle.** Play takes an AAB, not an APK, and `scripts/build-apk.sh` already
+ produces `build/app-release-bundle.aab` beside the APK. Our release key is the *upload* key
+ here.
+5. **Upload to the closed testing track** and roll it out. On a personal account this starts
+ the 14-day clock, so do it before the store listing is polished, not after.
+6. **Add Google's signing certificate to Digital Asset Links. This step is not optional and it
+ has no local symptom.** Play App Signing is mandatory for new apps, so Google re-signs the
+ bundle with its own key and a Play install presents *that* certificate, not ours. Copy the
+ SHA-256 from **Test and release > Setup > App integrity > App signing key certificate** into
+ [`../twa/extra-fingerprints.json`](../twa/extra-fingerprints.json), rerun
+ `scripts/update-assetlinks.sh`, and deploy three.ws so the new statement file is live.
+ Skip it and every Play user gets three.ws with the Chrome address bar across the top,
+ while the dApp Store build stays perfect and nothing in local QA looks wrong.
+7. **Verify on a device installed from Play**, not from `adb install`. `adb shell pm get-app-links ws.three.app`
+ must report state 1, and the app must open with no address bar.
+8. **Apply for production access** (personal accounts only) once twelve testers have been opted
+ in for fourteen continuous days. Google's review of that application is usually under a week.
+9. **Promote to production.**
+
+## Graphics
+
+Play's sizes are not the dApp Store's, so `../publish/media/` cannot be reused as-is.
+
+| Asset | Size | Required |
+| --- | --- | --- |
+| App icon | 512 x 512, 32-bit PNG, no transparency | yes |
+| Feature graphic | 1024 x 500 | yes |
+| Phone screenshots | 2 to 8, between 320 px and 3840 px on each side, 16:9 or 9:16 | yes |
+| 7-inch and 10-inch tablet screenshots | same rules | optional, and Play ranks listings that have them higher |
+
+The icon at `../publish/media/icon.png` is already 512 x 512 and can be copied. The feature
+graphic must be regenerated at 1024 x 500 (the dApp Store one is the same size, so check it
+before rebuilding). Screenshots can come from the emulator recipe in
+[`../README.md`](../README.md#emulator-qa): unlike the dApp Store, Play does not require a
+Seeker, and the two Seeker-specific frames (Seed Vault sheet, mint confirmation) are not
+appropriate for a Play listing that ships to every Android phone anyway.
+
+## What Play will reject
+
+Read [`listing/financial-features.md`](listing/financial-features.md) before building anything
+that touches money on this channel. Short version: three.ws passes review because it is not a
+wallet and not an exchange, and adding an in-app wallet, an in-app swap, or a fiat on-ramp
+would move it into a category that needs a jurisdictional license. Adding a paid tier inside
+the Android build would pull in Play Billing.
diff --git a/solana-mobile/publish-play/config.yaml b/solana-mobile/publish-play/config.yaml
new file mode 100644
index 000000000..1fafbebc3
--- /dev/null
+++ b/solana-mobile/publish-play/config.yaml
@@ -0,0 +1,66 @@
+# Google Play Console worksheet for the three.ws listing.
+#
+# Same idea as ../publish/config.yaml (the Solana dApp Store worksheet): the
+# listing is authored in the console, so this file is the single source for the
+# values the owner types there, kept in git so the console never drifts from
+# what was reviewed. Play-specific answers that are long enough to need prose
+# live in listing/ next to the copy.
+
+developer:
+ # Which account type this is decides the whole timeline. See README.md.
+ account_type: organization # organization | personal
+ name: three.ws
+ website: https://three.ws
+
+app:
+ # Must match the dApp Store build exactly. One package id, one app, two
+ # distribution channels.
+ package_name: ws.three.app
+ default_language: en-US
+ app_or_game: app
+ free_or_paid: free
+ category: Art & Design
+ tags: [3D, AI, Avatars, Creation]
+ contact:
+ website: https://three.ws
+ urls:
+ privacy_policy: https://three.ws/legal/privacy
+ terms: https://three.ws/legal/eula
+ support: https://three.ws/docs
+
+listing:
+ title: listing/title.txt # 30 char limit
+ short_description: listing/short-description.txt # 80 char limit
+ full_description: listing/full-description.txt # 4000 char limit
+ graphics:
+ # Play's sizes are NOT the dApp Store's. Do not reuse ../publish/media/
+ # without resizing; see README.md.
+ app_icon: media/icon-512.png # 512 x 512, 32-bit PNG, no alpha
+ feature_graphic: media/feature-1024x500.png # 1024 x 500
+ phone_screenshots: media/phone/ # 2 to 8, min 320px, max 3840px
+ tablet_screenshots: media/tablet/ # optional, raises quality ranking
+
+release:
+ # Play App Signing is mandatory for new apps, so Play re-signs this bundle
+ # with Google's key and the installed app presents a certificate that is NOT
+ # ours. Its SHA-256 must be added to ../twa/extra-fingerprints.json or every
+ # Play install loses full-screen mode. See README.md step 6.
+ bundle: ../build/app-release-bundle.aab
+ track: closed-testing # closed-testing -> production
+ release_notes: ../publish/listing/new-in-version.txt
+
+declarations:
+ # Every one of these is a required form on the App content page. The answers
+ # are in listing/; they are recorded here so a re-submission does not have to
+ # reconstruct them from memory.
+ privacy_policy: listing/data-safety.md
+ data_safety: listing/data-safety.md
+ content_rating: listing/content-rating.md
+ financial_features: listing/financial-features.md
+ ads: none # the app serves no ads
+ target_audience: 18+
+ news_app: false
+ covid_contact_tracing: false
+ data_deletion_url: https://three.ws/legal/privacy
diff --git a/solana-mobile/publish-play/listing/content-rating.md b/solana-mobile/publish-play/listing/content-rating.md
new file mode 100644
index 000000000..3520d3d71
--- /dev/null
+++ b/solana-mobile/publish-play/listing/content-rating.md
@@ -0,0 +1,27 @@
+# Content rating questionnaire answers
+
+Play Console > App content > Content rating. The questionnaire is issued by IARC and produces
+ratings for every region at once. Answer conservatively: a rating that is too low and later
+corrected can pull the listing, and there is no upside to under-declaring.
+
+**Category:** Utility, Productivity, Communication or Other.
+
+| Question area | Answer | Why |
+| --- | --- | --- |
+| Violence, realistic or cartoon | No | No combat, no weapons, no depictions of violence |
+| Sexuality or nudity | No | Avatar creation is clothed by default; sexual content is prohibited by our terms |
+| Profanity or crude humor | No | None in the product surface |
+| Controlled substances | No | None |
+| Gambling, simulated or real | **No** | This one deserves a real answer rather than a reflex. Users can trade agents and buy skills with USDC, and agents can be deployed as on-chain assets. None of it is a wager: there is no game of chance, no randomized paid draw, no loot box, no prize pool, and no mechanism where a user pays for a chance at an item of unknown value. Play's blockchain policy bans exactly that pattern and we do not implement it |
+| User-generated content | **Yes** | Users create avatars and agent personas that other users can see in the marketplace |
+| UGC: moderation and reporting | **Yes** | Report and takedown paths exist and are staffed through [email protected] |
+| Users can interact or exchange content | Yes | Marketplace listings, agent chat, embeds |
+| Shares user location | No | Never collected |
+| Allows purchases | Yes | On-chain purchases settled by the user's own wallet, not Play Billing. See financial-features.md |
+| Digital purchases of virtual currency | No | three.ws sells no in-app currency and mints no purchasable token |
+
+**Expected outcome:** Teen in North America, PEGI 12 in Europe, driven by the user-generated
+content and interaction answers rather than by anything in the app's own content.
+
+**Target audience:** 18 and over. Select 18+ explicitly. The app is not designed for children,
+must not appear in Play's Families programs, and the 18+ answer keeps it out of them.
diff --git a/solana-mobile/publish-play/listing/data-safety.md b/solana-mobile/publish-play/listing/data-safety.md
new file mode 100644
index 000000000..de66571be
--- /dev/null
+++ b/solana-mobile/publish-play/listing/data-safety.md
@@ -0,0 +1,63 @@
+# Data safety form answers
+
+Play Console > App content > Data safety. Google cross-checks these answers against the
+privacy policy at <https://three.ws/legal/privacy>, and a mismatch is a rejection, so change
+both together or neither.
+
+Terms used below are Play's, not ours. **Collected** means the data leaves the device to our
+servers. **Shared** means it is transferred to a third party. **Processed ephemerally** means
+it is used to service the request and not retained.
+
+## Blocking issue before this form can be submitted
+
+**The live privacy policy does not mention photo or camera data at all.** It documents account
+identifiers, uploaded 3D models, on-chain data, usage data, session data and legal acceptance
+records (version 2, effective July 16, 2026), and the selfie capture flow predates none of
+that: it is simply missing. The declaration below says photos are collected and retained,
+because `api/_lib/likeness-store.js` reads capture URLs back out of the stored generation
+params, so they persist. A Data safety form that declares photo collection against a privacy
+policy that is silent on photos is exactly the mismatch Google rejects.
+
+Draft clause for the owner to review and publish before either store submission. It states
+what the code already does and adds no new commitment:
+
+> **Photos you capture or upload.** If you use the selfie flow, the photos you capture (one
+> frontal image and up to two optional side angles) are uploaded to our reconstruction service
+> and used to build your 3D avatar. They are stored with the generation record so the result
+> can be reproduced, re-rigged and re-scored for quality, and they are visible only to your
+> account. They are deleted when you delete the generation or your account, subject to the
+> retention windows in Section 5. We do not use them to train models, we do not share them
+> with advertisers, and we do not derive or store a face template or any other biometric
+> identifier from them.
+
+The last sentence is verifiable in code: `api/_lib/likeness-score.js` computes face embeddings
+in memory to score likeness and files only the resulting 1 to 5 number, never the embedding,
+the crop, or the capture URL.
+
+## Data types
+
+| Play data type | Collected | Shared | Required | Purposes | Notes |
+| --- | --- | --- | --- | --- | --- |
+| Personal info > Email address | Yes | No | Optional | Account management, app functionality | Only if the user registers with email; wallet-only accounts never provide one |
+| Personal info > User IDs | Yes | Yes | Optional | Account management, app functionality | Username, display name, and wallet address. Shared is **Yes** because deploying an agent writes the wallet address to a public blockchain, which is disclosure and cannot be retracted |
+| Photos and videos > Photos | Yes | Yes | Optional | App functionality | Selfie captures. Shared is **Yes** because generation is forwarded to upstream model providers named in the privacy policy. Collected only when the user chooses the selfie flow |
+| Files and docs > Files and docs | Yes | No | Optional | App functionality | GLB/glTF models the user uploads |
+| App activity > Other actions | Yes | No | Optional | App functionality, analytics, fraud prevention | API calls and widget load events, for quota and abuse limits |
+| App info and performance > Crash logs | Yes | No | Optional | Analytics | Client error reports posted to `/api/client-errors` |
+| Device or other IDs | No | No | | | No advertising ID, no device fingerprinting. Session records store a hashed IP and the user agent, which Play does not classify as a device ID |
+
+Everything not listed is **not collected**: no location, no contacts, no calendar, no SMS, no
+call logs, no health data, no financial account or payment information (all value transfer is
+on-chain and settled by the user's own wallet), and no audio recordings.
+
+## Security practices
+
+- **Encrypted in transit:** yes. HTTPS everywhere, HSTS with `preload` on the apex.
+- **Users can request data deletion:** yes. Deletion is available in-product and at
+ <https://three.ws/legal/privacy>. Deleted accounts are soft-deleted for 30 days, then purged.
+- **Committed to the Play Families Policy:** not applicable, the app is 18+.
+- **Independent security review:** no. Do not claim one.
+
+## Data deletion URL
+
+<https://three.ws/legal/privacy> (Section 5 covers retention and the deletion path).
diff --git a/solana-mobile/publish-play/listing/financial-features.md b/solana-mobile/publish-play/listing/financial-features.md
new file mode 100644
index 000000000..9d768e8c9
--- /dev/null
+++ b/solana-mobile/publish-play/listing/financial-features.md
@@ -0,0 +1,53 @@
+# Financial features declaration and blockchain policy position
+
+Play Console > App content > Financial features. This is the form that decides whether the
+listing survives review, so it gets a reasoned answer rather than a checkbox.
+
+## What we declare
+
+| Financial feature | Answer |
+| --- | --- |
+| Cryptocurrency exchange | **No.** three.ws does not match orders, does not quote a book, and never takes custody. Buying and selling agents is a peer-to-peer on-chain transfer signed by the user's own wallet |
+| Cryptocurrency wallet | **No.** The app has no key material. Signing runs through Mobile Wallet Adapter, which hands the request to a separate wallet app the user already installed, or to Seed Vault on a Solana Seeker. Uninstalling three.ws destroys no keys and loses no funds |
+| Tokenized digital assets | **Yes.** Users can deploy an agent as a Metaplex Core asset on Solana, so the app enables users to obtain a tokenized digital asset. Declare it |
+| Personal loans, debt, banking, investments, insurance | No |
+
+## Why the wallet answer is "no", and how to defend it
+
+Since late 2025 Google has required crypto exchange and wallet apps to hold a jurisdictional
+license (CASP under MiCA in the EU, FCA registration in the UK, and equivalents elsewhere).
+The policy text describes cryptocurrency services broadly and does not spell out a custodial
+versus non-custodial line, so the safe posture is not to argue the line, it is to not be a
+wallet in the first place.
+
+three.ws is not, and the code shows it:
+
+- No private key, seed phrase or keystore ever exists in the app. `solana-mobile/src/mwa-wallet.js`
+ holds an authorization token from a separate wallet app and nothing else.
+- Every signature is produced outside the app, by the wallet the user chose, on hardware we do
+ not control.
+- We do not custody balances, do not offer conversion between assets, do not operate an order
+ book, and do not run a fiat on-ramp anywhere in the app.
+
+Keep it that way. **Adding an in-app wallet, an in-app swap, or a fiat on-ramp would move the
+app into the licensed category and jeopardize the listing.** That is a product constraint on
+this distribution channel, and it is the single most important thing to know before building a
+payments feature that ships to Play.
+
+## Play Billing
+
+Play requires Play Billing for purchases of in-app digital content. What three.ws sells is not
+that: deploying an agent pays a Solana network fee to validators, and buying an agent or a
+skill is a transfer between two users settled on-chain. three.ws is not the seller and takes no
+in-app payment. There is no subscription, no coin pack and no consumable sold inside the
+Android app.
+
+**Do not add one without re-reading this policy first.** If a paid tier ever ships inside the
+Android build, it needs Play Billing, and the on-chain lane cannot be used to route around it.
+
+## Copy review
+
+Play's blockchain policy also forbids promoting or glamorizing potential earnings. Before
+submitting, re-read `listing/full-description.txt` for any claim that a user can profit,
+earn, or make money. The current copy makes none, describes the wallet as optional, and states
+plainly that three.ws is not a wallet and does not hold funds. Keep that paragraph.
diff --git a/solana-mobile/publish-play/listing/full-description.txt b/solana-mobile/publish-play/listing/full-description.txt
new file mode 100644
index 000000000..58e48486a
--- /dev/null
+++ b/solana-mobile/publish-play/listing/full-description.txt
@@ -0,0 +1,37 @@
+three.ws turns a photo into a 3D AI agent you own.
+
+Take a selfie and get back a textured, rigged, animation-ready 3D avatar in about a minute. Give it a personality and a voice, talk to it, and put it anywhere on the internet with one line of HTML. No 3D software, no modelling skills, no account required to look around.
+
+WHAT YOU CAN DO
+
+Create from a selfie. One frontal photo becomes a rigged avatar; two optional side angles sharpen the likeness. Live quality gates tell you if the lighting, framing or focus will hurt the result before you spend a minute waiting.
+
+Create from text. No photo? Describe the character and the free generation lane builds it. Already have a model? Upload a GLB and it is rigged for you.
+
+Give it a mind. Attach a personality, a voice and skills, then hold a conversation with it. The agent answers in 3D, on your phone.
+
+Discover. Browse the whole community's agents. Drag to orbit, tap to inspect, open any agent to chat with it.
+
+Own it on-chain, if you want to. Deploy an agent as a Metaplex Core asset on Solana held by your own wallet. This is entirely optional: creating, chatting and browsing never touch a wallet.
+
+Embed anywhere. Every agent has a shareable link and a one-line embed snippet that works in a blog post, a docs site, Notion, or your own product.
+
+See it in your room. Point your camera and place any agent in real space through your browser's AR support. Nothing to install.
+
+WALLETS ARE OPTIONAL
+
+You can use three.ws without ever connecting a wallet. If you do connect one, signing runs through Mobile Wallet Adapter, so it happens inside the wallet app you already trust and this app never sees a private key or a seed phrase. On a Solana Seeker, that is the hardware-isolated Seed Vault. three.ws is not a wallet, does not hold your funds, and does not operate an exchange.
+
+OPEN BY DEFAULT
+
+three.ws is open source at github.com/nirholas/three.ws. Agents are published with an open manifest so they stay portable to any compatible viewer or marketplace. Your work is yours, and it leaves with you.
+
+WHAT YOU NEED
+
+A phone running Android 6.0 or later, and a network connection. Camera permission is requested only when you choose the selfie flow, and you can upload a photo from your gallery instead. Deploying an agent on-chain needs a small amount of SOL, typically under 0.01; everything else is free.
+
+SUPPORT
+
+https://three.ws/docs
+github.com/nirholas/three.ws/issues
diff --git a/solana-mobile/publish-play/listing/short-description.txt b/solana-mobile/publish-play/listing/short-description.txt
new file mode 100644
index 000000000..b90bebf22
--- /dev/null
+++ b/solana-mobile/publish-play/listing/short-description.txt
@@ -0,0 +1 @@
+Turn a selfie into a rigged 3D AI agent you own, talk to, and embed anywhere.
diff --git a/solana-mobile/publish-play/listing/title.txt b/solana-mobile/publish-play/listing/title.txt
new file mode 100644
index 000000000..ee0aa755e
--- /dev/null
+++ b/solana-mobile/publish-play/listing/title.txt
@@ -0,0 +1 @@
+three.ws: 3D AI Agents