That is really useful to know. That is actually the way I’m planning on using strapi, but wanted a second opinion before assigning resources to it.
Just to give you some context of what I’m trying to do, I really like Strapi for the blog/mktng funnel/frontend website side. So far so good.
It gives me control, and everything is JS, so I don’t need to use different resources for frontend/app/backend, which is very useful tactically in early stage (of a project or startup - allows versatility in using my resources).
We are building out an Iot play, so the end user functionality will probably be a meteor app. Meteor does pub.sub nicely, and I need it to work with timescale db, which is optimised for continuous time logs (i.e. every single sensor). Designed nicely, it can be webapp & mobile app so really good fit.
The challenge is, we need client org admin somewhere. So clients have users within them, who have access to different Iot devices - where does this sit? I don’t really want it in a react native app with meteor middleware, because now the admin sits in a mobile app which is not ideal.
It would be super useful to have Strapi play this role, and first class support for pub/sub for all the admin-y stuff, so i just reuse the frontend website as a baby client facing admin app would totally be a reason to move off the community version as it plays nicely into the expanded role support.
Hope above makes sense. You guys are building a solid product, the work is very much appreciated and in an ideal world can pay you guys soon too. Thanks so much.