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): lead the account answer with the Android work and record why not to overstate Play history

nirholas46aad136a6cc
diff --git a/solana-mobile/publish-play/account-experience.md b/solana-mobile/publish-play/account-experience.md
index 1c5812c64..5d23291ee 100644
--- a/solana-mobile/publish-play/account-experience.md
+++ b/solana-mobile/publish-play/account-experience.md
@@ -10,34 +10,38 @@ it is checkable against this repository.
## Paste this
-> I have not used Play Console before. This is my first developer account, and
-> the three.ws Android app will be my first Play submission.
+> Android experience: I build and ship the Android app for three.ws
+> (https://three.ws), an open-source platform for creating, animating and
+> embedding 3D AI avatars. The app, package `ws.three.app`, is a Trusted Web
+> Activity built with Bubblewrap: signed release APK and AAB, minSdk 23,
+> targetSdk 36.
>
-> Android experience: I built a small Android app as a student, long before the
-> current toolchain. My current Android work is three.ws (https://three.ws), an
-> open-source platform for creating, animating and embedding 3D AI avatars. I
-> built its Android app, package `ws.three.app`, as a Trusted Web Activity using
-> Bubblewrap: a signed release APK and AAB, minSdk 23, targetSdk 36.
->
-> That work covered the release keystore and a non-interactive signing pipeline,
-> Digital Asset Links (live at https://three.ws/.well-known/assetlinks.json and
-> confirmed through Google's digitalassetlinks statements API), long-press app
-> shortcuts, an Android share-sheet target for images and .glb model files, a
-> maskable adaptive icon, an offline shell, and web push via a service worker.
-> I tested on a Pixel 7 emulator running Android 14: install and launch, shortcut
+> I set up the release keystore and a non-interactive signing pipeline, Digital
+> Asset Links (live at https://three.ws/.well-known/assetlinks.json, confirmed
+> through Google's digitalassetlinks statements API), long-press app shortcuts,
+> an Android share-sheet target for images and .glb model files, a maskable
+> adaptive icon, an offline shell, and web push through a service worker. QA on a
+> Pixel 7 emulator running Android 14 covered install and launch, shortcut
> registration through `dumpsys shortcut`, `ACTION_SEND` intent handling, and
-> deep-link verification state through `pm get-app-links`.
->
-> The same build is also prepared for the Solana dApp Store. The source is public:
+> deep-link verification state through `pm get-app-links`. Source is public:
> https://github.com/nirholas/three.ws, with the Android packaging under
> `/solana-mobile`.
+>
+> I also built an Android app as a student, long before the current toolchain.
+>
+> Play Console: this is my first developer account, and three.ws will be my first
+> Play submission. The same build is already prepared for the Solana dApp Store.
## Why it is worded this way
-- **"I have not used Play Console before" is stated first and plainly.** This
- field is not a pitch. Google uses it to calibrate the account, and an
- overstatement here is the kind of thing that surfaces later during developer
- verification.
+- **The Android work leads; the Play Console answer closes.** Both are stated
+ plainly, but opening with the disclaimer buried real experience behind it.
+ Order is presentation. The facts do not move.
+- **Do not claim prior Play Console use.** It is tempting and it is strictly the
+ worst option available. The field is private and gates nothing, Google can
+ already see whether this identity has held an account, and registration
+ accuracy is a termination condition in the Developer Distribution Agreement.
+ That bet risks the account to improve a text box only the owner ever reads.
- **No date is given for the first app.** The owner recalls it as roughly twenty
years ago, which would predate the Android SDK. The claim is true without the
number, so the number is left out rather than risk a wrong date on a form.