The Mobile Web 2.0

Moving blog location

2008-04-28T09:43:00.003-06:00

Howdy readers of my blog. Just wanted to let you all know that from now on, I'll be posting at my new blog. It is simply a consolidation effort so that I can keep track of things in one spot.

Point your browsers to:
http://www.cityblogz.com/blog

Point your RSS Readers to:
http://feeds.feedburner.com/thomasyung

Not to worry. This blog will still be available as an archive.

The iPhone SDK for Web Development

2008-03-10T23:12:00.001-06:00

Here's part of the announcement that Steve Jobs forgot to mention...

| View | Upload your own

Free My Phone (by Walt Mossberg)

2007-10-26T08:35:00.000-06:00

Here's a link to an opinion piece titled "Free My Phone" by Wall Street Journal's Walt Mossberg. Everything he points out is dead on, and as a consumer, I can't wait for things to change for the better.

Third Party Applications on the iPhone

2007-10-17T10:23:00.000-06:00

According to Apple's website, Steve Jobs officially announced that there will indeed be 3rd party apps for the iPhone (possibly coming in February 2008). Finally!

Third Party Applications on the iPhone

Let me just say it: We want native third party applications on the iPhone, and we plan to have an SDK in developers’ hands in February. We are excited about creating a vibrant third party developer community around the iPhone and enabling hundreds of new applications for our users. With our revolutionary multi-touch interface, powerful hardware and advanced software architecture, we believe we have created the best mobile platform ever for developers.

It will take until February to release an SDK because we’re trying to do two diametrically opposed things at once—provide an advanced and open platform to developers while at the same time protect iPhone users from viruses, malware, privacy attacks, etc. This is no easy task. Some claim that viruses and malware are not a problem on mobile phones—this is simply not true. There have been serious viruses on other mobile phones already, including some that silently spread from phone to phone over the cell network. As our phones become more powerful, these malicious programs will become more dangerous. And since the iPhone is the most advanced phone ever, it will be a highly visible target.

Some companies are already taking action. Nokia, for example, is not allowing any applications to be loaded onto some of their newest phones unless they have a digital signature that can be traced back to a known developer. While this makes such a phone less than “totally open,” we believe it is a step in the right direction. We are working on an advanced system which will offer developers broad access to natively program the iPhone’s amazing software platform while at the same time protecting users from malicious programs.

We think a few months of patience now will be rewarded by many years of great third party applications running on safe and reliable iPhones.

Steve

P.S.: The SDK will also allow developers to create applications for iPod touch. [Oct 17, 2007]

Symbian S60 platform brings it closer to iPhone

2007-10-16T09:12:00.000-06:00

Check out this new video clip on YouTube about the new S60 platform for Nokia and other Symbian based handsets. It's looking like the iPhone is finally getting a run for its money.

My experiences with the iPhone

2007-10-15T08:47:00.000-06:00

I finally bought an iPhone! Here are list of pros and cons that I have experienced thus far.

Pros

Mobile Safari web browser using Wi-Fi or EDGE. You can surf the web just as on a desktop, or you can go to iPhone specific sites that really customize the web browsing experience.
Everything you can find in an iPod, plus a mobile phone.
The thin form factor and profile is elegant and makes it feel like you're holding something luxurious.
Photos taken from camera are surprisingly good. Viewing photos on an iPhone is a joy.
Syncing all your songs, podcasts, photos, contacts, and calendar with iTunes is a breeze and brain-dead easy.
Wi-Fi Music Store. This is really a long time coming. Basically, if you happen to be at a coffee shop (i.e. StarBucks), and you like a song thats playing there, you can connect to the Wi-Fi Music Store and purchase it on the spot. To me, thats the future of how people will discover new music instead of traditionally on the radio.
An active iPhone hacker community.

Cons

