Strapi Review

PROS: Strapi lets us intuitively churn out a GraphQL API from the content type builder model. It has great lifecycle hooks too.

CONS: Initially, it doesn't support subscription processes upon setting up. Fortunately, I've found a great solution to such a problem. Now, Strapi works flawlessly for our operations.

PROS: Streamlines our model development process. That's even when we apply specific GraphQL API and rules.

CONS: It is difficult to use the access restrictions in the admin and API panels. Say, setting roles and rights, among other options. And I think that combining the API and admin management panels would streamline the functions.

PROS: Strapi is packed with tons of powerful functions for developing top-notch apps. But what makes it unique are its features such as the graphical API as well as useful components. It also offers different field types, including the JSON and those that are uniquely designed.

CONS: The Strapi Docker image is too bulky for production. It exceeds 1GB in size.

PROS: This CMS is completely awesome! It helps me set up and create cool rest API, and it comes with GraphQL support too. Also, I didn't experience any difficulties when personalizing the admin manager.

CONS: As of today, Strapi doesn't carry internationalization functions. However, I am looking forward to its release since it's included on the list of possible future features.

PROS: Helps me create a light CMS that circles on a dependable API. This tool has allowed me to begin easily by spending a couple of hours on documentation and video tutorials. Then, I've started developing my own CMS right away. And I use it for mobile app development as well as for end-user purposes during the production phases.

CONS: Moving from the development to the production panel is somehow rough. Although, this may mean that I need to get a better grasp of the tool. I got no big problem with Strapi.

PROS: Strapi is a superb headless CMS tool with unique functions. It is super customizable, plus it supports unbelievably quick API building.

CONS: Some policy restrictions for personalizing custom control actions don't meet my preferences. This has pushed me to find the right solution over a lengthy period.

PROS: It lets us build an API in a snap. Then we can insert data smoothly. We can begin from scratch and develop a robust headless CMS for back-end purposes in a few minutes. We do not even need to insert a line of code into the platform.

CONS: Strapi only has a small team of developers. It is probably the reason why it takes them a long time to build new features. It has minimal support from external contributors too. That could help in boosting Strapi a lot.

PROS: You won't have difficulties setting up and running Strapi. It is regardless of you being a seasoned or a newbie developer. It also sports an API that you can trust, and it has no artificially configured limitations. You'd love its reasonable pricing, too, especially when you compare it side by side with other SaaS solutions.

CONS: The most glaring disadvantage of Strapi is its lack of software development kits. I need to wait for a considerable amount of time for its new features to roll out as well.

PROS: It is a breeze to configure and begin any developing task. It also offers tons of features that are all easy to use and apply. Plus, it is easy to scale its interface.

CONS: Yes, it has a scalable interface. However, you need to apply some codes to make some tweaks. I hope this process would become more manageable.