Shared

Explore

Shared

Shared

Mastering Retention Podcast

Ep.88: Increasing the longevity of your game

⁠

https://www.youtube.com/watch?v=EwajZNWg3RI⁠

⁠

🎙️ Mastering Retention Podcast: Designing Long-Term Engagement with Jonathan Durr

Host: Tom Hammond, Co-founder of UserWise

Guest: Jonathan Durr, Co-founder of FoxBear Games

⁠

Introduction

👋 About Jonathan Durr:

Began his career at EA Tiburon as a QA tester, working on titles like Madden NFL.

Transitioned into game design after four years in QA.

Worked at THQ, Kabam, and FoxNext Games.

Played a key role in the development of Marvel Strike Force.

Currently the Co-founder of FoxBear Games, partnered with Wildlife Studios.

⁠

Founding FoxBear Games

🏗️ Partnership with Wildlife Studios:

Wildlife approached Jonathan with an opportunity to create a new studio under their sponsorship.

FoxBear Games was established with creative control and Wildlife's support.

The studio benefits from collaboration with other experienced teams within Wildlife's network.

🎯 Focus Areas:

Avoiding hyper-casual games and massive projects requiring large teams over many years.

Leveraging Jonathan's expertise in mid-core to hardcore mobile games.

⁠

Challenges in Mobile Game Development

🌊 Navigating the Red Ocean:

Recognizing the difficulty in finding unique opportunities in a saturated market.

Understanding that even well-made games can fail in soft launch due to scalability issues.

🧠 Strategic Approach:

Emphasizing the importance of data-driven decisions to identify audience needs.

Acknowledging that making successful games often involves educated guesses and risks.

⁠

Designing Features for Marvel Strike Force

🔍 Competitive Analysis:

Studied successful games like Heroes Charge and Star Wars: Galaxy of Heroes.

Identified key features that resonated with players in the hero collector genre.

🗣️ Player Interviews:

Engaged with elite players from other games to gather insights.

Asked questions about what they loved, their engagement drivers, and pain points.

Used content creators and community leaders to reach top players.

✅ Validating Assumptions:

Tested initial design hypotheses against player feedback.

Ensured that new features addressed real player desires and problems.

⁠

The Importance of Regularity

📈 Defining Regularity:

Regularity measures how consistently players engage with the game.

A player who logs in seven consecutive days becomes a "regular."

Regulars have a high likelihood (around 98%) of returning the next day.

💰 Business Impact:

Regular players constitute about 70-80% of the game's revenue.

Focusing on regularity helps in designing features that enhance daily engagement.

⁠

Understanding Different Player Behaviors

👥 Player Personas:

Acknowledged that players have different play styles and schedules.

Example personas:

"Schizophrenic Nancy": Plays in short bursts whenever possible.

"Planned Out Suzy": Schedules longer, dedicated play sessions.

🎯 Designing for Core Players:

Prioritized designing for competitive players who are deeply engaged.

Allowed casual players to enjoy the game at their own pace without diluting core features.

⁠

Designing for Long-Term Engagement

🛣️ Planning Ahead:

Recognized the need for meaningful player goals extending three years and beyond.

Developed a rough roadmap for future features and content expansions.

🌌 Introducing End-Game Content:

Created features like Dark Dimension as challenging, long-term objectives.

Provided players with a "North Star" goal to work towards over time.

🔄 Content Treadmill:

Continuously added new challenges to keep the game fresh.

Balanced between offering new content and maintaining game stability.

⁠

Live Operations (LiveOps) for Long-Term Games

🎪 "Running the Show":

Implemented a strategy to introduce something new in the game daily.

Scheduled events, character releases, offers, and messages to keep engagement high.

🛠️ Sustainability Challenges:

Addressed the risk of developer burnout due to constant content creation.

Emphasized the importance of sustainable practices to maintain team health.

🎉 Event Pacing:

Planned major updates or events once or twice a year.

Included smaller monthly events to maintain player interest without overwhelming them.

⁠

Communicating with Players

📣 Transparency and Roadmaps:

Provided players with regular updates on upcoming features and bug fixes.

Conducted bi-annual roadmap presentations to align player expectations.

🤝 Community Engagement:

Involved top players in testing and providing feedback on major features.

Fostered a sense of collaboration and trust between developers and the community.

⁠

Potential Pitfalls in LiveOps

⚠️ Managing Player Feedback:

Recognized that acting on all feedback could harm game balance.

Avoided over-rewarding players, which could disrupt the in-game economy.

🐞 Dealing with Bugs and Errors:

Shared examples of offers with incorrect values (e.g., extra zeros).

Emphasized the importance of swift, fair responses to maintain player trust.

🔄 Learning from Mistakes:

Used errors as opportunities to create positive experiences (e.g., generous compensation).

Gallery

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.