4 ms·
I agree as a developer, but I think the economics favour having many incompatible UI libraries: A. It’s expensive to standardise and agree on what the UI primi
by justsomeuser 6y ago
I agree as a developer, but I think the economics favour having many incompatible UI libraries:
A. It’s expensive to standardise and agree on what the UI primitives would be, and a standard would force the lowest common denominator of features. If you want a new whizz bang button now you have to create an RFC and cajole agreement.
B. It’s profitable to own the platform, which includes the UI, because then you can charge 30% taxes. If Apple spent money making a portable library they would be attacking their own income source.
- ziml77 6y agoThere's actually an advantage for users. Because you have to enter a new mindset for each platform (or have different devs for each) it pushes you to think about designing the UI to fit the platform. It's nice when the UI and UX feel like they belong with everything else on the system.
- api 6y agoHaving everything written with Electron is an advantage to users? Because that's the result.
- api 6y agoIf (B) is the reason, the platforms are eventually killing the golden goose by pushing the entire dev ecosystem onto the web stack for building UIs. Electron will rule.