Archive for January, 2008

N95 + ATT Browser Image Issues

Thursday, January 3rd, 2008

Russ and I spent a bit of time poking around today with the Mowser images on the Nokia Open Source browser on the N95. For some reason I was getting these really crappy looking images when I loaded the site, just absolute junk. I’m on ATT in the US, so we tried from some other ATT phones and they worked out fine. I had seem some similar issues before when I was fooling around with HSDPA and EV-DO connections for my lappy, so to remove the network from the equation I connected my N95 over wifi and reloaded. Bing! Crystal clear images.

After a bit of searching I found a post about the proxy being used for images by ATT in the US causing problems for N95 and E90 devices. I tried duplicating the AP, removing the proxy info, changing the connection, and reloading. No better image quality however. The post says you need to reboot in order to make the change work. In retrospect all I probably needed to do was shut down the browser, but I rebooted anyway. Sure enough, crystal clear images! I’m really surprised the devices are getting configured that way on a fast network like the N95 uses on ATT. Thanks Zach! Now, certainly would be nice if devices were unfucked by default once you get them configured on ATT. Wouldn’t that be nice?

Colocated Mowser

Thursday, January 3rd, 2008

Russ and I sat down in the same room to work on Mowser stuff for pretty much the first time yesterday. Between the holidays and just stuff that had piled up and needed to be done, it was just the first real chunk of time we had to get work done. Both of us have worked remotely or virtual office or whatever you want to call it. I spend a few years actually working with a group of folks I hadn’t met in person till about 2 years into the project.

Still it was amazingly effective to be in the same room working on stuff for a chunk of time. We found a bunch of little bugs, brainstormed how to fix a few issues that were kicking around, and implemented big chunks of a new feature. In a few days we’ll have stuff synced up well and we won’t need to be in the same place. Right now though it’s having a tremendous impact. Much more drastic than I had expected.

The Mobile Web or One Web, or Something Else

Wednesday, January 2nd, 2008

One of the questions I keep hearing over and over again is “Are better devices and more capable browsers going to lead to the death of the mobile web? Are we going to stop thinking about the mobile web as a separate medium and just do web development?” Eventually that might be the case, but a number of things would have to happen first. So instead of trying to answer that emotionally charged question with a relatively meaningless yes or no, let me lay down a few factors that hopefully indicate why people are asking it so frequently now.

The impetus of course has been the iPhone, and the ability of the browser on that device to render any web page out there pretty much and present a fantastic version to the user. Does that mean that there won’t be a mobile web any more however? That depends on what you define as mobile web, which is ultimately a somewhat boring question when compared to how to make pleasing applications for mobile phones. What the iPhone is calling into light is that one of the conditions that brought about the split between authoring for traditional browsers and authoring for mobile devices is starting to fall away.

The split between mobile web development and traditional web development was supposedly based on two factors : technology and user experience. The technology aspect was that the networks were much slower than wired networks at the time and the devices had less ram and slower processors. What that led to was using different markup for the pages themselves. Something that was stricter in the computer science sense and easier to interpret on the device and validate in the network. Something that dropped out a lot of features and functions normally found on the web as it was. The user experience end was about presenting the information in a format that was more suitable to viewing on a smaller screen and interacting with one handed while on the go.

The iPhone proves that with current technology and on relatively recent networks the technology argument for mobile web content as something distinct from traditional web content is dead. Leave aside all the questions about Apple’s market strategy, pricing, carrier reactions, etc. Stripped down to just a technology question the iPhone has demonstrated that a handheld device can consume and present existing web content in a way that most users find at least acceptable. Done.

However does that mean that this thing we think of as the mobile web goes away? I don’t think so, I think it just shifts purpose. Take an example right from the iPhone itself. The iPhone renders the front page of the Digg news site no problem, but still there’s an iPhone optimized version of Digg available just the same. This is the mobile ecosystem working just as it should. Now that the question of what is technically possible has fallen away, the new issues becomes what is most useful and pleasing to the end user. In the case of Digg they apparently saw a way to put together the content they had in a way that better served the group of mobile users who are on iPhones.

