Blog
Behind the scenes of LowFlow
The build journal of LowFlow, published as it happens.
Episode 25
Opening LowFlow to many more platforms
Weeks without writing, because I was busy connecting real data sources. Here is where things stand.
Episode 24
After building, you have to show
After months of building in the shadows, it is time to show what LowFlow actually does.
Episode 23
Thinking of LowFlow as plug and play
Install, pick your platform, a few clicks. Whatever can be prepared in advance should be.
Episode 22
Software should be able to explain itself
If I have to explain every feature myself, something is missing from the product. The guide is now part of the journal.
Episode 21
A trader can have several accounts
A trader often has several accounts. LowFlow has to follow them without ever mixing the data.
Episode 20
Watching habits appear
A single day can be misleading. What keeps coming back over time is what becomes visible.
Episode 19
When the history starts to get serious
A few dozen trades pose no problem. The real test comes when the history gets serious and everything still has to stay fast.
Episode 18
Reviewing a day differently
A number tells part of a day. Looking at the whole day, not just trade by trade, reveals what happens between the trades.
Episode 17
Building a trading memory
A number tells part of a trade, rarely the whole story. Screenshots and context keep what memory rewrites.
Episode 16
The trader chooses
A journal can quickly become too prescriptive. LowFlow provides the tools, it doesn't impose a method.
Episode 15
Understanding multiple markets
Every platform speaks its own language. The journal has to translate, not force the trader to adapt.
Episode 14
Not depending on a single data source
Every platform structures its data its own way. A journal cannot depend on a single source.
Episode 13
Building visibility without losing the product
Getting a product known can become a second full-time job. So visibility has to become a system, not a mountain.
Episode 12
Making LowFlow visible
What good is a solid product if no one knows it exists? Visibility gets built too, one piece at a time.
Episode 11
Building the cockpit
A system can work and still leave you in the dark. Automatic never means invisible.
Episode 10
Testing LowFlow like a real customer
A real machine, a real card, a real journey: testing LowFlow like someone who just bought it, not like the one who built it.
Episode 9
Building the customer journey
Every piece can work on its own — and the whole can still be broken. Connecting the steps so the customer moves forward without seeing the machinery.
Episode 8
From project to product: putting LowFlow online
The site, payments, licensing, distribution — the pieces finally connect and LowFlow becomes a real commercial product.
Episode 7
Making the system work for me
Automating without losing control: payment, licensing, and updates become automatic — and the Control Panel becomes mission control.
Episode 6
When LowFlow Had to Be Protected
Becoming a real commercial product changes everything: protecting the licenses, the updates, the infrastructure — without ever turning LowFlow into complicated software to use.
Episode 5
Getting LowFlow to the trader
Turning software into a system that can deliver itself: the client account, the license verified remotely, and why an update is never just a file swap.
Episode 4
When LowFlow could no longer stay entirely on its own
Why staying 100% local wasn't enough once LowFlow became a real product to distribute — the birth of the Control Panel, and the separation between the trader's data and the infrastructure needed to manage accounts, licenses, and updates.
Episode 3
From HTML to App: turning LowFlow into a real application
Moving from an HTML journal to a real Windows application: choosing a hybrid app over Electron, keeping the trader's data separate from the application, and why selling a product ended up requiring a server and an API.
Episode 2
The prototype: when the journal became a real tool
Turning the idea of the journal into something practical enough to actually be used — context, screenshots, statistics that were never imposed, and the moment the prototype started outgrowing what a simple HTML project could handle.
Episode 1
At first, I just wanted to build my own trading journal
LowFlow didn't start as a company. At first, I just wanted to build my own trading journal — something that actually matched the way I worked.