(this is page 34 of 121)





Latest

Tablets and interface fatigue

While I, along with the rest of the world, am as excited as a teenage girl at a Hannah Montana concert for the famous Apple tablet to get to market, in trying to puzzle out how the interface for a new class of device might work, I've gotten a little worried about something that we may be about to face during this Precambrian explosion of "post PC" devices: interface fatigue.

Though we're just now coming to grips with the new fat finger, small screen (sounds like a Cake song no?) way of touching our way through smartphones, I wonder how many other classes of devices people will be willing to put up with learning. And especially a class of device that is functionally equivalent to what either a laptop or a smartphone can already do.

The worst of it may actually be that just as Apple readies its tablet, a number of other competitors are doing so as well— each with its own special value-add on the interface metaphor, most based on Android's incomplete user experience guidelines.

Think of it another way: you learn your new car's crappy electronic interface (especially bad it seems with in-car GPS systems) because there is no other way to accomplish the same task. Ditto for a few other appliances that are increasingly presenting richer and more complex interfaces. Each of these devices takes up a limited area of "interface RAM" in your head, and while smart companies may try to copy market leaders (like the iPhone), copyright law and the challenges of execution may hinder this attempt to get some interface leverage. In this world won't we quickly get to the point where we'll turn down the next shiny device, just so as not to have to learn another interface?

(Which may be why an Apple tablet running standard Mac OS may be just what the doctor ordered...)

Comments Permalink

Two cool bits of Javascript

In the, "I didn't know they could do that department:"

1. Wolfenstein 3D done with a pretty decent framerate inside of a browser without new-fangled HTML5 stuff. Having recently bought a native port of this game for my iPhone, I can say that a finished version of this JS one would rival it in every way.

2 Skulpt, the beginnings of a Python implementation in Javascript. It doesn't import and seems to just support the basic built-ins, but you get the idea.

What amazing things people are doing with Javascript these days! At Google IO this year, someone from the GWT community declared that it had become the new assembly language— the machine instruction set of the browser— and that we should now get ready to see all of the high level languages and frameworks that will be able to compile down into it. Though at the time I thought it was an interesting justification for the weird mongrel that GWT seems to be, seeing demos like these makes me wonder whether there isn't a kernel of truth to it.

One thing is for sure: Javascript and JS VMs are going to be really important over the next 5 years. More than Win 32, Cocoa, Flash, Flex, Silverlight, and all of the other junk that just clogs up the application development circulatory system of the Internet.

Comments Permalink

Fresh upon arriving in Spain this week, someone stole my iPhone (after a long flight and in the blink of an eye) which has left me to explore the vastly more fascinating world of European carriers, unlocked phones, and prepaid SIMs. As with most travel to foreign lands, the net result has been a much better appreciation for differences in the culture of mobile computing here.

And if you're about to travel to Spain, Portugal, or some parts of Asia, read on for some good advice on how not to return with astronomical cellphone bills.

First off, I was lucky to be traveling with an old iPhone 2G, a.k.a. the "portable babysitter," which could function as a replacement phone. Thanks to the allure of Rolando 2, I had recently updated its firmware to 3.0 which initially left me feeling as though unlocking the phone was going to be impossible.

Enter redsn0w, the best and simplest iPhone unlock program I have ever used. I don't think that getting the phone jailbroken and baseband unlocked will ever be a single click experience, but after doing this with 3 other devices, I have to say the folks behind redsn0w deserve a lot of credit for returning the full power of our devices to us.

Unlocked iPhone in hand, I headed down to a shady looking mobile phone retailer called "The Phone House." Or perhaps it just looked shady to me because I am not used to seeing every carrier's wares and every phone ever made both new and used (probably including my swiped iPhone 3G) in a tiny retail storefront that looks like a cross between a 42nd St. camera store and a Sunglasses Hut.

At the store I was able to buy a prepaid SIM card for 20 Euros with 20 Euros worth of credit on it from a carrier called Yoigo. The way it works is like this: every day of day costs approximately 3 EUR for all the data you can use; however, after 100MB of data use, the bandwidth goes from almost acceptable to totally unacceptable (EDGE to something resembling a 12 kbps 1985 modem). Phone calls and SMSes have some nominal charge, and the whole system is constantly telling you how much of your alloted spend (which I doubled by adding another 20 EUR) you've consumed with these popup messages that I didn't even know the iPhone was capable of.

So how is this native mobile experience? It's reliable though a bit slow. However, I can't tell if this is just having to get used to the old iPhone with its pre-3G roots or if the Yoigo network is really just not up to it. The other drawback seems to be that some non HTTP services don't work at all, like secure SMTP and secure IMAP. Overall though, the fact that I can go to a strange country and get a provisioned phone card with minutes and data on it to last me just over a week with nothing more than a credit card and a passport should put the US carriers to shame.

