The connection kept resetting for me, so here is the Google Cache link: http://webcache.googleusercontent.com/search?q=cache:f-pnPOuBD-wJ:https://jakearchibald

The connection kept resetting for me, so here is the Google Cache link: http://webcache.googleusercontent.com/search?q=cache:f-pnPOuBD-wJ:https://jakearchibald.com/2015/if-we-stand-still-we-go-backwards/+&cd=1&hl=en&ct=clnk&gl=us http://webcache.googleusercontent.com/search?q=cache:f-pnPOu... --- I don't web develop often. As a user, mobile web is usually more usable than a native app - not in terms of whether or not it works, but in terms of usability, flow of actions, and predictability. Cut, copy, and paste work in the browser but rarely in native apps. Other little things too, items too little for a project architect to notice or a punch list to pick up. The other half of what killed Blackberry was Microsoft Activesync. Blackberry's email service required you have set up their Blackberry Enterprise Server (or their lower-performing cloud-hosted Blackberry Internet Service) and connected this to your email account. BES had an "agent": a service that would log into your email account every 30 seconds, check for new email, and then forward this to your Blackberry over the Blackberry network (which is why you had to pay the $10 "Blackberry Fee"). Activesync (I think) used Exchange mail rules to do the same thing, and the iPhone mail client could use Activesync. It was that "one-two punch" that took out Blackberry: * iPhones were cool. Androids were cheap. * Activesync comes with Exchange, no other server setup necessary. * Works with normal carrier service; no $10 Blackberry fee.