User voice first
Each stage’s priority is set by real users’ requests. Waitlist feedback directly influences the plan — there will be a voting mechanism too.
Roadmap
Where we’re heading
An open plan: what’s ready, what’s queued, what’s in the future. The plan is alive — priorities may shift with user feedback.
We start small — but we start right. Every stage must deliver real value to real users. Below are four stages, each with its goal, contents and status. Stages ship sequentially — the next one does not start until the previous is stable. That’s not slowness, it’s discipline: one reliable feature beats ten half-baked ones.
Now — in development
v0.1: the core trio for Windows
The first public version. Three key functions — typing, conversion, normalization — run stably on Windows 10/11. Goal: close the main pain of people who type in Uzbek every day. In this version stability comes first: wide testing, checks on real documents. Few features — but each reliable.
- Real-time typing correction
- One-click conversion (Latin↔Cyrillic)
- Unicode normalization (U+02BB)
- Fast/Hybrid modes
Next
v0.2: browser extensions
Most text is written in the browser: email, social media, online documents. Chrome and Edge extensions will bring UzType into the browser — correct typing without installing a separate program. The extension works right inside the browser: you type in a text field — correction happens there. No need to open a separate window.
- Chrome extension
- Edge support
- Deep web-app integration
Planned
v0.3: macOS and Linux
After Windows, other operating systems are next. Same engine, same experience — just on your platform. Written in Rust, the port is technically easy: the main work is adapting to each system’s specifics. A native experience for each system: integration with macOS keyboard services, compatibility with major Linux desktops.
- Native macOS app
- Linux (major distributions)
- Settings sync
Future
v1.0: professional writing assistance
Not just letters — the quality of the whole text. Style suggestions, deep spelling analysis, tone checking. At this stage UzType grows from a simple “fixer” into a full writing assistant. This is a long-term goal: first the core trio must become perfect. Writing assistance builds on top of them — without a solid foundation, the building won’t stand.
- Style and tone analysis
- Extended spelling checks
- Corporate features for teams
How we decide
For the plan to live in practice, not on paper, we follow three principles. They guide every decision — which feature ships first, which one waits:
Small but working releases
Instead of big promises — small but stable versions. Every release is tested, documented and can be rolled back if needed.
Openness
The plan and changes are published openly. If there’s a delay — it’s announced with the reason. This page is updated every quarter.
Current focus
The team is now working on v0.1 stability: wide testing on real documents, covering rare cases, simplifying the installer. In parallel, a browser extension prototype is being prepared — but it will ship as a separate release and won’t delay v0.1. We openly report what’s done at each stage. The next news — via the waitlist.
The plan is approximate — timelines get refined with user feedback and test results. Join the waitlist to follow the news.