… web developer, writer, and consultant based in Hveragerði, Iceland.

I write about web dev, interactive media, digital publishing, and product development.

I’m available for consulting and hire.

Explanatory windows

So, I decided to go through some of the apps I use every day (with Google Maps as a bonus) and see which of them use explanatory windows and for what purpose.

Turns out most of them do. Some for autocompletes. Some to bring up contextual tools. Some to bring up a purely explanatory window. It is, as I said in my earlier post, a generic tool for interactivity that I think should be standardised and implemented as a primitive by ereaders.

Again, excepting Google Maps, these are all apps I use on a daily basis. I didn’t even try to look for it in other apps.

Apologies to Pablo Defendini for using my exchange with him in the screenshot.

Twitterific uses explanatory windows for conversations

Byword uses them for a tools palette

OS X uses them for dictionary definitions

Coda uses them for autocompletes

Google Maps uses them for information on a location

Join my Newsletter

Do you ever wonder why a newly released open source project matters? Why it doesn't? How new or old standards or specifications affect your work? Why the web, tech, and publishing are the way they are?

This is an unapologetically political newsletter about tech, the web, and publishing—with context.

Because, to decide whether to use a piece of software, web standard, or open source project, you need to know why it‘s interesting, not just that it‘s interesting.

I won't send you spam. Unsubscribe at any time.