The immediate goal is a useful small practice loop, not a long feature list. This roadmap separates what you can use now from work that still needs evidence. It does not announce a desktop release date.
What comes next, and what has to earn its place
A public roadmap for Ptichi, with clear evidence gates instead of invented release dates.
Now: make one comparison worth hearing
The public website offers authored exercises, explanations, sources and a demonstration of the method. Those are usable reading and practice materials. The demonstration is not a recording of your voice or evidence of improved speaking.
In the desktop project, the current focus is the path from a first visit to a first take: understand the method, check the microphone, record, listen, change one thing, compare and try new words.
Before calling this ready: real capture checks, clear unavailable states and a first-run path people can navigate without guidance. macOS and Windows need their own evidence.
Next: test usefulness with people
A small observed pilot should answer questions the build cannot:
- Do people understand what the exercise asks them to change?
- Can they hear a relevant difference without seeing which take came second?
- Does that change remain comfortable and work on a new sentence?
- Where do they stop, hesitate or misunderstand the feedback?
Before widening access: resolve failures that block practice, choose the comparison interaction from observed evidence and provide a reviewed, privacy-conscious feedback route. A successful second take alone is not enough.
Later: expand only what travels
Practice with your own message, a first-week sequence and a clearer record of transfer and effort are possible next steps. They depend on the small loop proving useful. Longer curricula and broader distribution come after that evidence, not ahead of it.
What would change the plan
If listeners cannot hear a useful difference, revise the exercise or its premise. If a measurement is unstable on ordinary microphones, keep it unavailable rather than giving it a polished score. If a feature adds steps without helping the practice, remove it.
The next meaningful milestone is evidence that supports a decision. A longer roadmap is easy to produce; a reason to keep a feature takes more work.
