← Back to blog

Why I'm Building Still

I used to start my mornings with a ritual that looked organized from the outside.

Open a handful of browser tabs — the news sites and blogs I followed, the ones I'd been meaning to catch up on since last week. Switch to my portfolio tracker to check the numbers, then my bank's website for the cash picture, then log into each of my investment accounts separately because none of them talked to each other. Pull up Google Calendar to remember what I'd committed to today, then check Keep for notes I'd jotted down, then find a sticky note on my desk with something I'd written yesterday, then remember there was also a file somewhere on my Mac with a running list I'd abandoned months ago.

Try to remember what I was learning about last week — something about deep-sea cartography, or Byzantine architecture, or the history of Westerns, or whatever rabbit hole I'd fallen into on Wikipedia — and not find it anywhere. Think about a friend I hadn't spoken to in months, feel the familiar pull of that, do nothing. Close everything and start working.

The apps were doing their jobs. But the constant context-switching had a cost — not in minutes lost, but in something quieter. The sense that I was always mid-thought.

All these tabs and apps were tracking the same person — me — and none of them knew the others existed. My reading life was invisible to my financial life. My daily intentions were scattered across so many places that I wound up losing track of most of them. The people I cared about weren't in any system at all, just in my head, quietly drifting.

I had a dashboard for everything and a sanctuary for nothing.


The breaking point

There was a specific afternoon — and I remember it clearly because it was the moment I stopped tolerating the situation and started taking notes.

I'd spent twenty minutes trying to find an article I'd read three weeks earlier. Something about attention and rest. I had a vague sense of where I'd encountered it — a bookmark, maybe, or something I'd written down, or possibly just a tab I'd closed and assumed I'd find again. I checked everything I could think of and found nothing useful.

Then I looked at my task situation. Tasks in Calendar. Tasks in Keep. Tasks on paper. Tasks in a file I'd made months ago and stopped opening. Dozens of good intentions, distributed across a dozen places where I'd never see them again. Not because I was disorganized — I'd tried every system. But each system I adopted became, over time, a graveyard of good intentions. The friction of switching between them meant the only tasks I actually did were the ones I could remember without looking.

I closed the laptop and wrote two words in a notebook: fewer places.

That's not what I built. But that's where it started.


So I started building Still

I've never liked context switching. Not as a software developer, and not as a human being. There's something I've always valued — the calm of doing one thing at a time, investing fully in a single aspect of life rather than flitting between them. Today's digital world works against this in almost every way. The tabs, the apps, the sites, the platforms — each one a separate surface, each one demanding a different kind of attention, none of them aware the others exist.

I wanted something else. The digital equivalent of a quiet pasture where I could tend to the parts of my life I cared about — as a serene ritual, not a frantic hop between digital domains.

The name came before the app did.

I wanted something that felt like a pause. A place where you could look at your life clearly without being told what to do about it. No streak pressure. No badge to earn. No notification pulling you back in at 7 PM on a Wednesday. Just your own data, arranged so you could actually see it.

Still, as in: quiet. Still, as in: not moving. Still, as in: even now, it's okay.

I didn't set out to build six things. I set out to build one: a reading hub that surfaced what I'd chosen to follow, not what an algorithm decided I should see. But once I started, the connections became obvious. The person who wants to read more intentionally also wants to see their finances in one place. Also wants their daily intentions to live somewhere they'll actually look. Also wants to hold onto the things they learn instead of losing them. These aren't separate needs. They're facets of the same one.

A life that's actually visible to itself — and one where the parts know about each other, where something you read can become a subject you explore, and someone drifting from your life can surface as a quiet nudge in your daily intentions.


The app that says no

Here's the thing about building for calm: you have to say no constantly.

Not to user requests, necessarily — to your own ideas. Every feature that seems reasonable in isolation adds to a whole that, if you're not careful, becomes another system demanding your attention.

I built a Canvas hub. It was genuinely beautiful — a freeform whiteboard where you could place notes, images, and connections freely. I spent three weeks on it. Then I looked at what I already had in Discovery, where you can save things you find on the web, annotate them, and build collections. The Canvas and Discovery overlapped. They didn't complement each other; they competed. So I deleted the Canvas entirely.

Three weeks of work, gone.

That decision is probably the most honest thing I can say about what Still is trying to be. The question isn't "is this feature good?" The question is "does this feature belong here?" A feature that belongs somewhere else doesn't belong here, even if it's excellent.

