iPhone app: is it ready for the App Store?
Not yet. The code is in good shape, and #1942 is merged to platform main. Submission is blocked on account items only Eoj can do, then about a day of device and TestFlight work.
What is done
| Area | State |
|---|---|
| Code | Merged to platform main (#1942) |
| Debug build | Compiles (simulator) |
| Release build | Compiles (simulator, optimised), checked today |
| Parity with m.allternit.com | Rounds 1–8 done: Home, Bots, Code, ACI Teach, decks, icons, games, backgrounds |
| Sample data | Debug only; never in Release |
| Privacy manifest | App/PrivacyInfo.xcprivacy and the screen extension |
| Usage strings | Camera, microphone, photos, speech |
| Delete account | In Settings (App Store rule 5.1.1) |
| Sign in with Apple | Button and entitlement present |
| Listing draft | AppStore/listing.md, waiting for Eoj's approval |
| Privacy and support pages | Both live (200) |
Blocked on Eoj
- Apple team ID.
DEVELOPMENT_TEAMis empty inproject.yml. Without it there is no signing, no device build and no upload. - App Store Connect record for
com.allternit.mobile, plus approval of the listing text. - APNs key (.p8) for cloud-api, so push works in production.
- Clerk settings:
- app name and logo shown as "Allternit"
- Sign in with Apple turned on
- users can delete their own account
- the app's sign-in return links allowed for Google and GitHub
- Demo account for Apple's reviewer, with a cloud computer that stays online during review.
- Encryption answer. The app uses WireGuard. Eoj answers the encryption question in App Store Connect; the Info.plist key stays out on purpose.
- Universal Links. ai #872 serves the association file, but it still has
TEAMID_PLACEHOLDER. Today ai and m.allternit.com return a web page there, not the file. It needs the team ID, then a merge, which is a production deploy.
Left for me once those land
- Set the team ID, then make a signed device build on the bot iPhone.
- Do a full tour on a real account:
- sign in with email, Apple, Google and GitHub
- Home streaming, bot chat stage, group rooms
- Code through the relay: Terminal look and Shell
- ACI Teach, push, and Delete account on a test user
- Take App Store screenshots (6.9" and 6.5") from the sample workspace.
- Upload to TestFlight, run an internal test, then submit on Eoj's go.
Known differences from Desktop (not blockers)
- Code Tree card: shows checkpoints but can't rewind to one.
- Bot stage: no "Since you were last here" briefing or work-steps card yet.
- Teach: exact Run, the recording timeline and the business profile stay Desktop-only.
- Background tap ring: built but not seen yet; the simulator can't tap from a script.
Risks for review
- Real accounts: most changes from rounds 5–8 were checked only with sample data in the simulator.
- Reviewer access: Code and Automation need a computer online during review. Without one, the reviewer sees "Connect a computer".
- Push setting: the push entitlement says development. Xcode switches it to production when exporting for the App Store, which needs a distribution profile.