How

How will Flow Will Be Implemented?

This section gets into the technical details of how Eliot intends to implement everything. According to market research, only a few tech-minded folks like Eliot will read this part, so we’ve placed it here and will focus up top on more exciting, high-level applications for Flow technology. (Don’t worry, we’ll have attractive diagrams for everyone else who’d rather be watching sports or going out on fun dates.)

1. The Core Philosophy

At its heart, Flow is based on Eliot’s career-long mission: empowering people to control their own data and connect with all kinds of complicated, disparate systems. Flow accomplishes everything through integration, but not the way most people might expect.

Instead of relying solely on traditional integration methods like open standards (HL7, FHIR) or APIs, Flow recognizes that many of today’s crucial systems—social media, messaging apps, business tools, and health records—aren’t very friendly to standard integrations.

2. Simulating Human Users

Rather than fight against the tide, Flow takes a different approach: if a system is hostile to integration, Flow simply imitates a human user. Vendors can put paywalls around their APIs, but they still need to let real people use their products. Flow leverages this by interacting with your systems just like you would—only with far less manual effort required on your part.

3. Flexibility with Standards

Of course, sometimes there are well-designed standards out there, and when they exist, Flow will use them too. It’s all about using the most logical, effective path for integration—whether that’s seamlessly working with recognized protocols or cleverly simulating a user to get the job done.