Still has no notifications. Not "notifications off by default" — no notifications. There's nothing to push. Your data doesn't live on a server somewhere, so there's nothing to push from. If you want to check in, you open the app. If you don't, it waits.

Still has no streak pressure. You won't see a counter go gray because you missed a day, or feel your progress reset to zero. Where Still does track habits — your consistency with daily intentions, for instance — it surfaces that as quiet observation, not a counter you're racing against.

Still has no social layer. Your financial data, your relationship notes, your daily intentions — none of it is visible to anyone else, ever, because it lives on your device, not on a shared server.

Still does use AI — for summarizing what you've read, exploring subjects, reasoning about your finances. But it's opt-in, model-agnostic, and works with your own API key. The AI serves you; it never sees more than you choose to give it.


Six lenses on a life

Still is organized around six hubs. Not modules. Not widgets. Lenses.

Vellum is the way you choose to see the world through what you read — a curated feed of sources you've decided matter, not an algorithm's guess at what will keep you scrolling.

Means is the quiet awareness that financial health is health — a clear view of what you hold, how it's moved, and where it might be heading, without the noise of five separate logins.

Intent is the small act of deciding, at the start of each day, what actually matters — three things, not forty, and the permission to be done when they're done.

Discovery is the way a curious mind moves through the world — loose associations, unexpected depth, the ability to pick up a thread you left months ago and follow it somewhere new without losing it again.

Presence is the recognition that the people you love drift away slowly, without drama, unless you make a quiet practice of keeping them close.

Pulse is the bird's-eye view of yourself — not biometric data, not optimization metrics, just a gentle awareness of how you've been, so you can notice the patterns before they become problems.

Together, they're not a productivity system. They're the shape of a life worth paying attention to.


Built from research, not just instinct

I should be honest about where two of these hubs came from.

Vellum, Means, Intent, and Discovery: those are the obvious ones. I felt those pains directly — the scattered tabs, the disconnected finance apps, the task graveyards, the lost gems from Wikipedia rabbit holes.

Presence and Pulse were different. They weren't apps I'd tried and abandoned. They were quieter things — more like patterns I'd noticed and then pushed away.

I'd always lamented how people drift apart as life gets busy. Not dramatically, not with any falling-out — just the slow accumulation of weeks that become months that become "I should really reach out." I never had a tool for the awareness that preceded that. Something that didn't nag, but also didn't let important people slip completely off the radar.

And with Pulse: I had this persistent itch that there were patterns in my life I simply wasn't seeing. Patterns in how I felt, how I slept, how I engaged with the week — things that were shaping my days without my knowing it. I wanted a way to discover what those patterns were, without turning it into a quantified-self obsession.

Research confirmed what I'd begun to feel. People consistently neglect two things when life gets busy: their awareness of their own wellbeing, and their relationships. Not because they don't care — because no tool makes it easy to pay gentle attention. The calendar reminds you of appointments. Nothing reminds you that you haven't spoken to someone you love in four months.

I built Pulse and Presence because the research and the feeling lined up. They may not be everyone's first reason to try Still. But they might be the most important reason to keep using it.


Your data never leaves your device

This part matters more than it might sound.

Still runs entirely in your browser, backed by a SQLite database stored in your browser's local storage. There is no Still server holding your financial data. When you close the tab, your data isn't traveling anywhere — it's sitting on your device, waiting for you to come back.

I made this choice early and I've defended it through every feature decision since. Local-first means your data belongs to you in a concrete sense: no company can quietly change the privacy policy on it, no bankruptcy can take it, no server breach can expose it to strangers — because there is no server.

Cross-device sync is on the roadmap. When it arrives, it will be end-to-end encrypted: your data will travel between your own devices without ever being readable by Still's infrastructure. The local-first foundation stays. Sync is built on top of it, not instead of it.


I'm building this in public

Still is a one-person project. I'm a software engineer. I've been building this in my spare time — at first to solve my own problem, now because the problem seems worth solving for more people than just me.

I'm going to keep building it in public: sharing what I'm learning, what I've broken, what I've deleted. Not because building in public is a growth strategy (though it is), but because it's more honest than shipping in silence and hoping people trust you.

If this resonates — if you've also felt the friction of too many places to look, or the quiet guilt of letting people drift, or the vague unease of not really knowing how you're doing — I'd love for you to follow along.

Thanks for reading.

— Jonathan

Be among the first

Get early access when Still launches. One email, no spam.

By joining, you agree to our Privacy Policy. Your email is the only thing we store.

Questions? hello@stillapp.life