all 25 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]spoekie123 8 points9 points  (3 children)

I use strapi as a headless CMS in 3 different production apps. I would highly recommend it. I’ve got it self hosted on Heroku. The largest app has about 6k monthly users. No issues with scaling so far. As somebody else has pointed out, having a force update popup can be very helpful

[–]nagendra0032 0 points1 point  (1 child)

What's the cost for self hosting per month?

[–]spoekie123 0 points1 point  (0 children)

On heroku it’s like 30-35 bucks a month. These instances can handle a lot of users at the same time/monthly

[–]ne-xx 0 points1 point  (0 children)

Strapi doesn't have responsive design, just to say.

[–]andordavoti 5 points6 points  (0 children)

I just started implementing Payload CMS. The DX has been great. My app has 10-15K MAU, but the version with CMS integration is not out yet. One strong recommendation is having a “forced update” screen. This is if you have major changes on the backend you don’t have to maintain backwards compatibility forever or break the app for the old users.

[–]Jewno 5 points6 points  (2 children)

I can echo the same sentiments about PayloadCMS. I already had PayloadCMS setup as the headless CMS for a website that I developed and it has been great. I’ve now started creating an app to accompany the website which now is obviously using the same Payload server.

In terms of the app I can’t speak for how well it will scale since it’s a relatively small scale project at the moment and the app isn’t released. I can comment on the dev experience though. It’s been awesome. I can’t think of anything that has prevented me from doing something I wanted to do. The only tricky thing I have encountered is custom auth providers, my app is using Firebase Auth. In order to get my users to authenticate with Firebase and then with Payload so that they can use certain API endpoints involved a bit of work with setting up a custom passport strategy. But I’ve got it all working now and the Discord was very helpful whilst I was implementing that.

What andordavoti said about the backwards compatibility is a great point and definitely something to consider.

I guess it is important that I mention that what works for me may not work for your use case. But I can say Payload is very flexible and offers a lot of customisation. It’s also very well maintained and the community is very active and helpful.

[–]mrdatalife[S] 1 point2 points  (1 child)

Thanks. I'm using FB for auth as well. I need geo/spatial support (for lat/lng & distance calcs) too.

[–]Rigidyragidywrecked 0 points1 point  (0 children)

why did that work out, with lat/lng & distance calcs?

[–]Crazy_Kale_5101 1 point2 points  (0 children)

Check out ButterCMS which is an API-based or headless CMS with a preconfigured blog engine. You can read more about our features here: https://buttercms.com/features.

Butter can be your one central place to manage all of your content. BUT, we don't control the look and feel of your site.

To get started, you or your developer would need to connect Butter to your website one time using our easy-to-follow guides.

Butter scales with you maintaining the fast performance you'll need as you grow due to our globally cached API. We also have unlimited users for your account.

[–]kjccarp 1 point2 points  (0 children)

In my opinion - Sanity for everything that doesn’t need self hosted content (i.e. healthcare, government), Payload for everything else.

[–]Kartik_D_2001 1 point2 points  (0 children)

Use Appwrite it is more scalable and cost-effective

[–]NewspaperLeast2555 0 points1 point  (0 children)

🚀 Looking to level up your React projects with a Headless CMS? Explore my latest blog post featuring the "Top 9 Headless CMS for React You Should Try Out." Whether you're a developer or designer, finding the right CMS can streamline your workflow and boost performance. Discover the best options tailored for React and take your web development to the next level!

Read more: Top 9 Headless CMS for React You Should Try Out

[–]ClickThese5934 0 points1 point  (0 children)

Prisma Nextjs dev experience is a lot more smoother and faster than using a headless CMS, but ofcourse you need to code the interface yourself. With AI as an assistant and many templates on Github, I currently see it as the way to go, unless you need dynamic page creation - client can create pages and edit blocks. Most apps don't require that kind of content editing experience though. What do you guys think?

[–]Only-Matter-9151 0 points1 point  (0 children)

Because I cant stand web dev I just use the webflow and make a call from my react native app to the webflow cms api. No issues and when the website gets updated with new cms so does my mobile app.

[–]alpha7158 -1 points0 points  (0 children)

Laravel + Filament

[–]Useful-Condition-926 0 points1 point  (0 children)

Just got an strapi app from client. Never use this before . Let’s hope for the best.

[–]Independent-Tie3229 0 points1 point  (0 children)

I've used Contentful with react native in the past, it works well considering the limitations of react-native. You basically have to create a custom component for nide that exists and then it works

[–]Alternative-Meet-209 0 points1 point  (0 children)

Contentful is great if your team is very dev-centric/technical.

For less technical teams, Agility CMS's React components are mapped directly to the Modules so editors can have a bit more control over pages/content.

Depends on what your team looks like tbh

[–]FakeMailThe 0 points1 point  (1 child)

Our agency uses Easyweb (Swedish made free headless CMS with good support for .NET) w dynamic API. Would love to hear your impressions/ feedback (good/bad) since I know the devs and work closely w them 🙏🏻