The project is an interactive Hunger Games simulator where users can run different Games, select tributes, simulate events and battles, view victory odds, explore tribute profiles, and create custom scenarios.
Some of the current features include:
⚔️ Full Hunger Games simulations
👊 1v1 fight simulator
📊 Victory odds calculator
👤 Tribute profiles and stats
🏛️ District information
🧠 Hunger Games quiz
🏆 Victor/leaderboard features
🎬 Dynamic events, alliances, betrayals, and eliminations
🎯 Custom Games and tribute combinations
I’m interested in improving the architecture and potentially expanding the project with more advanced functionality.
I’d especially like feedback from developers who have experience with FlutterFlow, Firebase/backend architecture, game-state management, APIs, animations, or real-time applications.
A few things I’d love advice on:
What would be the best way to structure a simulation engine in FlutterFlow?
How would you handle complex game states and dynamically generated events?
What backend/database architecture would you recommend?
What is the best approach for scaling if many users run simulations simultaneously?
Are there FlutterFlow-specific techniques that could make the UI and simulation experience smoother?
Would you recommend keeping the simulation logic in FlutterFlow/custom actions, or moving the core engine to a separate backend/API?
The current website gives a good idea of what I’m building: https://hungergamessimulators.com/
I’d really appreciate feedback, architectural suggestions, or examples from anyone who has built something similar.
Thanks! 🙌
May the odds be ever in your favor.