I feel that yii3 is very good, and I can’t help but want to use and update the project. May I use it for a new project? Or for local use, what should be noted if it can be used?
I feel that yii3 is very good, and I can’t help but want to use and update the project. May I use it for a new project? Or for local use, what should be noted if it can be used?
I don’t think that you have to excuse for anything! :] That is a very good question.
Did you notice “Looking for Yii 3 progress?” button in the homepage? When you click it, you’ll see a message that says:
Released 95/115 packages
That’s 83% of all packages already released. I’d say that it is pretty much mature for starting a new project.
Of course everything depends on the size of your project and number of end-users your design it for. If you have 10-20 persons teams working constantly on this single project only then you may soon reach the place where some package is still not available for Yii 3. But for smaller projects I’d definitely consider it.
I have started a new project a year ago. “Still” in Yii 2. If starting a new project right now, I would still go for Yii 2. But that has nothing to do with the maturity if Yii 3. I am simply not convinced that I need Yii 3. I think that the dev team has done a really, really good job creating Yii 2 and I have everything that I need right there.
And even, if support for Yii 2 will eventually be stopped (first general, then security fixes) then I am still in the lucky position that I am developing mostly projects for a very-small to small group of users. Sometimes even for just a couple of them. So I think even then I’ll be able to handle things myself.
But, if the scale of your project or group of potential users is large then I’d definitely go Yii 3.
Short answer is: If all packages you will depend on are released, then Yes!
Thank you for your perfect and detailed explanation. I will take a look at the current completion progress and see if the completed modules meet the needs of the project. 
Thank you. I have reviewed the completed list and it should meet the project requirements。
I inspected Yii3 about 6-8 months ago, but my conclusion was that Yii2 is better.
For me “maturity” of something means not only its development progress, but the most important – number of people who are actively using it. You don’t want to change your old buck to a brand new car that there are no spare parts for it and nobody seriously know how to change a tire in it, right?
Yii 3 progress goes forth, much, much slower than anticipated, but still ahead. But the number of people and projects actively using it is risky small, if you ask me.
That’s for a brand new project that I plan to start, I still decided to go Yii 2 instead.
As good as yii2 is, it may not be able to withstand the future expectations of developers as PHP advances
I am not saying, that it will be. Even now there are probably things added to PHP 8.0, 8.1 and 8.2 that hasn’t been re-implemented to Yii 2 and won’t be re-implemented ever, because Yii 2 is or soon will be in maintenance mode.
I am just saying that given progress of Yii 3 and number of active users of it, Yii 2 is still a better choice for starting from scratch a brand new production project – that is what is asked in this question.
Yii2 is still great for Projects, but your assesion of Yii3 is wrong. There is great direct support to Yii3 from core developers. That is like a guarantee for getting spare from the manufacturers. Nothing is better than that!
As long as the manufacturer and spare parts provider actually drives the roads, instead of sitting in the office! 
Core developers tend to be busy with developing framework itself. Usually we get immediate response, but on some issues or questions we need to wait a couple of days or weeks. Which is perfectly normal.
That’s why I still think that any framework or technology must first have a strong out-of-dev-team in-community support to be mature enough for production-grade projects.
I don’t mean to change your mind. That’s just my personal thinking.
You could just post the link to Telegram which is pretty active
Maybe I’d be getting lynched for this, but I’ll say my 2 cents.
I’ve been Yii2 developer for a long time. Since 2015. I really really liked it’s approach. I’ve been developing with custom CMSs and Symfony before 2015. And when I saw Yii2 and it’s approach, I immediately loved it. In Symfony at the time, the big problem was documentation. I mean there was documentation on how the system works, they’d written about the core concepts and all that. But as a website/webpp developer you needed practical things. How to do translations, how to do slugs, how to do catalogs with filters, etc. And when you read Yii2 documentation, you immediately saw that Yii2 was written by developers for developers. Everything was documented and was about solving practical everyday problems, not some abstract concepts like in symfony.
So, I’ve been following Yii2 development and Yii3 development for years and years. And the core idea of Yii3 being developed from scratch and incompatible with Yii2 rubbed me wrong from the start, back in 2019 or what year this was. Rubbed me wrong for 2 reasons. The scope of Yii3 seemed so big, that I thought it would never be released or it will take a very long time. Nobody would develop on Yii3, because Yii2 exists and it already works. But then at some point developers announced that there would be Yii2.2 which would be transitional. Which is great idea, but it should have been there from the start.
So Yii3 was started in like 2019 and here we are in 2025 and it still not being released and developers still:
IMHO, the whole approch should be. Abandon Yii3 for now. Switch to releasing Yii2.2 ASAP. Then gradually release 2.4, 2.6 and 3.0 at some point.
As an analogous situation. Imagine core php developers would start developing php 10.0 which would be totally incompatible with 8.x. First they would take too long. And if they ever released it, it would be like python 2.7/3.0 situation. Both version will exist for more than 10 years. Currently Yii2/Yii3 seem to be going in the same direction as python 2.7/3.0
You can still use Yii2 it isn’t going anywhere.
2.2 which will keep Yii2 torch burning is brewing.
But if you want modern and shiny features, then go Yii3. Some people have projects running on production as we speak. So yeah, all released packages can be used in production with stable API.
Unreleased packages can get bc break wile being finalized but I doubt it will be anything serious at this point.
No need to Switch to Laravel, at all