I had an appointment at the hospital today, and was thinking about the rates at the hospital car park. The parking area at big NHS hospital in my town has the highest parking rates around. They are probably more than double the rate at any other paid parking zone in the town.
At a first look, they seem extortionist. At most places, high parking rates are a nudge for users to either take an alternate means of transport, or to curtail their visits. At a hospital, however, few people visit by choice. Also, the visitors are more likely to use a car – comfort for the ill and all that. By charging these, probably ill, visitors these extraordinarily high rates, the hospital/NHS/council are just heartlessly milking the already suffering.
On a second thought, however, there is a valid reason behind these high rates – consumption tax. They are not just parking rates, they are an indirect tax on the heaviest NHS users.
Since its founding, Twitter has made a religion of listening to users. After all, they came up with some of the company’s best ideas — including the hashtag, reply and retweet. After the flow of good ideas from users stopped, Twitter was hard-pressed to come up with its own.
The usual Premier league table gives a good idea of the ranking, but the gaps between teams aren’t immediately obvious1. I love how this visualisation shows both the rankings and the gaps with one simple line.
There are no visible cues hinting at ability to navigate from one expanded post to the next (or previous).
Navigating back to the post list (using back button), and then to next post makes it slow, and click heavy.
Keyboard shortcuts work, but there are again no visible cues indicating even their presence.
No visible hints that any keyboard shortcuts exist
Keyboard shortcut discoverability is solely by trial and error, or ‘Google’
Traditionally, pressing ‘?’ (in, say, GMail or Pocket) brings up relevant shortcuts modal. Doesn’t work in reader.
One suggested hint could be to place a keyboard icon next to the help (?) icon, at the bottom, in the left navigation bar.
j/k navigate to next/previous post as expected. However, the more ‘lay’ user-friendly left-arrow/right-arrow versions don’t.
esc key works the same as browser’s back button – navigating back through history stack (i.e. going back to last viewed post).
A better (expected) implementation would be to jump out of expanded-post view to the posts list view, ideally scrolled to the last viewed post.
Like keyboard shortcut, l, works as expected. Adding f as an additional activator would be useful – a lot of platforms use favourite as an alternative to like, and some users may be more behaviourally trained to press f instead of l