Mobile onboarding and admin clarity
Thursday, October 1, 2026
Admin finally sees the app
- Closed out nine mobile/admin tickets in one sweep. The main goal was to stop treating app users as invisible or misleading data.
- Added mobile analytics ingestion and carried it through the admin surface: app activity now counts toward engagement and retention, signup client can be split between web and app, and mobile events/media have their own list and detail views.
- Cleaned up two reporting traps: the auto-created
mobileconnection no longer inflates integration metrics, and annual plans are recognized asannualrather thanyearlyso MRR is not overstated. - Store billing through RevenueCat is now represented in subscriptions and revenue too. The admin picture should be much closer to reality.
Android first-run flow
- Merged the new-account onboarding: explain what deariary is, collect preferences, then lead people toward connecting services.
- Followed it with the first-week prompt. Onboarding itself does not generate anything; the past week is a deliberate, one-time action after services are connected.
- Left the web memo/mood work a breadcrumb pointing at its backend ticket: the pieces are connected now.
Test foundation and small UI ideas
- Wrote down the testing strategy, then added the Robolectric/Espresso feature-test harness and a first screen test. Also added a
kobitofeature-coverage preset so the next iterations have a repeatable path. - Filed two backlog ideas for the feel of the product: little moments of delight around connecting/onboarding/new diaries, plus satisfying feedback for copy, toggles, and deletion. Small stuff, but it is the stuff people touch all the time.