The story behind the Flow apps

I find a problem.
Then I build the fix.

I’m Hans. This is how a teacher ended up making apps.

I’ve been a teacher for over 20 years, in classrooms and in the district office.

I’m not a programmer.

But I notice what gets in my way. And now I can fix it.

Voice Flow on iPhone

It always starts
with something small.

Every Flow app began as a problem in my own day.

Meeting Flow

Meeting notes made on my own devices, not someone else’s servers.

See Meeting Flow

Focus Flow

A countdown I can see, and a break that gets me to breathe.

See Focus Flow

Home Flow

Our paper week plan, on every phone. It has to beat paper.

See Home Flow
Voice Flow recording, with the spoken words appearing on screen
Save Flow on iPhone: recent saves and collections, each with a thumbnail
Home Flow on iPhone: this week’s list, with what’s done, what’s left and who has each task

Then I kept going.

Five apps. Four websites. And a few tools I use at work every week.

  • A family travel editor
  • Spin, a name wheel for workshops
  • A slides hub for my trainings
  • A dashboard for my Mac

How I build.

People call it vibe coding. I don’t write the code. I bring the problem.

  1. 1

    Notice.

    Something gets in my way more than once.

  2. 2

    Say it.

    I describe the problem in plain words, the way I’d explain it to a friend.

  3. 3

    Build.

    AI writes the code. I try it on my own phone and Mac, and say what’s wrong.

  4. 4

    Live with it.

    I use it every day. Whatever still bugs me becomes the next fix.

It’s the same in a classroom.

Spin: a name wheel I use in every workshop.

In a school office.

A slides hub where teachers find my sessions.

In a small business.

A website for The Story Well’s legacy films.

What will you create?

What problem will you solve?

If you lead a school, a district or a small business and something keeps getting in the way, I’d love to hear about it.