Project Status & Roadmap Discussion: Community Perspective on Development Activity

[mstroeve]

Opening Remarks

First and foremost, I want to express my deep appreciation for Quasar Framework. It's a truly excellent project that has proven invaluable to our development efforts over the years. The framework's comprehensive approach to building VueJS applications across multiple platforms is genuinely impressive, and we remain strong believers in its capabilities.

Our Observation

As long-term users and sponsors of the Quasar project, we've been following the development closely. Over the past several months, we've noticed a gradual decline in development activity. While the framework continues to receive maintenance updates (which we greatly appreciate), the pace of new features, significant improvements, and strategic direction seems to have slowed considerably.

Additionally, we observed that the roadmap hasn't been updated in approximately a year, which makes it difficult for the community to understand the project's future direction and planned focus areas.

Intent of This Discussion

I want to be clear that this observation comes from a place of genuine interest and support, not criticism. We care deeply about this project's long-term sustainability and success. We're curious to understand:

1. Current Priorities: What are the main focus areas for the project right now? Where is the team's energy being directed?
2. Roadmap Status: Are there plans to refresh or update the public roadmap soon?
3. Project Sustainability: How can the community best support the project's continued development and growth?

Our Commitment

We remain committed to Quasar and would like to explore how we can contribute more meaningfully. Whether that's through increased financial support, active participation in development, bug reporting, or other forms of contribution—we're interested in finding ways to help move the project forward.

Thank you for all the hard work that has gone into building and maintaining this framework. We look forward to hearing your thoughts and insights about the project's direction.

[LadIQe]

Hi, it saddens me too, because I have been pushing this framework in my job since v2. At that time, it was a breath of fresh air for Vue 3 ecosystem. In my opinion, its still the most mature framework out there, but lack of discussions, new updates, something, doesnt help.

it looks like Vuetify 3, or in near future, Vuetify 4 will take the lead as the most mature and still maintainable framework for Vue 3, which is kind of surprising due to some caveats like missing customization for components compared to even Vuetify 2.

Long story short, we are considering to switching to Vuetify 3/4 or giving PrimeVue a try.

[tinohager]

Yes, from my point of view, the development that we have seen and felt has also stalled. There was already a discussion about this last year. At that time, it was promised that development would continue.

Personally, I would also be interested to know whether this is a financial problem or why it is no longer continuing. I would also be very grateful for open communication so that I can continue planning my own projects.

• What is the future of Quasar? #17726

Development activity was quite limited last year.

[DocBouCou]

I am also wondering whether this is a financial issue or rather a “human” one (for example, health issues affecting the people behind the project).
I am finally starting to earn money from my project, built with Quasar, and I was thinking about making a donation. Sadly, though, I am unsure whether donating is still possible or if there is still someone actively behind Quasar.
I fully understand that open source involves a huge amount of work, often for little reward and under a lot of pressure. It can be mentally challenging to keep going. I would therefore like to send my greetings, support, and love to the maintainers of Quasar, especially @rstoenescu and @pdanpdan (and everyone else).

[tinohager]

@DocBouCou Donations can be made in two ways

• https://github.com/sponsors/rstoenescu
• https://opencollective.com/quasar

[DocBouCou]

Thank you for your answer.

I know that, technically, we can still donate through these links.
However, when I said "I am unsure whether donating is still possible", I meant that if the people supposed to get the money through the donation are not here anymore, then does it make sense to donate? I genuinely mean that they might as well be dead or something like that, for all we know (I do not say that in a bad way, accidents may happen - sadly - ).

[kalvenschraut]

Quasar is great and I don't regret picking it when we moved off of bootstrap-vue so we could get to be able to use vue 3. We actually had started a rewrite in vuetify 2 back in 2021, but seeing that vuetify 3 being in a usable state for my company was a long off I made somewhat risky decision to shift to quasar instead. It worked out well and had really good interactions with the maintainers and submitted PRs when I could. I consider this decision to be one of the best decision, for our applications, I have made in my career. Since Quasar helped accelerate our development in several key areas we started sponsoring the project.

Over past year I have noticed the slow down and getting issues fixed even when we submitted PRs for them started to become really painful, I sadly started to have concerns. Now with vapor mode coming out, I have doubts that quasar will ever be able to offer vapor compiled components due to heavy reliance on render functions. Not at least without significant effort on the teams part, which doesn't seem realistic with current state of things. Finally after my experience with quasarframework/quasar-ui-qcalendar#459, I started having to unfortunately consider another alternative.

