What are these apps that have 50+ MB in code built with? Or what counts as code in that regard?
Snapchat for example is 95MB, 77MB code, and on my phone (Android, so not directly linked, but probably similar) the most unresponsive, crashy and painful-to-use app right along with Skype.
I was amazed to find a C++ "Hello, World" program was several megabytes. It turned out that it was due to statically linking in all of Unicode support. In the particular build environment it was invisible to the programmer; i.e., you wouldn't even realize it unless you went looking for it.
I'm wondering if the same kinds of things happen with Facebook, Skype, etc. It's not the actual Facebook or Skype code that's so huge, but that they've been around for so long and so many people worked on them that they have a very complex build procedure and they're linking in all kinds of unnecessary junk, but no one has the responsibility or desire to go prune it.
It's a pretty cool break down you do, but you should consider not including hearthstone in your demo, as most of its image, video and audio assets are placed in the "other" category. So it is a bad example of how your service can help me understand my app, since your demo doesn't help me understand this game.
When I got my first smartphone, the guy in the shop installed Whatsapp for me without really asking. It was around 80mb, and chewed through a fair chunk of my data allowance on the first day. Made me paranoid to use the data connection for the first few weeks.
Maybe someone can clear this up for me.
I'm struggling to understand why it is that size. I'm not going to be silly and say it would it be a simple app because I don't know enough about mobile to make that assumption.
However, I see plenty of other apps that appear to have way more complexity than the Facebook app. They are all significantly smaller. I don't understand what's happening there that requires that much bloat. The UI appears fairly minimal. From an outside perspective (probably an ignorant one), it just appears to be making API calls and throwing out the data.
Genuine question. Where is this bloat coming from? Is it just a pile of thrown on band-aid fixes and kitchen sinks, or is there something that I'm missing. Even third party applications do the same job, yet treat my battery and storage with respect. They seem to be fully capable of the same things that the official app is capable of.
Part of me wants to assume it's the whole, "move fast and break things" approach.
User has device at 95% capacity. User tries to download app. If the app is under lets say 40mb, it installs. If app is over 40mb, user gets "please make room for app" alert. User loses interest, app is not installed. I know I have done this before, has anyone else?
@CharlesW we mostly focused on the facts and running as controlled of an experiment as possible without bias or drawing conclusion on exactly why heavier apps get downloaded less. Though my personal guess from working years in the mobile app space is that users are surprisingly conscious of data & disk usage. Not everyone has unlimited data or 128GB storage iPhones.
Oh my gosh - this so, SO much. I think there's a lot of 'designers' thinking they're 'developers', I've seen that first hand and that's how you get rubbish like Drupal.
MildlySerious|9 years ago
Snapchat for example is 95MB, 77MB code, and on my phone (Android, so not directly linked, but probably similar) the most unresponsive, crashy and painful-to-use app right along with Skype.
cantrevealname|9 years ago
I'm wondering if the same kinds of things happen with Facebook, Skype, etc. It's not the actual Facebook or Skype code that's so huge, but that they've been around for so long and so many people worked on them that they have a very complex build procedure and they're linking in all kinds of unnecessary junk, but no one has the responsibility or desire to go prune it.
wodenokoto|9 years ago
collyw|9 years ago
bitmapbrother|9 years ago
BoredDev|9 years ago
However, I see plenty of other apps that appear to have way more complexity than the Facebook app. They are all significantly smaller. I don't understand what's happening there that requires that much bloat. The UI appears fairly minimal. From an outside perspective (probably an ignorant one), it just appears to be making API calls and throwing out the data.
Genuine question. Where is this bloat coming from? Is it just a pile of thrown on band-aid fixes and kitchen sinks, or is there something that I'm missing. Even third party applications do the same job, yet treat my battery and storage with respect. They seem to be fully capable of the same things that the official app is capable of.
Part of me wants to assume it's the whole, "move fast and break things" approach.
aq3cn|9 years ago
http://www.ghacks.net/2016/10/04/facebook-messenger-lite-wha...
SilasX|9 years ago
What gives?
CharlesW|9 years ago
So, let's assume Segment is right and there's a causal relationship between app size and downloads. What am I missing?
scsilver|9 years ago
tonyx|9 years ago
quadrature|9 years ago
sotojuan|9 years ago
f2prateek|9 years ago
https://www.quora.com/How-do-page-load-times-affect-e-commer...
laurentdc|9 years ago
mrmondo|9 years ago
jlarocco|9 years ago
According to Wikipedia, segment.com's sole purpose is to aggregate data for marketing and advertising. Not a company I want to give page views to.
DigitalCannon|9 years ago
zanecodes|9 years ago
orng|9 years ago