The Collaboration Paradox
Real-time collaboration sounds straightforward. Everyone sees the same board. Changes appear instantly. No one is ever looking at stale data.
In practice, it’s one of the hardest problems in software. Two people move the same card simultaneously. Someone updates a task title while another person is editing the description. A user on a slow connection submits a form that was already changed by a teammate.
Most tools handle this badly. Either they lock everything (“someone else is editing this”) or they silently drop one person’s changes. Neither is acceptable for a team that’s actually working.
How FlowEra Resolves Conflicts
FlowEra is built on a local-first data layer powered by PowerSync. Each client maintains a local SQLite database, and changes sync to the PostgreSQL backend in real time when online. The sync protocol handles conflict resolution at the data layer — not in application code.
The result: if you and a teammate both update the same task simultaneously, both updates are recorded and merged based on last-write-wins per field. If you changed the title and they changed the status, both changes survive. There’s no “your version vs. their version” dialog to dismiss.
Typing Indicators in Chat
When a conversation is happening around a task, FlowEra shows typing indicators in real time via WebSocket. You see when a teammate is composing a reply before it arrives, which prevents the awkward “we both just replied to the same message” situation. This is a small detail, but it changes the feel of in-app communication significantly.
Presence Without Overhead
We deliberately chose not to add cursor presence or per-character sync to the task editor. That kind of feature looks impressive in demos and creates noise in daily use. When four people’s cursors are moving across the same task card, no one can read anything.
Instead, FlowEra shows you who is active in a flow — a small presence indicator — without turning the board into a multiplayer game. You know your team is working. You don’t need to watch them type.
Notifications: Pull vs. Push
Collaboration only works if people know when something needs their attention. FlowEra’s notification system distinguishes between:
- @mentions — direct pings that appear at the top of your notification feed
- Watching — subscribe to any task or entity and receive updates when it changes
- Flow activity — summary of what happened in a flow since you last checked in
You control which notifications you receive. The default is conservative — only explicit mentions and direct assignments. Opting into broader watching is a deliberate action.
The Knowledge Base Layer
Real-time collaboration isn’t just about tasks. When your team is writing documentation — a spec, a rundown, a post-mortem — FlowEra’s knowledge base editor supports concurrent editing with automatic conflict resolution. Multiple people can edit the same page simultaneously and changes merge cleanly.