You Are Here:

Community: Blogs

Maximiliano Firtman's Forum Nokia Blog

The nicest and slowest UI: Yahoo! Go 3.0, Android competitor?

firt | 17 January, 2008 00:35

Recently, Yahoo! announced his new Yahoo! Go 3.0 platform (beta). “The best Internet experience on your phone. Period.” Let’s see after the period.

Yahoo! Go is a Java ME application available to many MIDP 2.0 devices and is the On-Device Portal that Yahoo! published for access mobile content provided by the company as Mail, Maps & Local, News, Financial, Sports and Web navigation.

 Yahoo! Go 3.0 is also one response to Google’s Android. It isn't a new operating system as Android, but it has the ability to host new Widgets and Snippets developed by any using the Blueprint language, an XML based language on XForms. The first thing to note is that the platform doesn't use the standard way to develop widgets: XHTML, CSS and JavaScript/AJAX, as Series 60 Widgets. All applications inside the download are Widgets developed with this language. You can download more using Internet.

A widget is some kind of application that is installed inside Yahoo Go! and can use RSS and internet information using some visual controls (similar to iPhone UI). All widgets are shown on a carrousel (like Android Home application) and when you browse them, you can see resume information about them (for example, your last e-mails or current weather information). You can access a submenu of each widget using up and down when you are over a widget on the carrousel.

A snippet is a "mini widget" that appears on Yahoo WAP Home Page and Yahoo Go Home Page and shares the layout with other snippets. They can link to widgets or external websites. All of this happens inside the Yahoo Go application that has its own browser implementation. I like more Opera Mini's renderization than this one's.

According to the roadmap, in the future the Widgets will run directly on the device. I don't know how, will it generate dynamically a JAD and JAR only for your widget? Today it hasn't some client script programming language, all the logic must be implemented server-side.

  The User Interface is really cool, smooth animations and transitions. But there is one big problem: IT'S TOO SLOW! I'm talking about the UI, not the response time from the server.

I've tried in my Nokia N95 (with a good CPU) and it's really slow. In the Home Page carrousel when I press the right or left key I've to wait one second until the UI shows next widget on the carrousel. To open a Widget sometimes you need to wait 3/4 seconds and to move from one news or item to another leaves you another seconds. Everything feels slow. Reading news and looking for some restaurants, I pressed down key to scroll the information and it reacted 7 seconds later!  To go back from a widget to the carrousel (the * key) you have to wait 3 seconds. Opening the soft key menu "Options" take 1 second or more.

You don't know if the application is alive or not. There isn't any waiting signal in the UI or clock pointer: a big UI mistake. If some operation will take more than 1 second you need to warn the user to wait.

Try it yourself in your mobile phone and tell me if it's only me ;-) Go to get.go.yahoo.com from your mobile phone or go.yahoo.com from your desktop. If you want to learn about how to develop Widgets and Snippets you can see the developer site or download the Blueprint Developer Guide in PDF.

I think it has a great UI, but if the Y! team don't speed up the UI in final version, I won't use it, and I won’t develop widgets for it. For now, Nokia's Widsets has more content developed and the UI is much faster.

What do you think?

Here is a video showing the application (on a desktop) in CES 2008 Las Vegas

 
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZrelationQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fschemasE2fnokiaE2fFNE2d1E2e58E2eowlX qdcZtitleQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qdcZtitleQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qdcZtypeQUqfnZE44istributionQ qdcZtypeQUqfnZSiteQ qdcZtypeQUqvocZTermQ qdcZtypeQUqvocZVocabularyConstructQ qdcZtypeQUqwebZSiteQ qdcZtypeQUqrdfsZE52esourceQ qswZserviceQUxhttpE3aE2fE2fswE2enokiaE2ecomE2furiE71aX quriE71aZserviceQUxhttpE3aE2fE2fswE2enokiaE2ecomE2furiE71aX qvocZpartOfQUqfnZPublicationQ qwebZserviceQUxhttpE3aE2fE2fswE2enokiaE2ecomE2furiE71aX qrdfZtypeQUqfnZE44istributionQ qrdfZtypeQUqfnZSiteQ qrdfZtypeQUqvocZTermQ qrdfZtypeQUqvocZVocabularyConstructQ qrdfZtypeQUqwebZSiteQ qrdfZtypeQUqrdfsZE52esourceQ qrdfsZisE44efinedByQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fschemasE2fnokiaE2fFNE2d1E2e58E2eowlX qrdfsZlabelQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qrdfsZlabelQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qrdfsZseeAlsoQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fschemasE2fnokiaE2fFNE2d1E2e58E2eowlX