Mobile groundwork and Play setup
2026-09-26
Mobile backend groundwork
- Closed out the core backend tickets needed to support the Android app: mobile sign-in with PKCE, a mobile-only token claim and ingest guard, event ingestion, plan-based capabilities, and OAuth callbacks returning to the app.
- Also made the auth callback scheme environment-specific, so local, staging, and production builds can coexist without stealing each other’s deep links.
- Added the RevenueCat webhook path for store subscriptions. The remaining work is mostly configuration rather than backend shape.
Android release prerequisites
- Mapped the operational dependency chain for publishing subscriptions: virtual office → sole proprietorship registration → D-U-N-S number → Google Play organization account → Play subscription products.
- The organization account route avoids the new personal-account closed-test requirement and keeps the app published under deariary rather than a personal name.
- Noted the immediate blocker plainly on JRNL-835:
Blocked by the Google Play Console organization account.
- These business prerequisites also overlap with the long-running Meta Business Verification work. At least the vague prerequisites are now concrete tasks.
Public-facing cleanup
- Published the AI model update changelog, recorded the accompanying X announcement, and refreshed the homepage’s featured essays instead of leaving two March posts pinned there.
- Updated the public supported-integrations list to match what is actually live now: Discord, Last.fm, Swarm, Trakt, and Linear; Weather moved to “coming soon.”
- Small but satisfying alignment pass: product, docs, and homepage now tell a more current story.