Where Muse is going.
The roadmap represents direction rather than a promise that every item will be completed. Each item is either committed, exploratory or speculative — which keeps the roadmap from becoming a disguised feature list.
Foundations
- Continue developing the software
- Explore the technical foundations for clothing understanding
- Develop image-based clothing workflows
- Continue computer-vision and product-recognition exploration
- Clarify the first genuinely useful product experience
- Document experiments and technical findings
Making it concrete
- Make the wardrobe representation more concrete
- Improve recognition and structured garment information
- Develop matching and outfit workflows
- Test the user experience
- Connect technical capabilities into a coherent product flow
- Document real software demonstrations
Depth
- More sophisticated outfit generation
- Personal preference modeling
- More advanced recommendations
- Wardrobe analysis
- Better understanding of personal style
The longer arc
- An intelligent personal stylist
- Deep personalization
- Understanding wardrobe gaps
- More sophisticated fashion intelligence
- Richer connections between clothing, style, context and preference
Three levels of commitment.
- Committed
Intentionally being pursued.
- Exploratory
Being investigated, but not committed to.
- Speculative
An interesting future possibility.
Items move between lanes as the project learns. When an item moves, the reason is recorded in the project log or as a decision.
Not yet established.
Muse does not yet have a formal release-version history. Development milestones will be recorded once the project reaches versions that describe genuine states of the product, rather than milestones created for the sake of documentation.
Muse — active development. The project is evolving through product exploration, technical development, computer-vision investigation and software work.