Andrew G. Stanton - Wednesday, April 22, 2026

Local-first isn’t the hard part, at least not in the way most people assume.

I built Continuum with ownership and control at the center.

That was the priority.

Not ease of use, onboarding, or polish.

Those things mattered, but they came second.

The goal was to make sure that what you create is actually yours.

That your identity isn’t tied to an account, and that your work doesn’t live inside a system you don’t control.

And that part is working (actually really well now).

But over the last month, something has become clearer.

Some of the friction in Continuum is just product work that needs to be improved.

The onboarding can be simpler.
The flow can be clearer.
The language can be more direct.

That part is on me.

But there’s another part that’s different.

Continuum runs locally.

There’s no default account.
No central system holding everything together.

That changes the experience from the very beginning.

You don’t just open a website and start typing.

There’s a step before that.

And that step matters.

It’s part of what makes ownership real.

But it also introduces friction that most people aren’t used to.

That’s not something I can completely remove.

But I can make it feel more natural.

Right now, the friction shows up in smaller ways:

• needing to understand what an “identity” is
• switching between identities
• knowing when something is saved vs published
• understanding what actually happens when you click “publish”

None of these things are inherently difficult.

But together, they create just enough resistance that a new user has to slow down and think.

And that’s the problem.

Most people don’t want to slow down and think just to get started.

They want to open something and use it immediately.

If local-first isn’t the hard part, then why isn’t everyone doing it?

Because most of what makes modern tools feel simple depends on central control.

A single account.
A single source of truth.
A system that quietly manages everything for you.

That makes onboarding easy.
It makes the experience consistent.
And it removes a lot of decisions from the user.

But it also creates dependency.

When you don’t have that central layer, you have to solve those problems differently.

You still need things to feel simple.

But you can’t rely on:

• a single account to anchor everything
• a backend to resolve conflicts
• a system that hides complexity by taking control

That’s where the real difficulty shows up.

Not in running something locally.

But in designing an experience that feels just as natural without relying on those shortcuts.

That’s a much harder problem.

And it’s the one I’m working through now.

Because if it isn’t simple, most people won’t use it.

And if people don’t use it, it doesn’t matter how important the underlying ideas are.

That’s the reality.

So the goal isn’t just to be different.

It’s to make something that people can actually use without having to think about it first.

And that’s what I’m working toward.