Roadmap principle: TBM prioritizes stability, speed, clarity, and a better daily workflow over adding features simply to make the product look larger.
Core workflow
- Project Desktops with rapid switching
- Main Tabs, Sub-Tabs, and visual asset grids
- Smart Visual Pointers for local files, folders, apps, links, and notes
- Drag, drop, reorder, move, and copy workflows
- Focus Mode, resizing, and floating Bubble
- CSV, bookmark, and curated-topic import workflows
- Visual customization, backup, and licensing tools
Polish the core
- Continue stability and performance refinement
- Improve consistency and feedback across drag-and-drop actions
- Make setup, recovery, and HELP pathways even clearer
- Refine keyboard, accessibility, and high-resolution behavior
- Strengthen update safety and quality assurance
Useful, not noisy
- Richer reusable project structures and templates
- Additional safe import and export workflows
- Optional shortcuts for repeated working-set actions
- Further cross-project quality-of-life improvements
- User-requested refinements that preserve TBM's lightweight nature
How roadmap decisions are made
A feature belongs in TBM when it reduces friction without making the product heavier, less predictable, or less private. Improvements are evaluated against four questions: Does it make real project work faster? Does it preserve the user's existing files and tools? Does it keep the interface understandable? Can it remain lightweight and reliable?
No artificial release promises
The roadmap is directional. Items can move, change, or be removed as testing and user feedback reveal better solutions. A roadmap item is not a contractual commitment or a promise of a specific release date.