apps that don't set appropriate input defaults

if your app's input field is restricted—for instance—to numeric entry, and your app doesn't default the user to the numeric keyboard, i advise you to prepare for the most exquisite torments. when i am king, this is how it will be.

images in email signatures

will be verboten. on pain of pain, when i am king, that is how it will be.

toasted sandwiches

will only be served on wire racks or plates warmed to above the temperature of the sandwich, so that the soggy sandwich will be a thing of the past. when i am king, this is how it will be.

reams of paper

will be placed entire in the printer instead of opened and left on the table—short a few sheets—to warp subtly due to ambient humidity and later jam the printer in a particularly unfixable way at the worst possible time. on pain of pain, when i am king, etc.

webpage element sizes

should be declared instead of left implicit, so that user control elements such as buttons don't move about maddeningly as objects load gradually from a slow server, causing one to click where one does not mean, in fact, to click. on pain of pain, when i am king, this is how it shall be.

non-drip lips

will be a mandatory feature on pitchers, beakers, bottles, jars, and all such vessels. when i am king, this is how it shall be.

content websites

will prioritize loading content over loading ads, so that customers are not left fuming at an empty page just because the ad network CDN has decided to have a little snooze. when i am king, etc.

user interfaces

will use helper text and contextual instructions to be be clear and explicit enough that the user will not find it necessary to use even a single separate set of instructions for completing a workflow—much less eight. my sympathies to the engineering team on exchange server, but my sympathies will not prevent them from being first against the wall when i am king.

passwords for services storing inconsequential information

will not force contortions for extra "security" where it is only questionably necessary. why have at minimum one letter, one number, and one non-letter, non-number character in a password for a service storing my cereal preference? also, let's be clear: 1) no one endorses repeating passwords across services, 2) services storing important data should have strong security (a single password, no matter how complicated, seems inadequate. give me multifactor). a sense of appropriateness and occasion is indispensable in diplomats and products both. when i am king, etc. 

an error message

should declare a) its source, b) its unique identifier and the system in which that identifier is unique, c) a human-readable description of the error, that we may never again gnash our teeth and resist in a kingly fashion the urge to throw the monitor out of the window. when i am king, etc.

journals requiring idiosyncratic formatting and citation styles

will publish a typesetting and bibliographic style file, so that we will not spend many hours fiddling with existing style files to do the work that the journals should have done to start with. when i am king, etc.

favicons

will be informative and intentional so that never again are we confronted with rows of browser tabs, half of which have the little globe symbol denoting a website that forgot (or didn't care to) design itself a favicon. on pain of pain, when i am king, etc.

focus on forms

will automatically be set, on load, to the first field that has to be filled. this includes the url field for new empty windows in browsers. designers, hear and obey on pain of pain. when i am king, etc.

grout and small tiles

will never be used in areas with constant water exposure, viz. backsplashes, bathrooms, sinks, counters of all varieties. and while we're on this topic, why do so many kitchens insist on stainless steel surfaces? that stuff watermarks at the drop of a hat. when i am king, etc.

multi-part stories

every instalment of a multi-part story should link to every other instalment of the same story. webmasters too lazy to update early instalments, you know what you have coming. when i am king, etc.

proprietary connectors

for generic things such as audio input and output will be prohibited, so that never again will we be stranded in an airport without the ability to listen to our livescribe pulse pen recordings because we assumed incorrectly that a regular pair of earbuds would work just fine. when i am king, etc. 

alarm clocks

especially those with alarms insistent, irritating, persistent, and set for 9.45am, will be shut off before their owners leave to parts unknown for many weeks. when i am king, etc.

bookmarklets on iphone/ipad safari

will not require 9-step installation workarounds that end in gentle seething. when i am king, this is how it will be.

hot water for tea

should never be served in a container that has been used for coffee or any other hot drink. the most carefully grown teas in the world are no match for the ghost of stale coffee grounds. expensive restaurants and their catering staff should know better. on pain of pain, etc.

slides

should be replicated for sequencing, so that presenters need not page backwards and forth through an enormous deck, muttering "i know the slide is in here somewhere...ah! here it is...no, i guess that's not it. well, i'll just talk through it," all the livelong day.