From There and Back Again! Porting from Mobile to Console and Back Again
summary
Gems of War moves from console back to mobile by focusing on textures: over 3,000 textures are reprocessed, switching Unity compression formats per platform, adding asset postprocessors to pad non-square art, and generating separate alpha textures for ETC1 on Android. Platform defines and plugins keep one codebase while build switching sometimes takes up to seven hours. Result: a 500 MB reduction on console builds and overall build size cut by about half, while preserving cross‑platform saves and support down to 512 MB devices.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:25Game trailer and platforms
- 3:17Project timeline and engine
- 5:46Unity multi-platform challenges
- 8:22Porting game considerations
- 13:41Existing game pain points
- 17:55Platform code and Unity tools
- 27:13Texture optimization
- 39:06iOS texture compression
- 44:34Android texture compression
- 48:50Compression quality vs support
- 50:15Conclusion and tips
related talks
41mBuild apps for Billions
20mCI/CD Infrastructure for Efficient Mobile Game Development
35mGame Development Infrastructure
30mA Deep Dive into a Cross-Platform Build Farm
22mAdvanced Workflows for Multi-Platform Mobile Development
43mSecret Sauce of Cross-platform Mobile App Continuous Delivery
34mARM Migration Made Practical
56mAI Infrastructure as Part of CI/CD for Mobile Game Development