It's not about productivity. It's about presence.

When we made floe, we started from an experience: Want to write. Open a blank page. Then stuck.

It's not that there's nothing— there's some invisible pressure that keeps that first sentence from landing.

So floe's design asks: What is that pressure? Can we remove it?

First choice: writing prompts are "invitations," not "commands"

Many writing tools give you clear prompts: "Write down three things you accomplished today" "Describe a moment you're proud of"

These prompts aren't wrong. But they assume: you should have "things accomplished," you should have "proud moments."

When you haven't accomplished anything today, when you're not proud of anything, these prompts become a form of invisible accusation.

floe's writing prompts are more like: "If this feeling were a kind of weather, what would it be?" "If it had a voice, what would it say?"

It doesn't assume you should have anything.

It just gives you an angle to help you pull out vague feelings a bit more easily. You can answer, or not answer.

You can follow it, or completely ignore it and write your own thing.

Invitation, not command.

Second choice: AI is "reflection," not "replacement"

AI can do many things. It can help you rewrite, polish, give suggestions, tell you a "better version."

But in floe, we deliberately don't use AI that way.

Because when AI starts telling you a "better version,"

you start doubting whether your version is "not good enough."

You start asking: "How should I write?"

Instead of: "What just happened to me?"

floe's AI is more like a mirror.

It helps you organize:

Which words keep appearing.

Which paragraph suddenly became intense.

Which sentence seems to be avoiding something.

It won't say "you should change it to this."

It just reflects: "this is how you just spoke."

And then you decide—

"Oh, I've been using this word"

"Oh, what I care about is this"

"Oh, I wrote this part especially intensely"

Reflection, not replacement.

Third choice: "quiet" is a design

floe's interface is very quiet.

No many colors, no many buttons, no notifications, no badges.

Not because we can't make those. But because we know:

When you're writing something, what you need isn't more stimulation.

What you need is space to "hear your own sentences.

If the interface keeps talking to you, it's hard for you to hear what you're saying.

Fourth choice: no goals, no scores

Many apps have "streak," "days completed," "daily goals."

These designs keep some people using it. But they also create pressure for others.

When you've checked in for 30 days straight and miss one day, you get a feeling of "I messed up."

So "journaling" goes from "I want to see myself" to "I must maintain this number."

floe doesn't have these.

Not because we don't care about retention.

But because we care more about: When you open floe, it's because you "want to," not because you "should."

It's not about productivity. It's about presence. This is floe's core. Not output, not efficiency, not growth. But "presence."

Present to your own feelings.

Present to this moment's shape.

Present to those small, but real signals.

We don't know if floe will succeed. But we know: If there's a tool that can make it easier for people to "meet themselves," without adding pressure,

then it's worth making.