GDevelop for live service games?

Hey everyone,

I’m exploring the idea of using GDevelop to build a live service game, something that evolves over time with frequent updates, player feedback loops, and ongoing content drops. Think “games as a service” (GaaS), where the experience grows post-launch rather than being a one-and-done release.

I’d love to hear from anyone who’s tried this approach with GDevelop:

  • How do you handle frequent updates? Is the workflow smooth for pushing new content, balancing changes, or seasonal events?
  • What’s your setup for analytics? Are you using built-in tools, third-party integrations, or custom solutions to track player behavior and retention?
  • Monetization strategies? Have you implemented ads, in-app purchases, subscriptions, or other models? What’s worked (or not)?
  • Any major drawbacks or limitations you’ve run into with GDevelop in this kind of live service context?

I’m especially interested in how well GDevelop supports iterative design and player-centric development. If you’ve built something that updates regularly or relies on long-term engagement, I’d love to learn from your experience

1 Like