That being said, the oddest-to-me thing in this article is a bank call center not being open 24/7.
That being said, the oddest-to-me thing in this article is a bank call center not being open 24/7.
</dated rant> (edit: my information is old, and perhaps hopefully outdated)
Oh oh!! Let me guess!! I don't do mobile but have looked into it. And the guy behind me is doing an app too. Everyone wants to minimize development effort so they pick a framework that will spit out both iOS and Android apps. It's the framework that ends up bloating everything. Maybe? That doesn't explain "why", it just pushes it off the app developer onto someone else.
There are two conflicting problems here that are the two heads of the same coin:
>"Why is this app so big, don't the devs respect my storage?"
vs:
>"Why is this app so slow, don't the devs respect people with poor connections?"
App size doesn't matter much in the actual use of the app, especially if you're using it often.
Start by removing all the pictures, videos, and similar. Then take out the analytics crap. Then, if your app is still big, figure out what's wrong with your code.
I'd venture a guess that there's a fat dependency chain based on the need to avoid reinventing the wheel all the while not paying for software dependencies.
NPM import npm2 npm2 install obscuredependency
And npm2 doing full dependency duplication to avoid version conflicts, leaving like 2 or 3 versions of each base library, that kind of stuff
That chain of dependencies does fall in line with the message (regardless of how widely it applies) of "modern developers don't care about efficiency".
The same reason it takes longer to write a shorter letter. Nothing is free, removing things costs time.