Dev Journal

Dev Journal #3 — When Someone Says “I Don’t Get It”

Every project has a moment where someone looks at what you’re building and says, “I don’t understand what this is.”

That happened yesterday on Reddit. Someone checked out Epheme and replied:

“Sorry, I didn’t get your app.”

And honestly? That’s fair — because Epheme isn’t an app.

It’s a correction. A direction. A way of thinking about software that we’ve slowly forgotten.

When I replied, I said exactly that:

“It’s not an app — it’s a concept, a thought.”

But that didn’t help them much either. They still felt lost. And that’s okay. Not everyone will understand Epheme immediately, and not everyone will care. But the exchange forced me to articulate something important.

So here’s the simple version I ended up giving:

“I want to help make software that doesn’t require user accounts, doesn’t promote tracking, and focuses on privacy and running in the customer’s environment — not on remote servers. Old school.”

That’s the heart of it.

Not nostalgia.

Not anti-cloud ranting.

Just a desire to bring back something we quietly lost: software that belongs to the person using it.

---

“Congrats, you just invented desktop applications.”

The conversation didn’t end there. The same user replied:

“Congrats, you just invented desktop applications. If you want to create apps on the web and distribute over the Internet, welcome to SaaS.”

And that’s the moment I realized why Epheme exists.

Because today, we treat software like it has only two modes:

1. Desktop application

- runs locally

- you own it

- no accounts

- no tracking

- no vendor dependency

2. SaaS

- identity and accounts

- cloud storage

- logs, metrics, analytics

- monthly payments

- vendor-controlled infrastructure

- dies when the vendor dies

We’ve forgotten there’s a third option.

---

The Missing Middle

What I want — what Epheme is trying to explore — is this:

Web applications that behave like desktop applications.

The web doesn’t have to mean SaaS.

The browser doesn’t have to mean surveillance.

Online doesn’t have to mean centralized.

We’ve just normalized those assumptions.

---

Why This Matters

That Reddit exchange reminded me that Epheme isn’t obvious.

It’s not a product category people are used to.

It’s not a pattern the industry encourages.

It’s not something most developers have seen modeled.

But that’s exactly why it’s worth building.

Epheme is about reclaiming the idea that software can be:

Not rented.

Not tracked.

Not dependent on a company’s uptime or business model.

Just software that does what you need, when you need it — and then gets out of the way.

---

Closing Thought

If someone says, “I don’t get it,” that’s not a failure.

It’s a sign that you’re working in a space that needs new language, new patterns, and new expectations.

Epheme isn’t trying to reinvent the desktop.

It’s trying to remind the web what it used to be capable of — before everything became a service.

And if that takes a few more conversations like this one, I’m okay with that.

Back to Journal