Android parity and release automation

Input and diary polish

  • Landed a big batch of Android work to bring the diary closer to the web: the timeline now keeps the entry chrome across days, the You tab has a real Profile row, and the home screen finally has a notification bell.
  • Put a lot of attention into the manual-input flow: focused forms, sensible keyboard actions, camera support, and confirmation feedback after posting or saving. Also fixed picked photos so they land on today instead of being backdated to their EXIF capture time.
  • Matched that work on the frontend: moved confirmation to Android-style snackbars and made the “add to today” detail-pane flow into proper pages. The feedback actually has somewhere visible to go now.
  • Also merged the Android-style auth, sources, and shared-page layouts. A lot of surface area, but it is all pulling toward one coherent product.

Release pipeline

  • Finished wiring Android into the same release rhythm as the frontend and backend: main can open a production PR, production checks version bumps and tags releases, and staging/production bundles deploy from the appropriate branches.
  • Added CODEOWNERS along the way. Nice to have the Android repo stop being the odd one out operationally.

Small maintenance

  • Sent two quick external cleanup PRs: a compression security override for cycle-flyer, and dropped EOL Ruby 3.2 support in irasutoya-cli.
  • The frontend backlog also shrank by 10 open issues over the recent reporting window. Quietly satisfying.

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

Android parity and release automation — deariary