ROADMAP.md

TajsOS Roadmap

This roadmap is directional, not contractual. TajsOS is still experimental, so priorities may shift when the product becomes clearer.

Current product direction

TajsOS is moving toward a cohesive local-first system for:

• capture,
• execution,
• knowledge,
• review,
• life-domain organization,
• lightweight insight.

The goal is not maximum feature count. The goal is a system that feels coherent, deliberate, and satisfying to operate.

Current priorities

1. Foundation before expansion

• strengthen core architecture boundaries
• reduce ad hoc screen structure
• improve consistency of state, layout, and interaction patterns
• keep the domain model coherent

2. Polish a small number of core flows

Priority depth over breadth, especially around:

• dashboard / now surfaces
• notes
• tasks
• capture / inbox
• detail flows

3. Platform focus

Primary focus:

• Android
• Desktop

Secondary / later:

• web
• iOS
• richer sync and integrations

Near-term themes

Product

• make TajsOS feel more like one operating system and less like several disconnected tools
• sharpen the distinction between core objects and support layers
• keep domains/lenses intentional rather than incidental

UX / UI

• strengthen shell + scaffold consistency
• improve responsive behavior across mobile and desktop
• refine greeting / briefing / dashboard-like entry surfaces
• keep the visual identity tactile, high-end, and system-like

Data / architecture

• continue moving toward typed, explicit models
• reduce overloaded generic structures where they hurt clarity
• preserve local-first behavior as a default assumption
• keep cross-cutting layers like relations, schedules, and reminders first-class

Quality

• improve documentation discipline
• add tests where logic is brittle
• improve performance in high-frequency flows
• reduce accidental complexity

Not a priority right now

These are not “never”, just not the center of gravity right now:

• feature spam for the sake of feature count
• broad enterprise/team collaboration features
• premature settings explosion
• over-designed sync/server systems before the local model is solid
• flattening the product into a generic productivity clone

How to read this roadmap

If a proposed change:

• improves coherence,
• sharpens core flows,
• strengthens foundations,
• supports Android/Desktop quality,
• and fits the product identity,

it is probably in bounds.

If it mainly adds novelty, complexity, or fragmentation, it is probably out of bounds.