Developing Upwards

The Chrome Development team is talking about how much faster Chrome is at loading your tabs when you restore from a previous session. This is a totally welcome improvement, especially compared to Firefox's long superior handling of session restore by on-demand loading tabs only when you switch to them. Chrome, by contrast, has already penalized you for every extra tab you had to restore by loading them all at once and immediately. But, something is missing from these announcements about improving the speed. On the forthy-fifth  release of the Chrome browser, I would have expected and been happier with finally improving the plain experience of restoring a previous session in the first place. Chrome doesn't even prompt  you to restore your tabs or even tell you there is a session that could be restored, if you don't explicitly go looking for it. Hidden behind the main menu button that many users don't even recognize and know is a menu , and then within the "Hi...

If you download Firefox on a linux machine today what you get from their servers is a pretty unfriendly tarball. What are you supposed to do with this? Maybe you know how to extract a tarball. Maybe you even know what of the many files inside it you're actually supposed to run and  how to run it? Maybe. But does everyone else? Do non-developer users have any clue what they're doing with this thing? They experience is awful. I want to see that change and followed a ticket that tracks just that. What do you think?

Why is it when I see an application in the Chome Web Store I see a little notice about what permissions the app will have, and I'll see a similar list of permissions before installing an Android application? Why is it that I don't see something more like this?

Yes, this is a screenshot of a screenshot. Stick with me, but I really do has a point to this! I have to admit, publicly, that I clicked the button. The one in the screenshot. The one that isn't a button, just a PNG image. I should be glad it wasn't a pop-up! I realized my mistake at the moment I was clicking on it, but it happened to fast to stop. I had to sit and think for a moment. Why did I do that? It drove me to write this pretty immediately and do a couple mock ups for solutions. I never want to let my users loose information or control over it. That is, we don't want them to OK a message away and neglect to actually read it and we don't want them to click "send" before they're really, really ready to confess their never ending love to Glenn Beck. Those are two distinct safety nets. Information the user missing for being click-happy and actual actions within the application they might have wanted to avoid. Any reversible actions, like closing a dial...