I’m quite impressed with Google’s mobile maps application for smartphones. It works nicely on the iPhone but is great on other phones too.

Among other things, it will display live traffic on your map. And I recently saw, when asking it for directions, that it told me that there would be “7 minutes of traffic delay” along my route. That’s great.

But they missed the obvious extension from that. Due to the delay, 101 is no longer my fastest route. They should use the traffic delay data to re-plot my route, and in this case, suggest 280. (Now it turns out that 280 is always better anyway, because aside from the fact it has less traffic, people drive at a higher average speed on it than 101, and the software doesn’t know that. Normally it’s a win except when it’s raining in the hills and not down by the shore.)

Now I’ve been wanting mapping and routing software to get a better understanding of real road speeds for a while. It could easily get that by taking GPS tracklogs from cabs, trucks and other vehicles willing to give them. It could know the real average speed of travel on every road, in every direction, at any given hour of the day. And then it could amend that with live traffic data. (Among other things, such data would quickly notice map errors, like one-way streets, missing streets, streets you can’t drive etc.)

Now to get really smart, the software should also have a formula for “aging” traffic congestion based on history and day of the week. For example, while there may be slow traffic on a stretch of highway at 6:30 pm, if I won’t get there until 7:30 it should be expected to speed up. As I get closer it can recalculate, though of course some alternate roads (like 101 vs. 280) must be chosen well in advance.

And hey, Google Mobile maps, while your at it, could you add bookmarks? For example, I would like to make a bookmark that generates my standard traffic view, and remember areas I need maps of frequently. And of course since traffic data can make them different, bookmark routes such as one’s standard commute. For this, it might make sense to let people bookmark the routes in full google maps, where you can drag the route to your taste, and save it for use in the mobile product, even comparing the route times under traffic. One could also have the device learn real data about how fast I drive on various routes, though for privacy reasons this should not be store unencrypted on servers. (We would not want our devices betraying us and getting us speeding tickets or liability in accidents due to speeding, so only averages rather than specific superlimit speeds should be stored.)

Also — there are other places in a PDA/phone with an address, most notably events in the calendar. It would be nice while looking at an event in the calendar (or to-do list) to be able to click “locate on the map.”

Ever since the first science fiction about cyberspace (First seen in Clarke’s 1956 “The City and the Stars” and more fully in 1976’s “Doctor Who: The Deadly Assassin”) people have wanted to build online 3-D virtual worlds. Snow Crash gelled it even further for people. 3D worlds have done well in games, including Mmorpgs and recently Second Life has attracted a lot of attention, first for its interesting world and its even more interesting economy, but lately for some of the ways it has not succeeded, such as a site for corporate sponsored stores.

Let me present one take on why 3D is not all it’s cracked up to be. Our real world is 3D of course, but we don’t view it that way. We take it in via our 2D eyes, and our 1.5D ears and then build a model of its 3D elements good enough to work in it. In a way I will call this 2.5D because it’s more than 2D but less than 3. But because we start in two dimensions, and use 2D screens, 3D interfaces on a flat screen are actually worse than ones designed for 2D. Anybody who tired the original VRML experiments that attempted to build site navigation in 3D, where you had to turn around your virtual body in order to use one thing or another, realized that.

Now it turns out the fact that 3D is harder is a good thing when it comes to games. Games are supposed to be a challenge. It’s good that you can’t see everything and can get confused. It’s good that you can sneak up behind your enemy, unseen, and shoot him. Because it makes the game harder to win, 3D works in games.

But for non-games, including second life, 3D can just plain make it harder. We have a much easier time with interfaces that are logical, not physical, and present all the information we need to use the system in one screen we can always see. The idea that important things can be “behind us” makes little sense in a computer environment. And that’s true for social settings. When you sit in a room of people and talk, it’s a bug that some people are behind you and some are in front of you. You want to see everybody, and have everybody see your face, the way the speaker on a podium would. The real 3D world can’t do that for a group of people, but virtual worlds can.

I am not saying 3D can’t have its place. You want and need it for modeling things form the real world, as in CAD/CAM. 3D can be a place to show off certain things, and of course a place to play games.

In making second life, a better choice might have been a 2D interface that has portals to occasional 3D environments for when those environments make sense. That would let those who want to build 3D objects in the environment get the ability to do so. But this would not have been nearly as sexy or as Snow-Crashy, so they didn’t do it. Indeed, it would look too much like an incremental improvement over the web, and that might not have gotten the same excitement, even if it’s the right thing to do. The web is also 2.5D, a series of 2D web pages with an arbitrary network of connections between them that exists in slightly more than 2 dimensions. And it has its 3D enclaves, though they are rare and mostly hard to use.

Another idea for a VR world might be a 3D world with 360 degree vision. You could walk around it but you could always see everything, laid out as a panorama. You would not have to turn, just point where you wish to go. It might be confusing at first but I think that could be worth experimenting with.