Roadmap
Track the development of @vuetify/v0. Milestones are organized by time horizon:
Now — Actively in development, due within 30 days
Next — Planned for the near future, due within 90 days
Later — On the radar, no immediate timeline
Completed — Released milestones
Priorities may shift based on community feedback and technical requirements.
Release Calendar
Expected dates for the v1.1–v1.5 minor releases, the net-new features landing in each, and the existing preview features on track to graduate to stable as of that release.
v1.0.0
Wednesday, July 22, 2026 16 graduatingExpected dates and graduations are strategic targets, not commitments — they may shift with community feedback and technical requirements.
Now Stable
v1.0 is here. A headless UI framework for Vue 3 — composables and components that handle the logic so you can own the design. No opinions on styling. No markup you can’t change. Just primitives that work.
Alpha opened on April 7, 2026 for feedback; beta hardened the APIs; the release candidate locked the v1 stable set. The stable v1.0.0 release shipped July 22, 2026 — the public API surface is now committed under SemVer↗︎.
Road to v1
Stable release. v0 1.0.0 shipped July 22, 2026.
What v1.0 means
This isn’t a proof of concept. v0 is feature-complete for v1 and ready to build with.
The stable set is locked. 16 composables and 17 utilities are marked stable — breaking changes require a major version. See the maturity matrix below for the full breakdown.
v0 is being built directly into Vuetify. The composables and patterns here are the same ones powering Vuetify’s next generation. This isn’t a side project — it’s the core.
Development continues. v1.1 and beyond are on the roadmap above, and preview APIs graduate to stable release by release. Every regression, gap, or rough edge you report still gets priority — if something feels wrong, say so.
Try v0
Whether you want to explore in the browser, scaffold a project, or integrate with your AI workflow — there’s a path for you.
Want a complete working reference? DevKey is the example project that ships with v0 — a full Vue 3 + Vite + UnoCSS app built on @vuetify/v0. Clone it, or run pnpm create vuetify0 to scaffold your own copy.
Get involved
Report a bug or request a feature — Open an issue↗︎ on GitHub.
Ask a question or join the conversation — Find us on Discord↗︎.
Contribute code — PRs are welcome. See the contributing guide for how to get started.
Maturity Matrix
Graduation Criteria
Every feature climbs the same track. Its level tells you what you can rely on today; the gate between levels is exactly what it takes to move up.
- Draft13 features
Planned, not yet implemented. There is nothing to import.
Gate to PreviewAuthor promotes in the landing PR- Implementation landed
- Unit tests cover happy path and edge cases
- Docs page with a working example
- Preview86 features
Implemented, tested, and documented. The API may still move in minor releases — every change lands in the release notes.
Gate to StableMaintainer decision- API unchanged for 2+ minor releases
- Edge cases and failure modes tested
- SSR-safe, or explicitly browser-only
- Accessibility reviewed
- Benchmarked when performance-critical
- Stable49 features
Production-ready. Breaking changes require a major version.
Gate to MatureMaintainer decision- Proven in production downstream
- Adapter ecosystem where applicable
- API frozen — breaking changes need a major
- Mature0 features
API frozen. Downstream frameworks — Vuetify itself — depend on it.
A feature leaves the track when a better pattern supersedes it. Deprecation always ships with a migration guide and a removal timeline — nothing disappears in a minor release.
FAQ
v0 is a headless UI framework for Vue 3. It provides composables and renderless components that handle behavior, state, and accessibility — without any styling opinions. You bring the design; v0 handles the logic.
v0 is the foundation layer being built directly into Vuetify’s next generation. The composables and patterns in v0 are the same ones that will power Vuetify’s styled components. You can use v0 standalone or alongside Vuetify.
Yes. v1.0.0 is stable and shipped July 22, 2026. The v1 stable set is locked, and the core is already being used to build Vuetify itself. Preview APIs may still see minor, documented adjustments.
No — the stable set is locked, and breaking changes to it require a major version. Preview features may still evolve in minor releases, with every change documented in release notes. Alpha gathered the feedback; beta locked things down; the release candidate was the final validation pass before v1.0.
v0 is style-agnostic — use UnoCSS, Tailwind, plain CSS, CSS Modules, or whatever fits your project. The docs and examples use UnoCSS. The theme plugin exposes CSS custom properties that you can map to any framework’s color system.
Yes. All composables and components are SSR-safe. Nuxt integration is documented in the getting started guide.
Stable means battle-tested with no planned breaking changes. Preview means feature-complete and documented, but the API may evolve in minor releases. Draft means experimental and subject to major changes. See the graduation criteria above for the full ladder and what it takes to move between levels.
Open an issue↗︎ on GitHub. Include a reproduction if possible — the playground↗︎ is a good way to create one.
See the contributing guide. PRs are welcome for bug fixes, new features, documentation, and examples.
Join the Discord↗︎ community. You can also use the AI assistant built into the docs — look for the Ask AI button on any page.
Sponsor Fund Vuetify0, get your logo on the docs
For companies whose product is built on Vuetify0. Logo across the docs, every page, and the README. One sponsor at a time.