Tuesday, January 08, 2008

Yahoo Go: because we all love SDKs

If you are a mobile developer, you are already a frustrated individual. You dream of a world with one mobile operating system and one SDK (wait, are you sure, take a look at what you have in front of you...), instead Yahoo at CES has just announced yet-another-mobile-SDK.

Damn, can't life in mobile be easier?

If you want to build a mobile app today, you can choose from:
When you think you are done with the list, boom! Yahoo comes up with a mobile platform over a mobile operating system. A sort of a middle layer that allows you to develop your applications on top of that. Not that far, as a concept, from JavaME or Flash. Certainly, more focused in scope.

The issue? Well, a mobile platform over an operating system might be a bit large in size and slow as hell. Hey, you can always hope in Moore's law.

The opportunity? Well, they already ported their platform over the other operating systems. If they make it really consistent (doable), you develop once and it will run everywhere. That's a developer dream.

The risk? Well, for your app to succeed, you need the underlying technology to succeed. If people do not download Yahoo Go on their phone because it is too large and too slow, you are toasted. Uuhhmmm.

Overall, I like Yahoo's move.

They needed to come up with something (anything ;-) to counter Google and Apple. They did it.

I am a fan of the mobile widget concept, as you might remember. In one of my first posts on this blog, I mentioned Yahoo going for WAP but my prediction was they would go back to mobile widgets one day. They did it.

Now they just have to make sure consumers love the platform and developers build the widgets. The problem is that the two are linked. One drives the other. And getting developers mind share in mobile is very very hard these days...

Good! Luck! To! Yahoo!
Posted by Fabrizio Capobianco at 12:07  

3 Comments:

Anonymous teena said...  

Hi, i might need your expert advices. I am new to mobile programming. My final year project title is health management and fitness monitoring using mobile application. So i don't know how to do it.Is it that creating mobile application is better than mobile WEB application. If it is can you recommend what sorts of programming tools i will be needed. Thanks.

Comment Posted at 00:50

Blogger Fabrizio said...  

Hi Teena,
it really depends on what the application will do. If there is a lot of data on the application, you might be better off with a "native" app (installed on the device). If the content changes every time, a web app might be better.

If you go for a native app, pick a platform and work on it. You can choose one, depending on the target you have. Either JavaME (if it is for a wide audience) or Windows Mobile or BlackBerry (more business audience) or iPhone (cooler people ;-) or Android (geeks for now, but it is a trendy platform). Once you have chosen the platform, check the websites and you'll find all the tools you need.

You might need Funambol if you go for the native app. It will give you data synchronization, which is a key element of a native app. It allows you to focus on the application instead of thinking about how to get the data on the device.

Good luck with your development.

fabrizio

Comment Posted at 16:54

Blogger sangza said...  

I agree with you.
I have develope some of J2ME, Symbian, WM5 and.. what's next
I hope my life will be better than this if we reduce scope to be a widget not application.

Comment Posted at 22:35

Post a Comment

Links to this post:

Create a Link

Back to My Blog