Opera Widget Strategy: Widgets everywhere….
This interview with Opera CEO gives some hints about Opera strategy in Widget space.
Opera is probably one of the players with the best positioning. Technically, they will benefit from their Opera platform, that contains already some important piece for a widget engine, the rendering engine, a script interpreter. Even better, their proxy technology that allows the transcending “on the fly” of widget from PC to Mobile is also a key benefit.
They also have on of the most deployed browser, so their strategy make sense.
Is this the ultimate solution for widget? I am not convinced, for different raison that I’ve already raised. A widget running on desktop and mobile will be different. Not only for size reason, but for usability reason: keyboard instead of mouse, other input functions, etc…. What will be the easiest path? To create very simple well adapted to different device, or try to create a single app adapted to all device?
I think that some widget could be easily adapted, a clock, or a weather widget are probably things that could be easily scaled to different platforms, but does a “phone book widget” on a mobile will be the same than a “phone book widget” on a PC?
Technorati Tags: j2me, javame, mobilewidgets, widgets
2 comments July 26th, 2006