No GPS. The Google Maps application is great, but without GPS you need a copilot with you when you are driving in order for it to work. Plus, it doesn't cache any of the maps. So if you are in an area without any network connectivity, you are pretty much hosed.
No wireless sync. This is something that Zune2 got right.
Can't record video.
No real 3rd party apps (no access to local storage and other advanced hardware features). UPDATE: See later post about Steve Jobs change of heart.
No disk mode. Basically, you can't use it as a flash drive as you used to be able to do with the iPod video.
Have to pay an extra $0.99 for a ringtone version of a song that you purchased at the iTunes store already. Ringtone maker won't work with MP3s or AAC files that you ripped from CDs.
No external battery. Must recharge.
Headphone jack is not compatible with other head phone makers. Duh!
Locked only to AT&T service provider for 2 years. There is a simple work-around to choose the Go-Phone Prepaid plans that have no contract obligations. Just make sure to call 611 to cancel automatic monthly refills, and you'll have a really expensive Go-Phone in your hands.
Apple and AT&T are becoming NOT so consumer-friendly. Just lookup the all the bad rap they are getting with their intentional "bricking" of iPhones and the really bad AT&T customer service.

Ok. There are more cons than pros, but that's the price you pay for being an Apple fanboy. For an alternative smartphone go check out the Nokia N95 8GB version. At the moment, its not available in North America and the price tag is $200 more than an iPhone.

iPhone Buzz (Fair and balanced)

2007-06-27T08:01:00.000-06:00

We are getting close to the launch of the iPhone and there is no shortage of media coverage. At least we are getting some constructive criticisms along with the praises. Here's a listing of some of the coverage that I've been reading...

I have one comment about the iPhone's announced rate plans. It works out the same as the current Cingular/AT&T voice plans plus the $19.99 unlimited data plan. There were rumblings that Apple and Cingular/AT&T would make it more expensive, but I think it was a wise decision not to charge more.

WWDC: iPhone 3rd Party Support?

2007-06-12T07:53:00.000-06:00

The general consensus when Steve Jobs announced that iPhone would support 3rd party apps coded as web applications was not that positive. However, I am here to say that we should keep an open mind as to what kind of capabilities that would be opened up by doing it this way. According to Bruce Stewart's post at O'Reilly:

It is after all a very good thing that Apple has decided to provide URL-based access to the iPhone’s telephony, email, and other services, but that point really got lost on the crowd I think, who were expecting an SDK to access these things. We’ve known all along that web apps would be one possibility for third-party iPhone development, and Steve’s “there’s no SDK, just use Safari and standard Web 2.0 technologies like Ajax to develop iPhone apps” message didn’t highlight the power of what they are actually allowing here. (As one colleague commented, “just try getting your web app to make an actual phone call on a J2ME-based phone.”) Personally, I think that there are a lot of interesting possibilities for third-party development with this kind of access to the iPhone’s main features, and I’m not surprised that Apple isn’t letting us get at the OS or place buttons on the home screen, but his message clearly didn’t go over well with the developer audience here in San Francisco. Read More.

Obviously, having access to basic phone functions isn't entirely new as many current mobile web browsers give this basic functionality (if your web pages are coded correctly). The real meat is if web developers are given access to local persistent storage on the phone, access to iTunes, and access to mail and calendar. Another important thing that we would need is access to the multi-touch user interface events (i.e. in addition to the standard onClick and onFocus events, perhaps we would use onPinchIn or onPinchOut events to trigger actions on the web application. I have yet to see any real specifications on this 3rd party web app API, but it does hold some promise (contrary to what many see as a disappointment).

Oh, and one last thing. I also want to be able to run Java ME on the iPhone. I already have two Java ME apps that I use constantly. Gmail and Opera Mini. It would be sweet if the iPhone could leverage the Java ME space. However, I do recall that Steve Jobs once quoted as saying that Java is too heavy weight and isn't likely to be in its future plans. Therefore, I'd assume that Java ME on the iPhone will most likely never happen.

Mobile Web Browsers button element

2007-05-30T20:43:00.001-06:00

Here's something to keep in mind when creating forms for the mobile web.

Time to stop using the button element because it doesn't render on many of the mobile web browsers.

Using your phone as a web server

2007-05-30T20:29:00.000-06:00

Zec from Zec Online Journal wrote about a new concept from Nokia demonstrated at MobileCamp event in New York for the first time - Nokia Mobile Web Server:

It's the concept of serving web pages directly from a mobile phone connected to the network.

The plan is that every mobile web server will be provided with global URL.

If every mobile phone or even every smartphone initially, is equipped with a webserver then very quickly many websites will reside on mobile phones. That is bound to have some impact not only on how mobile phones are perceived but also on how the web evolves.

Further reading at the Nokia OpenSource Wiki - Mobile Web Server describes some very interesting scenarios for possible use cases. In particular, one such scenario:

