I had same issues. Late 2021, I had developed a platform to beta using V3. I had to build a strong case for why to move to v4. Mind you v4 wasn;t as comprehensive as it is now when I made this decision.
Here are some things I considered:
- v3 had issues with is_null filters (This just fetches everything to first item) - fixed in v4
- v4 planned to support typescript (It does now)
- v4 has a very robust filters system
- More and rapid support of the plugins ecosystem
- Dark mode on the Admin (If you fancy this)
- The plugins marketplace is paradigm shift (So much possibilities)
You can check the release notes on github for more info Releases · strapi/strapi · GitHub
Some cons
- Migration from v3 to v4 is not simple. (DB models is different, plugin system is different, core is adjusted,)
- v4 is not as customizable as v3 (I couldn’t edit some core functions without making a clone of strapi)
If you remain inn v3 you might find yourself branching out your own clone of v3 to catchup with some of the things solved in v4. If you can upgrade as soon as you can.