I really do hope quasar can continue with its maintenance and with a proper roadmap and commitments would relieve a lot of my concerns. UI frameworks are major risk for a business if they stop receiving consistent maintenance so I had to start looking to migrate that risk. Until more detailed info is available I have landed on prototyping migrating to Vuetify 3 as their components could be compiled to vapor components as is. On top of their outlined plans and discussion I have had with John gives me confidence with their future outlook.

[NureddinSoltan]

+1, I’ve been feeling the same way.

I check the project almost every month hoping to see updates, but progress has been slowing down. The tech landscape, especially in 2025 moved very fast , and most major frameworks have received significant updates.

I really want to start using Quasar seriously for all my personal projects, but tbh, I’m hesitant to fully commit because I’m worried about investing a lot of time and then getting stuck later. Vue Vapor is coming soon and I’m excited about it, but realistically it doesn’t seem like it will land in Quasar anytime soon, assuming active development continues at the current pace.

That said, I genuinely want Quasar to stay as strong as it has always been. For me, it’s still one of the best frameworks in the Vue ecosystem. It feels like the main bottleneck right now is simply how much responsibility falls on the core team.

To help move things forward, I’d like to suggest a few ideas for transitioning toward a more community-driven model:

• Working groups: Create small, focused groups (UI components, docs, build tooling, social media, etc.) and empower trusted community members to review and merge PRs in those areas. This could significantly reduce the load on the core team and prevent stagnation.
• Bounty-backed roadmap: Since many of us are sponsors or work at companies that rely on Quasar, we could fund specific GitHub issues. Contributors who complete those tasks could receive the bounty, making development more sustainable.
• Better visibility: Even a short monthly “state of the framework” update, via Discord, GitHub, or an online meeting, would go a long way. It reassures the community that the project is alive and helps new contributors know where to jump in.
• Sustainable funding: To be fair, maintaining a framework of this size with a small team is extremely hard. At some point, since it’s a small developer team, we will need somebody to work on it full time, and that requires money. I’m sorry, but at the end of the day we need money, we have families to take care of. If thousands of users donated just 5$ per month (basically the price of a coffee), it could be a big thing for the team working on the project, while for most of it would be very affordable.
  The problem is that @DocBouCou was asking about the donation state, and whether the people receiving donations are still actively maintaining the project. That’s a fair concern. Right now, we don’t really have an organized, transparent structure to donate through.
  We need something similar to a lot of organization like Django Software Foundation, a Quasar fellowship program that supports maintainers in a structured and transparent way, where people can maintain Quasar as paid, organized work.

I’m really invested in Quasar and happy to help however I can. Curious to hear what others think!

[agroebe]

Thanks for starting this discussion. I've been waiting for an opportunity to share some of my thoughts as I suspected that I wasn't the only one with concerns.

I share the same appreciation shown by others. I'm grateful to everyone who has helped to maintain Quasar and get it to where it is today. When we decided on Quasar in 2021, we quickly noticed how competent, bug-free, and feature-rich it was. It was the best option in the ecosystem at the time. We are grateful for all of that.

That said, I am also concerned about the future of Quasar. I've noticed that the pace of new feature development, and even routine maintenance, has vastly slowed down. That is abundantly clear from commit history, release cadence, new components and features, or any other metric you look for. Highly requested features (ex: #5115) are going stale despite having proposed solutions, PRs, and in that example even an indication from maintainers that it may get attention. In a recent example, it took a month to introduce support for Vite 7, which may or may not have even been done without the community contribution.

Those concerns aside, I'd also like to address the future of Quasar from a slightly different perspective...

My fear is that even if Quasar magically snaps back into active development tomorrow, we would still be using an outdated framework with a questionable future, devoid of any advancements or exciting innovations made in the broader ecosystem in the meantime. I think it has shown signs of neglect long before it became obvious. The following are sticking points for me personally:

• Material Design: Quasar seems to still be very aligned with iterations of Material Design from the mid 2010s. The prevailing look-and-feel of the recent web has largely abandoned Material Design, at least in terms of aesthetics. The result is that, and I don't like to say this, Quasar looks clunky and outdated.
• Tailwind: Has become very popular amongst frontend developers and is here to stay. I'm aware that Quasar doesn't need to officially "support" anything for us to use Tailwind. However, other frameworks such as PrimeVue and Nuxt UI do have first-class support for Tailwind and have dug much deeper into including it as a core capability in their frameworks.
• Nuxt: Of course, Quasar supports two targets in Vite and Webpack. However, it still is missing official support/module for Nuxt, which the Vue ecosystem is slowly but surely standardizing around.
• Headless: A common theme adopted by many UI frameworks in recent years is to build around headless, unstyled primitives that give the consumer full control over their own UI. Frameworks like Nuxt UI and PrimeVue strike a perfect balance of pre-styled components out of the box, that are still based on headless primitives (Reka UI and Volt) to give you full control. This allows you to build around whatever styling solution you want, whether it be CSS, CSS Modules, SASS, Tailwind, PandaCSS, etc,. Quasar has no semblence of flexibility around styling.
• Figma: All of Vuetify, PrimeVue, and Nuxt UI have official Figma UI kits. Quasar does not.
• AI tooling: It is exceedingly common for UI libraries, and frankly any open source software nowadays, to provide AI tooling such as MCP servers or llms.txt. Vuetify, PrimeVue, and Nuxt UI all do so. Quasar has not lent much attention to this. It is not currently positioned well for the AI "era" if you will.

