Roadmap
A look at where Flow is going. Nothing here is a promise — priorities shift as we learn what matters most to users.
Current focus
Right now, most effort is going into stability, polish, and making the core editing experience feel right. That means:
- Improving fillable detection accuracy across more template types
- Refining ghost suggestion quality and latency
- Better error messages and compilation feedback
- Performance optimization for large documents
Planned features
These are things we'd like to build. Some are closer than others.
Editor improvements
- SyncTeX click-to-source — click a spot in the PDF and jump to the corresponding source code
- Project management — multi-file projects with
\inputand\includenavigation - Bibliography management — BibTeX/BibLaTeX integration with a visual reference manager
- Snippet system — custom reusable code snippets beyond the current template system
AI and intelligence
- Smarter context-aware completions for complex LaTeX environments
- Citation suggestions based on document context
- More writing nudge types for different document categories
Platform and ecosystem
- Plugin/extension API for community contributions
- More built-in templates covering additional use cases
- Improved CTAN browser with preview and search
Things we're intentionally not building
Flow has a clear scope. Some things are deliberately out of bounds:
- Real-time collaboration — Flow is local-first by design. Use Git for version control and collaboration.
- Cloud storage — Your files live on your machine. We won't add accounts, cloud sync, or remote storage.
- WYSIWYG editing — Flow is a source editor with preview. We're not building a visual LaTeX editor.
Share your thoughts
The best way to influence what gets built is to share what you need. If you have feature requests, bug reports, or ideas, we'd love to hear them.