Atlas
Atlas is a personal productivity workspace built around a simple premise: checking a box next to a habit doesn't actually get any meaningful work done. It brings habit tracking, notes, code snippets, alarms, smart reminders, progress tracking, and daily planning into a single customizable system, designed around consistently completing real work rather than just logging that a habit happened. It's currently in active development and doesn't have a public repository yet; the feature set and technical write-up below will keep expanding as the build progresses.
Why I Built This
Every habit tracker I've tried treats the habit as the whole point, check the box, keep the streak, done. But a streak doesn't actually get any real work finished. I wanted a system built around consistently doing the work itself, with habits as one input into that, not the entire product.
Notes, snippets, alarms, and reminders tend to live in four different apps, which means planning a day happens by mentally stitching those tools together. Atlas exists to put those pieces in one place instead.
A System, Not a Checklist
The habit-tracking piece of Atlas is intentionally not the centerpiece. It's one input into a daily planning view that also pulls in notes, snippets, and reminders, with the goal of helping someone actually complete meaningful work during the day rather than just logging that a habit happened. Progress tracking looks at whether the underlying work got done, not just streak length.
Why This, Why Now
This isn't a project built to fill a portfolio slot, it's a system I actually want to use myself. I've kept habits going for weeks in other trackers only to realize the streak was the only thing that survived; the actual work the habit was supposed to support never got any easier to find, plan, or finish. Atlas exists to fix that for my own use first, which is also why it's being built carefully rather than rushed to a demo.
Current Development Stage
Atlas is early, the core data model for habits, notes, snippets, and reminders is being worked out before any of it becomes a polished interface. There's no public repository yet because the foundation isn't stable enough to be worth sharing; putting it out before that would mean explaining away half-finished pieces instead of showing something coherent.
Planned Roadmap
The near-term goal is getting the connected daily-planning view working end to end, habits, notes, and reminders actually referencing each other, not just living in the same app. After that, the roadmap turns to the customization layer, since a productivity system that doesn't adapt to how someone actually works tends to get abandoned regardless of how solid the underlying architecture is.
Key Decisions
The core design decision is treating habits, notes, snippets, reminders, and daily planning as one connected system rather than separate features bolted together, a day's plan should be able to reference a note or trigger a reminder without switching tools.
Deep customization was prioritized over a fixed, opinionated workflow, since a productivity system that doesn't adapt to how someone actually works tends to get abandoned within a few weeks.
Specific architecture and technology choices are still being finalized as the build progresses; this section will be replaced with the real decisions once they're locked in, rather than filled with specifics that haven't actually been built yet.
What I Learned
Scoping a genuinely multi-feature system (habits, notes, snippets, alarms, reminders, and planning) without it turning into five disconnected mini-apps under one roof has been the main design challenge so far; the pieces need to actually talk to each other to be worth combining at all.
Too early in the build for deeper technical lessons learned yet. This section will be filled in honestly as development continues.