421 karma · joined November 24, 2011
[ my public key: https://keybase.io/rraval; my proof: https://keybase.io/rraval/sigs/Ax1_hUoT2TVxiPextem1Y8Vwi61TqJ2pIbE4E19eXqE ]
if (count > 100) {
$el.removeClass('low-value');
$el.addClass('high-value');
} else if (count < 50) {
$el.removeClass('high-value');
$el.addClass('low-value');
} else {
$el.removeClass('high-value');
$el.removeClass('low-value');
}
Compare to how this would normally be written: $el.toggleClass('high-value', count > 100);
$el.toggleClass('low-value', count < 50);But have you ever had Caps Lock on by accident in normal mode? Most confusing 3 seconds of my life.
So it's not just about displaying what mode the system is in but also making sure that the user is always aware of the mode. It's this mismatch that make modal interfaces bad.
Edit: Parent has since deleted their comment. It used to say something along the lines of:
> So if I make vim always display the mode its in, does that make it modeless?
> In Raskin's sense and according to his definition, an interface is not modal as long as the user is fully aware of its current state.
Given this definition, eliminating modes is as simple as making sure that the user is aware of what mode they are in at all times. This makes your assertion problematic:
> To think that you can simplify your model of computers to the point that you can eliminate modes is to simplify your model to the point that it is useless for a great many things.
I don't think you would argue against the notion that users should be made aware of what mode they are in. A pretty common example comes from the CSS `cursor` property:
- If its `default`, clicking should have no effect
- If its `pointer`, clicking should have an effect
- If its `move`, clicking and dragging should have an effect
These cues are far from useless and help transition a modal interface into a modeless one.
Intrigued by your claim, I turned to Google to find more. The only credible link was an article by the Huffington Post [1], and the claim had been redacted.
[1] http://www.huffingtonpost.com/irene-monroe/the-gandhi-none-o...
[1] http://tctechcrunch2011.files.wordpress.com/2013/03/screen-s...
One of the things I built that term was a tool to visualize user retention, implementing triangle heatmaps, which I believe were invented in-house by Danny Ferante.
The idea here is to exploit the very quick visual pattern matching we're able to do as humans, and turn that into actionable cohort analysis. From the screenshot in the article (http://i.imgur.com/qBbkZv8.png), I think we can agree that it would become unwieldy with a large number of datapoints.
Compare this to http://imgur.com/sOQ4vrm, a screenshot of the triangle heatmap generated for tcreech's Cover Photo Finder Facebook App. The x-axis represents the cohort (the set of users that installed the app on the same day) broken down by day instead of by week like the article (hence patterns are more granular). The y-axis represents number of days after installation. Each datapoint is then coloured to represent the percentage of users that return to the app on (installation date + number of days).
A number of patterns are captured quite easily:
- A vertical pattern is local to a specific cohort. A new promotion or redesigned sign up page often results in this.
- A horizontal pattern is local to a specific vintage. If your app has a trial period that expires after 7 days, then you'll see your retention plummet across all cohorts horizontally at y=7.
- A diagonal pattern is local to a specific date. If your app is down on January 2nd, then there will be a diagonal blue line (0%) across all cohorts.
I wrote up a work term report for the University of Waterloo detailing triangle heatmaps: http://zeroindexed.com/triangle.pdf
Video released by Facebook explaining triangle heatmaps: https://www.facebook.com/video/video.php?v=3707283286197