21–30 of 205 posts
Galaxy brain business model: shame the app developers and offer a tool to help them fix their mistakes.
TIL there is a Linkedin app. For me the question is why anyone would even consider installing it. The other is easy: It's Microsoft,
It’s required for messaging on a mobile phone. And probably other user hostile patterns.
Earlier quoted context omitted.
If I only ever use a single locale on my phone, why isn't there a way to avoid needing to download all of the extra info that my phone will never use?
In Ubers case, the app works well when you travel. Not sure why LinkedIn would need that, if that is your question.
Yes, you pay a bit for the sandboxing, GC, rendering, built in accessibility. But that’s a rounding error when businesses, especially large ones, go on a PM-centric feature frenzy. You get out exactly what you put in. Performance, security, user experience..
Whether it’s frontend, backend, embedded, whatever, the engineers are alright. Generally. It’s when you stop listening to them, or punish the grumpy ones in favor of the people-pleasers, that this crap happens. That’s worrying, because it’s become so prevalent.
Why does the web page presenting this complaint take 140 requests to serve and transfer 10Mb? Same reasons - bloat over time, developers with powerful machines and network connections who don't notice the impact, users with huge devices that don't care about 500M space for an app and management and corporate culture that don't care much about optimisation.
TL;DR: There're few global incentives for a LinkedIn app developer to make an overall good app, as opposed to making their PM happy. In detail: This is how death by a thousand papercuts looks like. I've had the (dubious) pleasure of observing a roughly similar BigTech app project. There are likely 100s-1000s of app developers involved in the LinkedIn app, and they are likely under immense pressure to Just Ship Alread…
I don't understand why you'd need 1000 or even 100 developers to produce such app. It's a CRUD frontend for a backend that already exists. What am I missing? Are you counting the developers of all the third party libs they integrate?