loatiBlog

Why Floati is built this way

The decisions behind Floati, with the real dates. I work on Floati alone from South Africa, and I started on 28 March 2026. Here is what I decided, and how it felt.

Course

Why I made a course about being watched

Blocking a tracker is useful. Understanding one changes how you see the web, and I wanted more people to have that.

Passed on: Block it and say nothing Chose: Show people how it works

1 view Compiler

Why I replaced a working compiler

The engine began with no compiler at all. Then it borrowed a good one. On 17 October I took that out and kept my own.

Passed on: Keep the one that worked Chose: Keep my own

Memory

Why the Floati browser remembers what you read

Six days into the browser I had to answer a hard question: why would anyone switch? My answer was not the one I started with.

Passed on: One more privacy browser Chose: A memory that is yours

Browser

Why I am building my own browser engine

I started the browser on 1 July and its engine the next day. It is the hardest thing I could have chosen, and I would choose it again.

Passed on: Build on another engine Chose: Write my own engine

Learn

Why Floati Learn exists

IT changes faster than courses do. So Learn is free, and it gets you understanding code and doing real work as fast as it can.

Passed on: Pay first, try later Chose: Free, code from lesson one

CV

Why the CV Builder is free

No account, nothing to pay, and the AI runs on your own device. That last part started as a money problem.

Passed on: Charge to download Chose: Free, no account

Privacy

Why Floati has no accounts

An account is the easiest thing to add and the hardest to take back. So I decided Floati would not have one, and let that shape everything else.

Passed on: Sign up to continue Chose: Nothing to sign up for

More to come. Want a decision explained? Email my@floati.life. Every message is read.