4 ms·
"why it's bad," followed by great reasons FOR it.
by mvkel 14y ago
"why it's bad," followed by great reasons FOR it.
- Fizzer 14y agoMost of the reasons they presented for it were reasons that benefited the developer, not the user. I assume the headline is referring to why it's bad for the user.
- dirkdk 14y agoyep, that's the issue. with all technology you have to balance the pros and cons for the user and developer. Path took 100 % the user as focus point, Facebook a bit more the developer
- gurkendoktor 14y agoiOS developers are certainly expensive. But if you have to balance 500 million users and a single development team, I don't think anything less than 100% on the user makes sense.
- msgilligan 14y agoThe reasons for it are valid and it is possible to get that benefit to the developer with a better user experience -- See the comment (above) about the LinkedIn app for an example of an app that makes both users and developers happy.
- msrpotus 14y agoThey don't talk about it in the article but the app is also just generally buggy.
- pjmlp 14y agoThat is why the future belongs to native applications, the consumers are finally realized how this web everywhere sucks and is only able to deliver half-baked experiences.