🔍🧠 QA Testing Powered by Frecuencia Gamer – Polishing Diet Survivor with Feedback, Bugs & Big Ideas!

Hey players and game dev enthusiasts! Today we want to share something special from behind the scenes of Diet Survivor: our amazing collaboration with Frecuencia Gamer and their talented students from the QA Testing for Video Games course.

This testing process was crucial to polish the game, uncover hidden bugs, and most importantly, receive fresh and insightful ideas that helped us level up the overall experience.

Throughout multiple testing sessions, the students played, analyzed, and gave structured feedback with a critical and constructive eye. Each one brought a unique perspective that made a real difference. Here's a shoutout to their contributions:

👤 Sebastián Sánchez

Helped us see the value in making the game stand out with a unique identity. Thanks to his input, we strengthened the visual style and humorous personality that make Diet Survivor truly memorable.

👩 Valentina Uribe

Focused on ways to make the game more immersive. Her suggestions led us to revisit sounds, animations, and small details that bring players deeper into the action.

🧑‍💻 Dylan Paternina

Thought like a product designer, offering ideas on how to keep players engaged and how to approach monetization without compromising the fun. His insights helped us think long-term.

🎯 Julian Torres

Provided valuable feedback on the game's presentation and shared a SWOT analysis (Strengths, Weaknesses, Opportunities, Threats) that helped us better understand Diet Survivor’s position in the indie market.

This kind of collaboration shows the power of working together with new talent in the industry. Huge thanks again to Frecuencia Gamer for facilitating this meaningful experience for both sides.
➡️ Learn more about their course here: frecuenciagamer.com/nuestros-cursos/qa-testing-para-videojuegos

Thanks to their support, Diet Survivor is now a stronger, more fun, and more polished game — and the best part: we’re still learning and growing every step of the way!

Would you like to read another devlog about how we’re applying these suggestions in future updates?