When every phone has a URL and there is a web service interface to calendar, it becomes straightforward to create a peer-2-peer based distributed calendar application without any centralized server.

This is really really cool stuff coming up. Can't wait to see how this pans out.

Amusing video about advanced Japanese mobile phone usage

2007-05-17T07:59:00.000-06:00

Amusing and instructional film about the advantages of being a smartphone user if you live in Japan!

This is why mobile phones in N. America still suck compared to those in Japan. Let's see how the Apple iPhone starts to promote changes needed to catch up.

Need better user input mechanisms

2007-05-15T12:40:00.000-06:00

It is really hard for non-qwerty keypad mobile phone users to input text into their mobile web browsers. This fact alone hinders the adoption of using the mobile web to do many of the things we normally do on the desktop web browser.

If only there was a way to save common canned responses to some datastore on your mobile phone, and simply paste them into form fields that you need to enter. I have a Windows Mobile smartphone device, and that is a feature that I most wished for. Sure... the platform supports copy and paste, but only for phones that have pen-based input. Surely, there must be a copy-paste mechanism for those smartphones that only have the joystick/keypad-based input. I have tried several mobile web browsers for my Cingular 2125 Windows Mobile smartphone device, and they all fail on providing this key feature. I tried Opera Mini (J2ME), Pocket IE, and the Opera Browser beta for Windows Smartphones, and it is an incredible chore to input text. A simple copy to datastore and paste mechanism would help alleviate this annoyance.

SXSW 2007 - Brian Fling speaks on Mobile Web

2007-03-11T20:00:00.000-06:00

Unfortunately, I wasn't able to attend the SXSW, as it looks like Mobile Web will be more prominently discussed this year. Brian Fling of Blue Flavor gave a presentation at SXSW, and here's his blog page on the subject. He includes a link to his presentation in PDF. I just finished taking a look at it, and he makes some very good points for designers and web developers looking to make a mobile version of their website. Until mobile phone web browsers have reached the same feature set as the desktop web browsers, all the things that Brian covered in the presentation are good to adhere to.

Mobile AJAX from PavingWays

2007-03-08T10:42:00.000-06:00

Here's a neat little blog post about Mobile AJAX written by PavingWays Rocco Georgi. He also has a PDF of the slides presentation that he gave in the XML conference 2006 in Boston and during the “Webmontag” in February in Munich. He says he will keep updating that page, and I'm curious to see what other web developers have to say.

My hope is that someday the mobile browser space will be advanced enough that it will rival that of the desktop browser space. That way, web developers can simply write their code once, and that it will render properly on all web browsers - desktop and mobile versions.

Mobile Phone vs Mobile PC

2007-02-04T12:43:00.000-06:00

This picture says a lot about how mobile phones and mobile PCs have overlapping features. Someday, this overlap will only get bigger.

Mobile Phone vs Mobile PC

Another article about Mobile Ajax

2007-02-01T08:30:00.000-06:00

Check out this article from The Register entitled "iPhone boosts Ajax and fluid UIs". Says pretty much the same thing as my previous post entitled "Mobile AJAX Browser Wars".

Mobile AJAX browser wars

2007-01-29T10:13:00.000-06:00

Apple's new iPhone has really put the spotlight on the mobile web experience. Up until now, mobile handsets have had a limited dumbed-down type of browsing experience from their desktop counterparts. The iPhone uses Safari webkit code which basically allows Safari Mobile to render web pages just as they were intended for the desktop. This technology is also being used by the S60 web browser that Nokia is supporting. What does this mean for web developers that wish to target AJAX for the mobile browser platform? Firstly, AJAX-enabled sites can now run on the mobile handset with little to no extra coding effort. Unfortunately, not all mobile handsets have the same web browsing feature set as the iPhone's Safari Mobile or the S60 platform. We can only hope that the iPhone will cause other handset makers to adopt the same web browsing experience and wait for the old mobile web browsers to disappear the way of Netscape 4 or IE 4. Unfortunately, we cannot wait that long.

Web developers in the desktop world have had to deal with cross-browser incompatibilities when writing code. The same can be said for the old class of mobile handsets and their fragmented support for WAP, XHTML, JavaScript, and AJAX. To my knowledge, there are only a few mobile web browsers capable of rendering AJAX.