I think that’s going to be the general trend. And it’s a good thing, it means mobile is moving up Maslow’s pyramid. We’re out of just simple survival and life functions and starting to think about how to make things more useful and pleasant. I think in the early days we had only two kinds of apps: mobile and not mobile. With things starting to blend between the two environments I’m seeing things starting to break down into four major areas (with admittedly very fuzzy boundaries):

  • Mobile specific applications
  • Mobile enhanced applications
  • Mobile aware applications
  • Mobile unaware applications

They’re actually overlapping group of apps, looking like this if we ignore the number of apps in different groups and think just about their relationships:

Mobile Web Applications Overview

The mobile specific applications are the ones that really only make sense when they have their mobile interface as the primary driver. They’re based on being primarily realtime and rely on some bit of info that you can only get at easily while mobile, such as current location. Take MizPee for example. Sure, you might be paranoid and check the location of public toilets before every outing. But most likely you’re going to use it when you need it and you’re in an unfamiliar area.

Mobile enhanced applications are ones that have taken their service and transformed interaction to suit usage from mobile devices better or have included some features mainly focused on mobile users. That can either be something like the mobile version of Yelp, which has a mobile version that changes the amount of info and presentation drastically from the desktop version. Or an application like Jaiku, which pretty evenly splits the difference between mobile app and desktop app in my opinion (even though I think everyone though of it as a mobile app at first, I think it’s found a lot of utility even among the wired only crowd). It has a traditional website, mobile specific pages, SMS integration, and IM capabilities.

Mobile aware applications are ones that have an ability to tune what they return to a browser to make it more appealing but don’t really make any changes to the content or add features. A Wordpress blog running a plugin that provides a mobile version, like the one that Andy Moore has been releasing I would consider in this category. Lots of the folks who are using it are concentrated on the traditional web, but wanted to have a version available that would work well on mobiles.

Finally there are the mobile unaware applications, which are just what they seem, do nothing in reaction to a mobile device. That doesn’t mean they don’t work on mobile handsets, just that they only work on mobile handsets that are able to render their pages and present them.

I think there’s a pretty strong resemblance between the levels of support for mobile that we see now and the evolution of the web itself. There were web specific plays like Amazon and Google, web enhanced companies like Dell and IBM who started going direct to consumer while keeping their traditional distribution channels, and simply web aware companies that put up their brochureware site so that they would have something to point to for the other members of the web ecosystem. I think the same thing is happening in mobile. And like what happened on the web the most value exists in the system when the set of sites out there that are mobile aware completely overlaps with all available sites.

Over time if the “mobile specific” things get baked right into the standards that make up the wired web, and the platforms all support all the different mechanisms you might want to use to tweek your site for use from a mobile (or do it themselves) then yes, we stop talking about the mobile web as a separate thing. But I don’t see it disappearing completely even over the long term. And I think the decisions are going to remain explicit, and reaching higher levels of capability is pretty costly. With Mowser we’re trying to make it as dead simple as possible for folks to at least hit that mobile aware stage and start participating in the growth that’s happening in web usage from mobile devices. If the mobile web is going to evolve away from carrier control we need as many participants as possible to balance out the distribution of power.

January 2008 Silicon Valley Mobile Monday

Wednesday, January 2nd, 2008

I just posted the details for the January 2008 SV Mobile Monday:

  • What: January 2008 Mobile Monday (Open Source)
  • When: January 7th, 2008 7:00pm
  • Where: Microsoft SV Campus, 1065 La Avenida St. Building 1, Mountain View, CA 94043
  • Who: Anyone interested in mobility
  • Cost: Nothing!

It’s about an area I’m very passionate about, and the word open has started to get thrown around in mobile circles with disturbing frequency. Sometimes it’s really justified, other times it’s obvious that it’s being used just to join in the hype currently surrounding the concept of openness. So lets shed a little light on what the difference is between open source, open standards, and open networks. What parts of the movement are new, and what moves are older players just moving themselves out of broken models but trying to appear innovative. We should be able to have a great discussion, there’s a lot of meat to the topic. Hope to see you there!