Designing better user interfaces
slideshare.net
slideshare.net
EDIT: Not the mention the excellent kerning: http://i.imgur.com/1yEya.png
I re-saved some of the slides to display a static JPG, the parsing of the PDF seems to cause some problems. I just tested it and could go through the 120 slides without problems now.
It's a bit of a pain, yeah.
Which leads me to this: Who actually loves slideshows in real life? So why would we like slideshows on the web? It's the same exact problem, the same annoyances. A linear, one by one, hard to scan through, 1 sentence per slide, time consuming, experience.
I'd take a blog with 120 consequent images over a 120 slide slideshow any day. I'm so sorry for my bitching but we need to do something about slides on the web. Can we kill them? We're killing flash and look how much nicer the place is. The web without linear slideshows will be like a park without dog shit.
I'm thinking of doing my next one like this, it makes more sense from a UI perspective.
> Customishard,andtomecustomisreallysayingthatyouhavemoretimetothinkaboutthebehaviorofaselectboxthanApple’sinteractiondesignteam.Andthatyouhavethedevpowertofixit. Oneveryplatformoutthere.Sosometimesyoujusthavetobepragmaticifyou’rebuildingaproduct
PS: slideshare sucks at exactly this kind of UI.
"Custom is hard, and to me custom is really saying that you have more time to think about the behavior of a select box than Apple’s interaction design team.
And that you have the dev power to fix it. On every platform out there. So sometimes you just have to be pragmatic if you’re building a product."
> SlideShare sucks at exactly this kind of UI
You can't copy and paste its text!
> If you do nothing, the end result is better.
"Designing better user interfaces sets out to teach interface design by talking through concrete examples: what works, what doesn’t work. A good interface consists of a thousand details done right. This presentation is all about those details."
I feel like G+ has one of the worst implementations of a photo gallery anywhere as a result of this.
Here is another goodie but specific to mobile UI design:
http://www.slideshare.net/mringlein/designing-for-mobile-678...
(I assume "clever progressive loading" refers to prefetching.)
You do not need to do this. On the embedded Google Map you can just click the Google logo in the bottom left corner and be taken directly to a new maps.google page with the viewpoint centered exactly where the embedded map was. I even verified that it works on the map he was using.
TL;DR: Click the Google logo on an embedded map to view larger.
"The map above is just an image that links to google maps"
I believe that violates Google's TOS.
It's all in the details :)
http://csswizardry.com/2011/12/measuring-and-sizing-uis-2011...
Why is zooming the whole document the preferred method? It feels sub-optimal to me, but maybe I'm missing something.
Although using px makes for an easier example, you don't have to mention the scale in which you are sizing your ems. The example was about the spacing, not about the unit used to determine the distance between heading and paragraph.