If your phone runs on the Windows Mobile platform, IE Mobile is the default web browser installed. According to the IE Mobile developer blog, AJAX is supported on IE Mobile. Unfortunately, the JavaScript DOM support is limited. Therefore, most AJAX toolkits out there will NOT render their AJAX widgets correctly on IE Mobile. Come to think of it, I am not sure that any AJAX toolkits even consider testing on IE Mobile or any other mobile web browser for that matter.

The Opera platform is probably the most well-known mobile web browser that is capable of supporting AJAX. The only thing slowing its adoption is the fact that it is not free, and it is a separate download and install. Opera does have a free version called Opera Mini, but it is not known to support AJAX. Opera Mobile is also only targeted for Symbian and Windows Mobile platforms. This leaves out Blackberry users, which is significant base of mobile web users out there. The only other way for Blackberry users and other handsets to adopt AJAX-like functionality is through the use of Java MIDlets (J2ME). However, this requires the handset to include a J2ME runtime, and it is a separate application install. Speaking of J2ME, Mojax is yet another platform that promises to enable AJAX in a large subset of mobile devices.

To recap... Full AJAX supported mobile web browsers are far and few between. The iPhone's Safari Mobile and S60 Platform is a giant leap forward for mobile AJAX. The other players include Windows Mobile, and Opera Platform. Blackberry and the rest of the field can use J2ME technology to fill the gaps for AJAX-like web content, but it really is not a true mobile web browser experience (as it is a separate application install required). Any bets as to who will lead this pack? Let's just hope that more and more mobile web browsers will support AJAX, and that everyone works together to ensure that we do not have the same cross-browser incompatibilities that have plagued the desktop web browser world.

Resources:
http://www.fiercedeveloper.com/story/editor-s-corner/2007-01-23
http://my.opera.com/operaplatform/blog/
http://my.opera.com/operaplatform/links/

Why No Apple iPhone 3rd Party Apps?

2007-01-12T09:21:00.000-06:00

Although many OS X developers out there were salivating over the prospect of potentially creating apps for the Apple iPhone, the consensus on the web and blogosphere is that Apple is not about to do that. I believe there are two big reasons why they are right.

Firstly, Apple is renowned for its tight control over the iPod. They never opened up the iPod for 3rd party apps, so why should they start opening it up for the iPhone (which essentially is an iPod with phone functions)? Let's imagine that they let poor quality 3rd party apps to be installed on their iPods. The result is a poor image of Apple when Joe Schmoe decides to show off the app to his friends. Of course, the opposite could hold true where a killer 3rd party app gets shown, and the result is that Apple gets free good publicity. If you were Apple, would you take that chance?

Secondly, remember that they have a relationship with Cingular. Cingular would crap their pants if some 3rd party developer (i.e. Skype) created a VOIP application that allows people to by-pass the Cingular network to make calls. Think of the potential loss of revenue on Cingular's part and you can understand why Apple would be hesitant to open up the iPhone for 3rd party apps. Of course, this assumes that Apple does indeed care about their partner Cingular and that it is not just a case of the "tail wagging the dog" syndrome. If Apple does call the shots (tail wagging the dog), then this argument goes out the window.

Finally, let's not lose complete hope for 3rd party support. Apple did show off widgets functionality which in essence is really just Dashboard widgets for the phone. Dashboard widgets are really just a sandboxed web programming environment using JavaScript. Also, you have the Safari mobile browser built-in. There are a ton of web apps out there, and if people are willing to live online exclusively for their 3rd party apps, then this should not be too much of a problem.

Apple iPhone's Mobile Safari browser

2007-01-09T14:27:00.000-06:00

For me, today's announcement of the iPhone was revolutionary. The killer app isn't the phone itself, or the wide-screen iPod functionality, it was the Internet functions (specifically the mobile Safari web browser). I said it before in a previous post, and Apple took it to heart and did it. I am now ready to proclaim that the Mobile Web 2.0 revolution is about to begin. Let's see if Apple will release some iPhone AJAX APIs. If they do, it'll mean some really great killer apps waiting to come out. 2007 will truly be the year of the mobiles.

Apple's Rumored iPhone Could Disrupt Mobile Service Model

2006-12-26T17:50:00.000-06:00

I just read a very interesting post at RoughlyDrafted.com titled "Apple's iPhone: Disrupting Mobile Service"(tb) that describes how Apple could shake up the mobile phone industry with their rumored iPhone (or whatever they end up calling it).