[ Incidentally on the crappy AT&T meme, when I called them to report my phone stolen and ask that they port my number to the other (still AT&T) SIM in my old phone, I was told that that SIM had been "permanently deactivated" (because apparently no one at AT&T has heard of "UPDATE from sim_card SET active='YES' WHERE serial_no=") and that I'd have to have a new SIM shipped to two different places to reactivate my phone. Great job guys, maybe next time you could just send me a flock of carrier pigeons! ]

The final thing I'll say about the experience was how smooth it is to lose and replace a device for which most of the critical data lives on some cloud-based service. This is the default orientation for most email accounts, but the combination of Mobile Me and iTunes made it a piece of cake to restore every piece of data on the phone that I cared about. A few password changes on some servers and I'm not even worried that my newly iPhoned Spanish thief has got anything more than some photos and an iTunes library which will only take him to the point of first sync (and no, Find My Phone did nothing for me).

It's an interesting comparison to something like having a laptop stolen, and may indeed point to one of the greatest benefits of the cloud when it comes to mobile computing.

Comments Permalink

I have zero doubt that all of the rumors about Apple doing a tabletesque device are true and that it will be the company's answer to netbooks and the explosion of demand for general purpose computing devices in the sub $500 range (and no, the iPod Touch, great though it is, is not the answer here).

If I am wishing for one feature though, it is that the aforementioned device does not in fact run iPhone OS, but instead some form of their desktop OS X. Given the company's preference for closed-and-controlled environments, I find it unlikely, but here are two good reasons why:

1. Having a device that has a different display size and other hardware will muddle a relatively nice developer story on the iPhone (Symbian anyone?). You can already see this beginning to happen in the 3G/3GS split and that is for CPU reasons alone; for instance, we've got this application that we've been testing at work that runs 4x faster on the 3GS than on the 3G. This basically makes the difference between usable and complete garbage. And this is just the beginning of the pain that we'd face if we had to be checking for other hardware differences, or worse still, designing "scalable GUIs" that somehow always end up looking shitty.

2. A general purpose computing device depends on a lot of two-decades old infrastructure that a new OS like iPhone OS just doesn't have. Printing. An ecosystem of 3rd party applications. Other input peripherals. By leveraging desktop OS X, the tablet would get all of these out of the box.

Incidentally, even mighty Google seems to have realized this with Chrome OS— after a year of everyone trying to shoehorn Android into a general purpose form factor, they just came out and said "whoops!, we really just want a regular Linux distro in there after all."

One final note: several folks have argued that the desktop model for computing is broken and that consumers need something simple like the iPhone OS but I don't buy this at all. While the PC OSes may be challenged (especially on the Windows side) when it comes to usability and maintainability, they have been incredible platforms on which to build for two decades— as Zittrain would say, "truly generative," and to throw them out now seems both pedantic towards the users who we all supposedly serve and very short-sighted.

Comments Permalink

Bob Metcalfe, while reminiscing about his days at Xerox PARC, and the specific passions of each of the researchers there once told me: "When it comes to what you are interested in doing, just remember that every one gets stuck on to something... and when you do, you should hope that you get stuck on something like Ethernet and not something like X" where X was a relatively obscure PARC technology.

I can't help but think of his advice that day every time that I see people from Boston area startups trying to "Web 2.0"-ize the latest version of their Lotus Notes-esque vision. And now it would seem that even Google is catching this particular disease.

Let me back up; broadly speaking (code for: huge generalization about to come), the evolution of personal computing seems to be split in three major phases:

1. The productivity revolution: incited first by the PC and then by the mainstream adoption of the GUI, this was the era of the spreadsheet and the word processor. These were the halcyon years when people realized that computers could have a tremendous impact on workplace productivity.

2. The networked productivity evolution: starts with Lotus Notes (the PC embodiment of all that people who'd had access to networked workstations had learned) and ends with Google's contributions to dynamic browser applications. Most of the Internet's killer apps fall into this bucket, and if you squint just so, even search and e-commerce belong in this broad bucket.

3. The social twist: though most of today's social Internet apps had their roots in networked productivity, they've since evolved socializing as a purpose of their very own. People go to Facebook "to facebook" not because they are hoping to get a particular task done. Similarly, despite all the exhortations about how Twitter is "the next step" in search, the reality is that it is first and foremost an interesting milieu for social interaction.

Now, here is where Metcalfe's advice comes in: when folks that grew up in phase 1 tried to build web companies in the mid 90s, we got productivity apps in the browser that failed to recognize that it was the network that really changed things (by enabling collaboration and server-held state, a.k.a. "the cloud").

I could start listing Boston companies that fell into this trap, both during the one-to-two transition and during the two-to-three but ultimately I am not sure whether there are more of them per capita than in any other tech hub except Silicon Valley. Perhaps what we should be wondering is why the folks in the Valley have managed to avoid these competency traps whereas those in Silicon Alley, Research Triangle, and Route 128 have not.

Except that now even my favorite networked productivity company, Google, seems to be trying to get all jiggy with social features. And the results are sort of gross. For instance, you get this heinous fly + man in transporter creation like "Google Reader + social" which leaves those of us who used Reader happily for years scratching our heads.

Perhaps we all ought to remember that, as Metcalfe says, the thing that matters is getting stuck on to something meaty and meaningful. And since I believe there is still so much untapped potential to the "networked productivity" phase, this seems like a good place to park. Maybe once we've done with the euphoria of tweeterbookspacing, some more folks around here will remember that.

Comments Permalink