Throughout my software development career, especially over the last 20 years, I've constantly sought a balance between system and software aspects. One of these balancing points is the issue of application size. On one side, I have an engineering instinct that says, "Every kilobyte matters, every excess is a cost," while on the other, a pragmatic perspective that argues, "Delivering value-adding functionality to the user as quickly as possible is essential." Navigating between these two extremes has been a significant part of my career.
So, should we really fight for every kilobyte? Or should we prioritize functionality? This is a gray area that varies depending on the project's context, target audience, and even deployment model. In my experience, there's no clear-cut answer to this question, but the best results can be achieved by asking the right questions and making conscious trade-offs. In this post, I'll share my thoughts and observations from different fields on this topic.
The Harsh Realities of Size in the Mobile World
The importance of size in mobile applications is undeniable. Especially in markets like Turkey, where mobile internet is widespread but not always fast or unlimited, app size directly affects download rates, user experience, and even how long an app stays on a device. Years ago, while developing my own Android spam application, I experienced this reality repeatedly. The smaller I made the app, the higher the download and installation rates became.
