Thursday, July 22 2010

No, not really.

What a thoroughly boring discussion that has distracted the entire tech industry. So many incredible innovations happening, yet everyone's talking this minor bit of errata. Move on!

It is further evidence that smartphones dominate the technology discussion now, with desktop technology fading into the noise. Intel is quickly preparing their very competent assault on the field with the Moorestown processor. It promises some exciting times ahead.

Backtracking on 802.11n with the N1

On the topics of product issues, in a prior entry I noted that I had been enjoying the fruits of 802.11n with the Froyo update on the Nexus One. Shortly after that entry, another update was pushed, FRF91, and my connectivity has become almost unusable unless I disable 802.11n on my wireless router (which was actually the case when I first got the phone, but FRF85 had provided salvation). So now I run two WAPs, with one to serve the 802.11n devices so I needn't cripple it for the N1, and a 802.11g one just to service the smartphone.

On High Density Smartphone Screens

With all of the talk about very high pixel density phones, and the downside of larger-screen phones, the focus of most discussions seems to be purely on the visual clarity of the screen. The actual usability of the on-screen content seems to be ignored.

On the Nexus One I'm dealing with a 252dpi (there is some fakery with the pentile pixel arrangement, but ignoring that), 3.7" screen. A site like the New York Times looks fantastic in landscape mode, with a fully readable presentation of the entire real-web contents. Yet the downside of that high-density, small screen becomes evident when I actually want to interact with the content on the screen. Something as simple as clicking on the category links down the left hand side is an exercise of extreme precision: Each link is approximately the size of a single fingerprint ridge, and they're so densely packed that a mm this way or that way yields the annoyance of a wrongly followed link. Zooming and unzooming just to interact with the screen isn't very enjoyable, and it erases many of the advantages of the pixel density.

Screensize is important, and smaller isn't better when you're talking about a device that doubles as a mini-web appliance. There is a balance to be achieved or the experience is compromised.

   

Reader Comments

> Screensize is important, and smaller isn't better
> when you're talking about a device that doubles
> as a mini-web appliance.

The other problem is that you're pushing more pixels in that small space. So it requires more CPU power, more GPU power, more battery power. There's a balance to be struck there that goes deeper than just the size of the resulting content. (And yeah, those small links can be annoying).

You should bug your N1 wi-fi problem with google, I don't see any mention of it on the android issues list on google code.
Trimbo @ 7/22/2010 9:06:55 AM
The best way to deal with tiny links on the N1 is the trackball. I don't know how people get by with phones that don't have one, for just this reason.
Noah Yetter @ 7/24/2010 2:58:22 PM
Just because you have the higher pixel density, doesn't mean that text should shrink with it. I'd argue that's more of an issue with the default zoom/layout performed by the browser than a hardware limitation.
Lee @ 7/29/2010 3:40:02 PM
Hey there Lee.

Your point is very valid, though one of the primary uses of the greater pixel densities on these small devices has been effectively fitting more content into the screen, providing the so-called "full web experience" without annoying constant scrolling and zooming. On the NY Times I really appreciate that in landscape mode the entire site as designed for a desktop is visible, it just presents a bit of an issue on the usability front.

If they doubled the density again, though, I wouldn't expect they would make the presentation only fill half the screen: The goal was to get a full widget displayed, and greater than that just adds definition.
Dennis Forbes @ 8/7/2010 7:54:06 AM

Add Comment

Name *:

Email Address:

(your email address is not displayed)
Website:

Comment *:



About the Author
Dennis Forbes Dennis Forbes is a Toronto-based software architect. While focused primarily on the .NET and SQL Server worlds, Dennis frequently ventures outside of this comfort zone into game development and image processing. He has been published in several industry magazines, has been quoted in the Wall Street Journal and has been interviewed by NPR.

He is a vice president and lead software architect at an innovative New York City hedge fund back-office services firm.

Dennis has been working on solutions for the financial, telecommunications, and power generation markets for over 15 years.





 

Dennis Forbes