From mobile to consoles and back to mobile
summary
Small indie studio moves from mobile to consoles, ships a 2016 top‑down shooter on Xbox One/PC, then ports a drunken brawler that previously hit 600,000 downloads back to consoles and now funds a new premium mobile version. Console builds take 1–2 years per game versus a few months for mobile, require certification that can take weeks to a month, and force hundreds of platform specs (achievements, suspend handling). Tradeoffs: single‑device optimization and launch visibility among tens of releases per month instead of thousands.
AI-written summary · about
chapters (6)
- 0:00Introduction and team background
- 2:07Shift from mobile to console development
- 5:16Key differences in console vs mobile development
- 8:05Pros and cons of console development
- 10:33Market size and future trends
- 12:02Platform convergence and streaming
related talks
44mPanel: Playing by New Rules – Game Development Under the Digital Markets Act.
22mSuperstar Session: The Future is Cross Platform
01h 04m“Mobile App Development for Multiple Platforms with Visual C++, 2016"
21mHow to Monetise Mobile Games Beyond the App Stores
15mThe 'Rami Ismail market overview' - Insights on what devs should expect
01h 00mCross-Platform Mobile App Development with Visual C++
40mPanel: The Rise of Real Attribution in PC & Console Gaming.
21mGaming platforms: Going beyond distribution