Project story / Rest+Rise · 19 Jul 2026
From a morning-routine Google Doc to Rest+Rise
Rest+Rise started in a Google Doc. I was trying to be more deliberate about my mornings, so I tracked the routines I was attempting, what seemed useful and what I wanted to try next. It worked, but it also exposed the limitations of a document: it could record a routine, but it could not help me build one, run it or understand whether I was actually sticking to it.
At the same time, I kept finding new ideas about sleep, light, movement, focus and recovery. Some had reasonable evidence behind them; others were confident wellness claims repeated until they sounded like facts. I wanted one place that made the distinction visible and turned the useful ideas into something a normal person could fit into the first or last part of a day.
Turning research into an actual routine
The product is organised around two moments: Rise, the first 60 minutes of the morning, and Rest, the last 60 minutes of the evening. It contains a library of time-bounded rituals, evidence labels and source material. People can browse the options, assemble their own stack, reorder it and then run it as a checklist or timer.
The most important product decision was to avoid making the app another guilt machine. Morning-routine content often implies that a good day requires a heroic sequence before breakfast. Rest+Rise is built around the time someone actually has. A short routine that gets used is more valuable than an ideal one that collapses after three days.
That also changed how the research is presented. Evidence is not decoration and the app should not claim certainty where there is none. The job is to give someone enough context to make a sensible choice, then get out of the way while they do it.
The cross-platform experiment
My first app, LightScout, was native SwiftUI. With Rest+Rise I deliberately chose React Native and Expo. Partly I wanted the app on both iOS and Android; partly I wanted to understand the trade-offs for myself rather than repeating the usual arguments about cross-platform development.
The shared codebase did what it promised. I could build the core experience once and take it to both stores. It did not make the platforms identical. Authentication, subscriptions, store configuration, release processes and the last layer of interface behaviour still have platform-specific edges. Shared code reduces one category of work; it does not remove the need to understand two products, two ecosystems and two sets of failure modes.
I am glad I built a cross-platform app. I am also much less likely to choose cross-platform by default next time.
That is not a verdict that React Native or Expo are poor tools. They are capable, and Rest+Rise now exists on both platforms because of them. It is a judgement about the kind of solo work I enjoy and where I want to spend complexity. For a future personal app, I would probably prefer to make one platform feel excellent and only add another when the demand justifies it.
What the app became
The current product goes well beyond the original document. It supports custom routines, generated quick stacks, guided sessions, history and a paid Insights layer that can turn usage into a weekly coaching note. The underlying idea, however, is unchanged: make the useful research easier to act on in the two parts of the day where small choices compound.
I still think of the Google Doc as the right first version. It proved I cared about the problem before I spent months turning it into software. The app was not the starting insight; it was what became possible once the manual system had shown me exactly where it broke down.