[JeremyNT]

Although I think you're exactly right, the irony is that they'll never actually be able to determine why somebody doesn't install an app due to this kind of junk. It's not like they can a/b test "bloated app" versus "good app" installation metrics, and they have no way to know why people are not installing something.

The trend towards huge installations is one of the many reasons I install as few apps as possible, especially in this class of "should have a fully functional web version" type social media things.

The damage is also cumulative: I have a perception that "apps" in general are likely to be huge piles of junk, so I'm reluctant to install any of them, regardless of their own merits. Even if LinkedIn were to spend the time improving their app it would suffer from the overall reputational damage to the entire ecosystem, and I still wouldn't even think to install it.

[eddd-ddde]

When I was in an internship, I needed a new library for some feature in one of the sites. The _first_ thing their PM objected on was bundle size. Only after confirming that adding my feature would bundle size remain sensible could I continue.

They are very sensitive over this kind of bloat over there, and it is definitely a key metric. You will even get a warning in your email if one of your builds increases bundle size too much!