What is really Yahoo!GO 3.0 SDK?
Finally, we had a chance yesterday to access to Yahoo!Go 3.0 SDK. As a frequent reader of this blog, you should know that Widgets is a favorite topic, so I was curious and excited about achivement of Yahoo!Go 3.0 and his SDK.
The home screen is really good, looks great. Very nice theme, with a background image and a caroussel of “widgets”. Things become bad you start to dig into the content. In fact, what is Yahoo!Go3.0 is very similar to Yahoo!Go 2.0: an enhanced browser to the yahoo content. All pages are similar to wap page, but with some improvment in the navigation. There is however some specific part that have some higher capacitities, like the “map” part which contains a GoogleMap type navigation.What really kills the experience is that the answer to every keypress (and I’ve tested this on an N95, which is usually a very fast phone) takes too much time!
So now , let’s look at the widget part and the SDK: in fact, what is promoted as “widgets” is in fact some enhanced xml/wap pages created with the “BluePrint” language. The good thing is that pages can be easily integrated within the Yahoo!Go content, and can also benefit from the integrated advertising feature.
So Yahoo!Go 3.0 is more or less an enhanced mobile browser without Ajax capacities, and these widget are XML component that can be part of the page. One of the benefit of such basic approach is that these “widgets”, can be deployed even on simple Wap/xHtml pages. The bad thing, is that it’s quite impossible to do “real widget”: very little interaction possible between the application and the user, no local caching, no access to phone features…. Seems like a step back in the times “before ajax”. Does it really make sens to build a download app if you just provides a browsing experience?
Identificateurs Technorati : yahoo, mobile, mobilewidgets
Add comment January 10th, 2008