It’s impossible to imagine a world now in which developers proudly browser-sniff to check that the customer is using the “right” browser on the “right” operating system, while they race to code applications that revolve around non-standard “extensions” thereby locking themselves and their users to one browser because it temporarily has the shiniest proprietary extras. That’s absolutely unthinkable as we approach 2011.¹

A relatively old post (over a year), but I found it the other day. A great way of looking at the browser arms race of today.

Whenever a blogger cries a cash register rings.

The brilliant Horace Dediu on #25 of the Critical Path.

Dialogs can be done well in many cases, avoiding the barrage. They’re only shown when the app requests access to the protected resources, and only the first time. Conscientious developers can usually avoid showing multiple dialogs in a row by only showing them when the data is needed — for instance, I don’t ask for location access unless (and until) a customer selects the automatic-dark-mode setting.¹

Marco Arment writes about the permission dialogs in iOS and Android and muses about what’s a good way to solve the various problems that too many dialogs can result in.