Anywhere you look, you'll find that all of these and more have become baseline expectations, standards of what is considered a "modern" UI framework. Of course, each of you can decide for yourself how important these points are to you and your product. For me, they are important.

I wanted to raise this perspective to offer my own opinion on what Quasar might be prudent to focus on going forward, assuming it is still maintained. This isn't me saying Quasar can't get there. But I think it's important to be honest about what it would take for many in the ecosystem, including myself, to consider Quasar as a modern, future-proof, serious option. I myself am currently evaluating Nuxt UI and PrimeVue with a lot of success and interest.

Having seen other options, I frankly no longer consider Quasar to be an exciting, forward-looking option for serious projects. For me, it is starting to show its age, and prove itself to be a project conceived in 2016. My views may seem harsh. But the important reality is that, for most of us, the UI library is one of the most important decisions we can make. And if we choose wrong, we can't exactly snap our fingers and untangle ourselves from it. Thus, I think every single option on the market deserves a lot of scrutiny.

The great news is that these are the types of things that can be addressed with active development and time. Similar to the points made by others, a status update, roadmap, or even just a committment to the project would go a long way!

Again, thanks for all you do as maintainers and I am appreciative of how solid Quasar has been for us for the past 5 years! I'm eager to see where it goes and I am hopeful to see some good signs in the near future.

[dmonterde]

AI is hitting hard as tailwinds is also in troubles.

[mstroeve]

@rstoenescu could you please inform us?

[HannesOberreiter]

From our experience migrating from Vuetify (when vuetify was stuck with vue2) to Quasar, we found it helpful to wrap every Quasar component internally (e.g., /primitives/Input.vue). This approach means that if you ever need to switch frameworks, you only need to update your primitives—something we’ve successfully done before and can recommend to others (at least for components, we do not really on many build in quasar features).

Quasar’s flexibility also makes it easy to implement custom native testing frameworks or different builds (like PWAs). Since Quasar is open and adaptable, you’re not dependent on external tools (e.g., waiting for quasar-testing to support a specific Cypress version).

We still support Quasar, though not as much as we did three years ago. Our AI agents work seamlessly with the framework, and Quasar remains our go-to for fast prototyping. Unlike heavier frameworks such as Nuxt, Quasar’s lightweight, meta-framework nature minimizes vendor lock-in—a huge advantage, especially for those of us still maintaining legacy Nuxt projects will understand this problem.

Cheers
Hannes

[pich]

Quasar has created real value for many of us in production and remains one of the most capable meta-frameworks in JS/Vue. What we need now is visibility and shared direction. If capacity is the constraint, let’s address it openly. Clear 2026 priorities and delegated review areas would unlock a lot of community energy. I’m willing to support and contribute where it’s most helpful. With structured collaboration and clearer direction, Quasar can stay competitive in 2026 and beyond

[rstoenescu]

I need to put a rest on all worries. Quasar is here to stay and lead. That is my hard promise to everyone.
It will become very obvious with Quasar v3, which I am currently planning. But more on this just a bit later. We will need your input on some decisions that we'll take for the new major version.

However, please help us financially to achieve our goals. We are in dire needs of funding.
https://github.com/sponsors/rstoenescu

[DocBouCou]

Glad to hear! Thank you! :-)

[NureddinSoltan]

That’s perfect 🚀 . Glad you’re working on Quasar V3 🙌 . Is there any information about what Quasar V3 will include, aside from the projects one? Because this list hasn’t been updated for more than a year, it seems outdated. Is there somewhere else I can follow updates?

[mstroeve]

Great to hear this, @rstoenescu

One small but important note: the long silence before this response did cause some sponsors and potential donors to hesitate or reconsider. Transparent, regular updates — even short ones — go a long way in keeping financial support flowing. People are much more likely to sponsor a project they can see is actively steered. Looking forward to what's next! 🙌

[rstoenescu]

If all goes according to plan, it's gonna be a great year for Quasar!