Essentially I am.. baffled by how nice Nix feels, at least as a first time user. It's difficult at first and kinda confusing (and tbh it still is confusing) but once you get it working it just kinda.. works.

Surprisingly... that was it? I had to write a default.nix file which is honestly just some messy code (once again, first time), but after that the build just.. worked? And it was added to my system configuration + reproducible (I just copied the file and deb file over to my laptop and it worked!)

I use NixOS so obviously I naturally reached to build it using Nix, which.. was a headache because Tauri apparently doesn't play nice with Nix? (Or I'm just unaware since this is my first time)

I ended up just building it as you would for other distros, then unwrapping the result

Either way, that's it for this week, little progress because exam season is rough :(

My current idea is just to copy what other apps have done and literally just choose the first n letters of the typed description, because if there's no description and there's no title I... don't think it should be saved?

The main issue is that the file structure still relies on titles, so I'm not quite sure how to deal with ideas that don't have titles, because I do want that to be a feature to make idea inputs as seamless and frictionless as possible.

Note, I do intend to release this as an app in the near future, so if anyone is actually interested in any of that, you might wanna check back in, in a couple months! (3 months maybe i hope)

That's all, I will return to horse game.

Thamk you for reading.

Technically, this is all kept local-first simply by using a state-deterministic idempotent indexer to generate a presentation layer. The front-end can then simply read from that layer, writing to files directly.

Therefore, the user can simply sync the files, and have the same output on each device.

There are also a few weird personal touches, like the concept of "Task Chains" that remind you of things to do after, and what you thought should've been done before

Or, scheduled and ephemeral Priorities, where you have a priority lane that you can schedule, and have it just go back if you miss it

Keep in mind that these things are meant to interact with one another! Ideas can become tasks, events, etc.

I also chose for a Tag-based structure rather than a Folder-based structure, since all these things are often multiple tags/labels, however rarely fit into one neat folder.

This is intended to be done with a split of what "Items" can take the form of.

Ideas - Quick Capture Notes
Tasks - Asynchronous Activities
Events - Synchronous Activities
Projects - Medium-term Collection of Items
Traces - Crystalization of Ideas that function as simple notes stored long-term.

Secondly, I've added Idea tracking which is meant to help with keeping track of all those things that you think of but you don't have the time or mental capacity to collapse into a task/event yet. It's not done yet though, still just rough implementations. I'll be working on that this week!