At first, pulling in trades seemed simple. One platform. One format. One file.
Then reality showed up. Every platform structures its data differently. Every broker has its own habits. Every data provider has its own access, its own limits and its own APIs.
And if LowFlow was going to become a real tool for several kinds of traders, it could not depend on a single source. That is where the idea of a more universal system started to take shape.
Today, LowFlow can already receive data in several ways: existing integrations, CSV imports and tools connected to the platforms. The next step is already clear: opening LowFlow further to APIs and external data providers.
That part is not fully settled yet. But it is no longer a question of whether it will happen. It is a question of time, access and integration.
The goal stays the same: LowFlow has to adapt to the trader's environment, not force the trader to adapt to LowFlow.
One platform today. Another one tomorrow. An exported file. A broker. A data provider. And eventually a direct API connection when access is available.
Behind that, it takes a lot of work: normalizing formats, recognizing instruments, understanding entries and exits, avoiding duplicates and keeping a coherent structure even when the sources do not speak the same language.
But for the trader, that complexity has to stay invisible. The journal stays at the center. The data sources orbit around it. Not the other way around.