Mobile backend foundation and Play setup

Mobile backend foundation

  • Closed out the core backend work needed for the Android app: mobile event ingestion, plan-based capabilities, mobile-only token guards, OAuth callback returns, and sign-in via custom scheme + PKCE.
  • Also finished environment-specific auth callback schemes and the RevenueCat webhook path for recording store subscriptions. That is a lot of the plumbing behind “the app can actually authenticate, ingest data, and know what plan someone has.”
  • Left Play Integrity verification as the remaining mobile security follow-up.

Billing and release prerequisites

  • Turned the store-subscription follow-ups into concrete ops work: configure RevenueCat, put the real webhook secret into Secret Manager, and create Google Play Basic/Advanced subscription products.
  • The dependency chain is clear now: virtual office → sole proprietorship registration (開業届) → D-U-N-S number → Google Play Console organization account → subscription products.
  • Noted the practical blocker plainly: > “Blocked by [#209] (Google Play Console organization account).”
  • These same business prerequisites also feed into the long-running Meta Business Verification and App Review work, so the admin work is shared rather than separate busywork.

Changelog and homepage cleanup

  • Published the AI model update changelog, then recorded the announcement post in the blog repo.
  • Refreshed the homepage’s featured posts, replacing two March leftovers with stronger recent essays.
  • Quiet social day otherwise; no Bluesky posts or likes.

Share

Check out my diary entry on deariary #deariary #diary

Your life, automatically written.

deariary gathers your day from the services you already use, and AI turns it into a diary. No writing required — just a daily record you can look back on.

Turn your passing days into your own diary.

Try it free

Highlights

blog / Pull Requests

3 opened, 3 merged

autojrnl / Issues Completed

7