The mobile phone market is very fragmented with mobile phone service providers dictating what technology gets implemented in mobile phones. I agree with Daniel that Apple is in a good position to shake things up. The mobile phone service providers will not do anything that will jeopardize their model of charging customers per minute or per MB, and they will certainly not make it easy for customers to switch over to Wi-Fi and the use of VOIP over it. Apple can shake things up by creating a platform and user experience that is seamless between the phone, the Mac/PC, and any other devices that are used to view information and content.

Also, I believe the killer feature on the iPhone would be an embedded version of the Safari web browser. Why? Look at what is driving Web 2.0 on the desktop; AJAX-enabled web browsers, accessible high-speed Internet, and what follows is the flurry of amazing web applications that allow users to replace their desktop applications with online versions. Give web developers the canvas and paint, and they will create their masterpieces for the mobile web 2.0.

The birth of the mobile web 2.0

2006-12-01T15:12:00.000-06:00

Get ready people! In the next few years, we will be witnessing the birth of the mobile web 2.0. The mobile lifestyle will finally become a reality. New business models will emerge, and companies that keep this in mind will flourish.

What I know is that there hasn't been much innovation in the field of pervasive computing or the idea that mobile devices can be used to access your computer applications, anytime, anywhere. There are many software applications that target only specific devices, such as Palm, Windows Mobile, Symbian, etc. Interoperability and device/platform independence has been difficult to attain. Software developers who wanted to write mobile applications had to target specific platforms. However, the web browser is the single application that ties all these devices together.

The notion that the "network is the computer" is starting to become more of a reality. We just didn't see it happening that much till now. The World Wide Web is having a resurgence due in part to "Web 2.0", "AJAX", and all these "community-based", "social-driven" web applications. This is partly because high-speed Internet access has become more ubiquitous and accessible to the masses. Web browsers on non-mobile platforms are commonplace and have recently had some incredible technological capabilities that allow web applications that mimic traditional desktop applications.

In the world of mobile computing, we have had a different experience. Surfing the web on mobile devices was very limited to whether mobile phone vendors would provide the necessary infrastructure and capabilities for these phones. In many ways, this is still the case. Web usage on mobile devices has had a slow rate of adoption due in part to data plans being too expensive, web browser features and support still in its infancy, fragmented web page markup language support (WML, xhtml, etc), and lack of any killer apps. However, in less than a few short years, I believe that will change.

A few years ago, the wireless data infrastructure was still slower than 56kbps. At least today, we can't complain that the wireless data infrastructure is slowing things down, because many of the next-gen networks are capable of some very impressive speeds. I am also starting to see some very good things happen that may usher in the new mobile web 2.0 era that we are about to embark.

This past year, Opera made an announcement that it would start making their mobile web browser more AJAX-friendly and included many Web 2.0 technologies such as RSS feeds, and JavaScript widget support. Opera makes their "paid-version" mobile browser software available on pretty much all the major phone vendors out there, and they even make their "free" Opera Mini browser available as a Java ME midlet application. This means they have their footprint in pretty much all the mobile devices out there. On the Windows Mobile platform, they already ship default with Internet Explorer mobile browser which is already capable of rendering web pages without needing websites to create WAP-friendly versions. The difference between Opera Mobile and Internet Explorer for smartphones, is that Opera is incorporating exciting new features that are key to Web 2.0, while Internet Explorer is stagnant and built for Web 1.0.

What we really need now is to have the web developer community start making those killer apps. Google has taken the lead by making many of their web applications mobile-friendly. Gmail and Google Maps have recently been ported to the Java ME specification. Also, an innovative new company called Soonr leverages the power of Opera's capability for mobile AJAX to create an interesting class of applications used for VOIP communications. Of course, other things need to also happen. These so-called smartphones need to be everywhere. Unlimited data plans from mobile carriers need to be much cheaper. There's nothing worse than getting a huge bill from your provider because you thought the 10 MB data plan was enough.

The other good thing I am seeing is that Apple is readying their rumored iPhone. This smartphone will supposedly have a mobile OS based on their desktop Mac OS X operating system. I can't help but think that this will help explode the smartphone market, in the same way that the iPod has exploded the personal MP3 player market. Imagine a Safari Mobile browser that can render AJAX-enabled web sites. This could be the catalyst needed to usher in the new era of the Mobile Web 2.0.