Mobile mobile 2.0 mobileweb Web Design

W3C Mobile Web Best Practices Flip Cards

Go get your Mobile Web Best Practices Flipcards now. These summarize the Mobile Web Best Practices 1.0 document. The flipcards are a useful reminder of the sixty guidelines explained in detail in the specification. A PDF version of the cards is available.

AJAX iPhone Mobile mobile 2.0 mobileweb

Mobile device client software vs. mobile websites

According to the Netbiscuits blog

The main advantages of client based mobile Web applications are that they provide very good possibilities for graphic design of user interfaces and keep content available even offline. Furthermore, they often show faster reaction times and are sometimes easier to link to other telephone functions such as directories, camera, etc. The main disadvantage of every client-based solution is that they initially need to be downloaded by the user and installed on the mobile – a practice that will need to be repeated for every new release. Many users are prevented from taking this step due to technical problems, security issues and a lack of clarity concerning costs involved. Furthermore clients are always dependent on the mobile phone operating system and must often undergo costly adjustments for each individual terminal.

Mobile sites, on the other hand, do not require any installation. They are immediately available over the browser and the sites’ content and software are continuously updated unobtrusively to the mobile user. Mobile sites also provide a greater scope of outreach than clients do, as nowadays practically all mobile phones have a browser. Adjusting mobile sites and rich media content to various mobile terminals can be made 100 percent automatic. This means a massive reduction in development and testing expenses. User interface design is also no longer an obstacle. Modern mobile phone browsers enable use of AJAX and Flash, thus creating a user experience similar to that of PC Web. If a company is looking for a larger audience reach with as little hassle as possible, the mobile site is the clear winner.

I totally agree. The one thing that I advocate is to have some kind of markup language that allows the browser to have access to native device functions such as the PIM, camera, etc.

iPhone Mobile mobile 2.0 mobileweb Pervasive Computing Technology

Why I am not getting iPhone 2.0

Just take a read at this NYT article entitled “New iPhone Pricing Model Is a Step Backward for Consumers” and it explains exactly why I am not going to be in the market for the new iPhone 2.0.  Apparently, Apple and AT&T have closed off the biggest loophole that existed that enabled iPhone 1.0 users to ability to jailbreak their iPhones and do with them as they pleased. What exactly was that loophole? They won’t let you walk out of the stores with the new iPhone 2.0 without signing up for the new 2 YR contract!  That’s right.  Loophole closed.

What does iPhone 2.0 offer that warrants an upgrade?  GPS, 3G, and slightly larger storage.  That simply is NOT enough to warrant the extra $30 / month I’d have to shell out to get the new iPhone 2.0.  I currently pay $55 incl. taxes and fees for my iPhone 1.0 plan, and I thought that was pretty hefty to begin with.  This new plan simply is highway robbery!  Apple and AT&T, no thanks, but I’m sticking with iPhone 1.0.