• The friction problem
• Trust begins before first use
• The Apple process
• Why this matters beyond Mac
• Why I cared so much

Andrew G. Stanton - Thursday, April 9, 2026

Over the past few weeks, much of my energy has gone into one goal: reducing friction.

Not conceptual friction.

Not philosophical friction.

Practical, immediate, real-world friction.

The kind of friction that prevents someone from ever getting to the point where they can actually use what you built.

For a long time, Continuum primarily existed in development environments.

Docker. Terminal windows. Mapped ports. Shell scripts. Environment setup.

For me, that was normal.

I have spent decades building systems, working in terminals, managing local infrastructure, and troubleshooting edge cases.

But one of the hardest lessons for builders is this:

what feels normal to us often feels overwhelming to everyone else.

A product can be profoundly useful and still fail at the very first step.

The install.

That is why getting the native Mac application signed and notarized became so important.

This was not merely a technical milestone.

It was a philosophical one.

§The friction problem

For all the work I have poured into Continuum, one of the biggest barriers has never been the product itself.

It has been onboarding.

A user should not need to understand Docker to begin writing.

They should not need to run scripts.

They should not need to open Terminal just to launch a local-first authorship platform.

Even when someone is interested, every additional step creates an opportunity for hesitation.

Install Docker.

Pull images.

Start containers.

Check port conflicts.

Refresh the browser.

Confirm scheduler.

For a technical user, this may be acceptable.

For most people, it is enough to stop.

That is real friction.

And friction compounds.

Even worse, on macOS, unsigned applications create another layer of resistance.

The system immediately presents warnings.

The app is “from an unidentified developer.”

The operating system blocks execution.

The user must right-click. Choose open. Confirm intent. Override system trust signals.

At that moment, the question is no longer:

“What does this software do?”

The question becomes:

“Can I trust this?”

That moment matters.

§Trust begins before first use

People often think trust is something the product earns after usage.

I think trust begins much earlier.

It begins with the first interaction.

The download page.

The app icon.

The installation experience.

The absence of warnings.

The sense that the software belongs on the machine.

Signing and notarizing the Mac app was about removing that moment of uncertainty.

I wanted the experience to feel natural.

Download. Open. Run.

That’s it.

The software should not fight the user before it even begins.

This is especially important because Continuum is built around local-first sovereignty.

Ironically, many sovereignty-aligned tools introduce enormous friction.

They require users to sacrifice ease for ownership.

I understand why that happens.

But I do not believe it has to remain that way.

Local-first should not feel harder.

It should feel better.

§The Apple process

I will be honest.

Getting through the signing and notarization flow was not trivial.

Apple has built a system that strongly prioritizes trusted distribution.

From a security perspective, I understand this.

But from a builder’s perspective, it can be exhausting.

Certificates. Developer identity. Signing steps. Packaging. Verification. Submission. Notarization tickets. Stapling. Retesting.

Each stage introduces failure points.

Paths. Permissions. Bundle structure. Framework resolution. Metadata issues.

There were moments where it felt tedious.

But I kept returning to the reason.

If Continuum is about reducing friction for the user, then this work matters.

Invisible infrastructure work matters.

The user may never know what it took.

That is fine.

In many ways, the best infrastructure is invisible.

§Why this matters beyond Mac

This is not really only about macOS.

It is about a broader principle.

The best local-first software must compete with the simplicity of cloud-native products.

People have become accustomed to low-friction experiences.

Click a link. Create an account. Start typing.

That convenience is part of why centralized platforms became dominant.

But convenience often came at the cost of sovereignty.

Your drafts live in their cloud.

Your identity lives behind their login flow.

Your access depends on their servers.

Your work exists at their discretion.

Continuum is trying to reclaim ownership without sacrificing usability.

That means friction removal is not optional.

It is part of the mission.

§Why I cared so much

I care deeply about this because the philosophy of Continuum is not theoretical.

It is practical.

Ownership should be lived.

Your writing should remain yours.

Your identity should remain yours.

Your keys should remain yours.

But if sovereignty requires endless setup pain, most people will never choose it.

That is the reality.

This is why the signed and notarized Mac app matters.

It is not just a technical checkbox.

It is a statement that sovereignty can also be usable.

And honestly, after the last few weeks of build work, getting this across the finish line feels like a major step forward.

Not the end.

But a major step.