Moving Health.md into a cross-platform monorepo
Transcript - 2026-07-26 13:37:53
A CLI proof of concept worked, so now, as is cliche, I’m doing a Rust rewrite to support multi-platform. My goal is to unify the CLI into its own code base and have it work for Mac, Windows, and Linux. I also want it to be the bridge between our agents and both iOS and Android. I’m glad I’ve gone down this rabbit hole. I thought my initial CLI bundled into the Mac OS was an effective strategy, but now I see it was lacking quite a bit. Little features like keeping the app awake while exporting or while CLI connection being toggled on is huge. Now the question is: can I hook this CLI up to Android as well? Enabling one interface and code base for a CLI to interact with either app sounds great, which also brings up the topic of a unified mobile app using React Navative or alternative. Maintaining two apps is a pain. It would feel amazing if both apps maintained identical UI and feature sets with slightly different output. AI decides React Native is a poor choice, and rather, it’s best to use Kotlin’s multi-platform support. Its reasoning is that both apps rely heavily on native APIs, so, a framework like React Native will introduce TypeScript while still maintaining Swift and Kotlin. I don’t know how confident I am with Kotlin’s multi-platform support. Seems like Rust’s and Mozilla’s Unify-RS package may provide quite a bit of performance benefits. No matter what, I want to have a monorepo, bring an iOS, Android, CLI, and plugin into a single code base. Okay, I’m letting GPT 5.6 Sol take a crack at a monorepo. This will move iOS, Android, Web and CLI into unified interface while also moving a plugin code into the repo while referencing it in the main plugin repo due to how Obsidian requires repo structure. We still need a dedicated plugin repo, but GPT is confident we can still condense the schema code into the monorepo, allowing for easier sharing of contracts. The previous method of multiple code bases has always felt fragile. Making a schema had to be applied to Android. If possible, and then adapted to the visualizations. This old system is a great example of what agents don’t like. They want structure and schemas to compare and validate against. Monorepo will unify the data contracts between all layers and should make each part much more resilient now that it’s supported by the pieces around it. I’m really liking the handwritten journal paper and pencil. It is so flexible and quick to draw ideas down that I’m finding myself writing consistently throughout the day. But I do not want to share, but I do want to share these thoughts with the world, so maybe I can build a system that will convert photos of my handwritten notes into draft blog posts that I can edit. If the character recognition fails, I would not generate any content, only just transcribe my writing to digital posts. Ideally, the whole flow is done on my phone, so maybe a shortcut and/or local LLM, an HTTP request to my blog would give the trick. Funny enough, an app is probably easier because then an agent can do the lifting, whereas a shortcut requires manual work from me.
Comments