myselfWhy we’re building myself.md
Four focused apps taught us how much of a life can fit inside ordinary data. We’re bringing them into one place while keeping each source clear and every export yours.
Most days leave a trail: a night of sleep in Health.md, the route to a favorite café in IsoMe, a sentence caught in Vox.md before it disappears, and a long afternoon in Time.md.
Each record is useful on its own. Put them on the same page and an ordinary day becomes easier to remember. The idea for myself.md began with that simple observation.
The pieces came first
myself.md grows out of four existing apps. Health.md works with health and activity records. IsoMe keeps a history of places and routes. Vox.md catches spoken thoughts and quick notes. Time.md shows where screen time goes.
Those apps have distinct jobs and distinct data sources. That history will remain visible in the unified app. A Health.md record should still identify Health.md. A place should still carry its original provider. When platforms measure something differently, myself.md should show the difference instead of filling the gap with a made-up match.
Context, with the seams showing
A shared daily view makes new questions possible, but records that appear together do not automatically explain one another. A morning walk and a better night of sleep on the same date do not prove cause and effect. Useful context needs the original times, sources, and limits close at hand.
“Do I spend less time on my phone on days I take a morning walk?”
That question crosses IsoMe and Time.md. The answer should let you inspect the records behind it, see what is missing, and decide what the pattern means for you.
The file is part of the product
A personal archive should stay useful outside the interface that created it. We’re planning exports in Markdown, JSON, and CSV. Markdown fits naturally beside notes. JSON gives tools a structured record. CSV keeps the same information approachable in a spreadsheet.
Readable formats also leave room for different ways of exploring the archive. You might use a local agent, choose a cloud service for selected files, or simply read yesterday’s Markdown. The app does not need to choose that for you.
One app, built in stages
The unified app will use one visual language across every domain. Health, places, notes, and screen time will still retain the screens and workflows that make sense for their data. Under the surface, deterministic logic moves into a shared Rust core while permissions, storage, and other device work stay native.
We’re moving complete workflows in stages and testing each one on its real platform. The results need to stay honest about what every device and provider can do.
Where things stand
The unified app is in development. Health.md, IsoMe, Vox.md, and Time.md remain available today, and their links are on the myself.md home page. We’ll share supported devices and early access details when they are ready.
This blog will keep a record of the choices along the way, including the ones that change after we try them.
Early access
Want to try myself.md when the first early access builds are ready? Join the list for occasional product updates. The website only stores the email address you submit; the privacy notice has the details.