The latest articles on DEV Community by Echo (@echolin). https://dev.to/echolin https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4186109%2F4c62c0c0-4ad9-4ad7-b500-1cadf625421a.webp https://dev.to/echolin en Echo Thu, 15 Oct 2026 07:42:57 +0000 https://dev.to/echolin/hi-im-echo-learning-how-games-actually-get-shipped-571i https://dev.to/echolin/hi-im-echo-learning-how-games-actually-get-shipped-571i <p>Hi everyone, I'm Echo.</p> <p>I'm interested in a part of game development that doesn't get talked about as much as gameplay or art: what happens to a game between "it runs in the editor" and "players download it from a store."</p> <p>That part turned out to be much less obvious than I expected. A few questions I've been reading about:</p> <ul> <li>Why can a mobile game show a high FPS number and still feel choppy?</li> <li>Why does a build end up so much bigger than the project folder suggests?</li> <li>What does the player actually download, compared with the file you upload to the store?</li> </ul> <p>I'm mostly learning from the official Unity and Android documentation, plus discussions from people here and elsewhere who have shipped real games. The docs answer a lot, but they're spread across many pages, and it's easy to mix up which page says what.</p> <p>So this account is where I'll write up what I learn: short posts on one question at a time, with links to the docs behind each point so you can check them yourself. Corrections and "that's not how it works in practice" comments are very welcome.</p> <p>If you work on mobile games, I'd love to hear what part of building or shipping confused you most when you started.</p> introduction gamedev beginners