Week 13: The First Update After Launch — Lumi

Week 13: The First Update After Launch

A short update about Lumi's first post-launch release, advanced recurring reminders, Pause Until, and the careful checks behind a stable release.

Build in Public - Week 13 (July 20-26)

After the family trip, I came back to the product with a different kind of pressure. Launch day was over. Lumi was already on Google Play. That meant the next release was no longer about proving that I could ship an app. It was about proving that I could keep one alive.

This week became the first real update after launch. The biggest user-facing change was advanced recurring reminders. Lumi could already handle common schedules, but real life is messier than that. People say things like “every three hours,” “every two weeks on Wednesday,” or “the first business day of every month.” This update made Lumi better at handling those patterns.

I also added Pause Until. A reminder should not only be active or paused forever. Sometimes you just want it quiet until next Monday, or until a trip is over, or until a period of work has passed. This made Lumi feel closer to how people actually manage daily life.

The release notes looked simple:

  • Advanced recurring reminders for custom hourly, daily, weekly, and monthly patterns
  • Pause Until for temporarily pausing reminders
  • Better calendar views, conflict detection, and task summaries
  • More reliable reminder scheduling and notifications
  • Better Plus subscription recognition
  • Performance, privacy, and stability improvements

Behind that short list was a lot of defensive work. I had already learned from white-box testing that a reminder app can fail quietly. A task may look correct in the UI while the next reminder is wrong. A paused reminder may disappear from one screen but still behave incorrectly later. So this update needed careful checks around the invisible parts, not just the visible screens.

There was also ordinary release work: preparing the update, checking the package, testing upgrade behavior, and making sure the app still felt stable after the new reminder logic was added. None of that is visible in the product screenshots, but it matters.

By the end of the week, Lumi had moved from “launched” to “maintained.” That felt like a different milestone. The first version proves you can finish. The first update proves you can return to the code, improve the product, and keep it stable.

Next week: less celebration, more maintenance.