Mats Lindh

(Haha! Thanks to the wonderful internet, I’m on vacation .. and still posting things in my blog .. that I wrote BEFORE we left! How’s that for TIME TRAVEL???)

We should really stop using the resolution information in our statistics scripts for anything. It’s nothing other than curiousity, and it should never be used for making any decisions regarding how a page should be structured. Most people probably stopped reading halfway through and thought that I’m going completely nutters. What do you mean? But .. how can we know how many pixels we can use for our design?

You’re out of luck! Hopefully I’m not singing Lady Madonna and strolling around somewhere in Europe wearing a pink tubetop just yet, and I still have my sanity. Instead of basing our decisions on resolution, we should start paying more attention to actual browser window size. This is interesting from a usability perspective, as it considers the size that we actually can use without demanding that our users start resizing their active browsing window. The desktops I use actively are usually running in 1920×1200, but my browser window is considerably smaller. If a page suddenly would require me to use 1920×1200, I’d be annoyed (and yes, that includes those of you who still think your content is SOOOOO important you should open up windows in fullscreen mode, and still only use 50% of it for content..), even though I actually have a resolution that supports that kind of content.

Since this means that we’d see a lot more sizes than the regular 1024×768, 1280×1024, etc, we’d simply create intervals of “acceptable sizes” instead. We’d have (640-800), (801-980), (981-1099) instead, and we’d be able to give an estimate of how much content we could actually show a certain percentage of our users within their first view of our information. Even though people have 1024×768 as their resolution, we have no idea about how much content they actually see. I have no idea if that means that the majority of people see 500 pixels of content, 300 pixels of content, etc (and that would of course also change based on font size, but .. stay on track with me here), which is actually the useful information to base your decisions on.

So, anyone with me? How about support for this metric in Google Analytics? Anyone know of any existing statistics project that has added support for the actual viewport instead of the screen resolution?

I’ve now spent a fair amount of time with Wordpress since I ported my blog over to it from Serendipity. My first experiences were collected in my post titled Wordpress Usability Issues, and I’ll further extend on this here.

• I’ve gotten used to having the “Save”-button on the right side, but this comes from having to learn the location by hand. I still move to the bottom of the page from time to time, but I’m not lost like I were earlier.
• The location of the “Save”-button has however trigged another problem: since I now move my focus to the right of the page when I’m done writing my post, 9 of 10 times I fail to give my posts any tags or assign any categories to it. This is done beneath the text of the post, but since I no longer move vertically to progress from the post field (my eyes now move horizontally to the save/publish button instead), I never think about adding those. Guess I’ll have to learn that too, instead of following the flow of the application.
• “Preview this Post” does not save the post before showing the preview. That means I’ll have to press Save, then “Preview this Post”, even though “Preview this post” is placed all by itself and seem to function independent of the other buttons.
• Not a usability-issue, but probably a simple bug: some times my posts does not allow for comments, and I’ll have to enable them manually by going to the details of the post. I’m pretty sure that I’m not turning them off by accident, as the option is buried even further down from the tags and categories that I’m already having trouble finding without thinking explicitly about it.

Just got pasted a link about this very neat way to navigate through videos and their playback, Video Browsing By Direct Manipulation. Haven’t read the paper yet (it’s linked on the same page) but it seems that they’re recognizing objects through several frames, and then allow a user to navigate through the video by following those movements. The video says it all.