At least I have the feeling that widget initiatives like W3C Widgets http://www.w3.org/TRa/widgets-reqs/ or JIL http://www.jil.org (Verizon Wireless, Softbank, China Mobile) have a lot more traction with telecommunication companies. Opera is very active in the space as well, and BONDI http://bondi.omtp.org/whatisbondi/SUPPORTERS/Home.aspx looks like a promising approach to drive Widget integration with phone hardware. Look at the impressive list of supporters: http://bondi.omtp.org/whatisbondi/SUPPORTERS/Home.aspx
It's going to be interesting to see if the relatively new mobile HTML5 frameworks like Sencha will be able to compete with established products and standards in the mobile widget market. Of course, W3C widgets are HTML+JS+CSS based as well, just packaged into a standard format with a descriptor file. So you could build a W3C Widget with Sencha, OpenLaszlo or any simple HTML page you have. There a many competitors in the industry in Europe - don't know the U.S. market to well, and I'd say you'd have to partner up with a few large telcos to get traction in the market. For telcos, it's much about the ability to create a new mobile app marketplace, independent of Apple or Google. 2010/6/21 Raju Bitter <[email protected]>: > Yes, I looked into the framework as well. While it's technically a > promising approach, I doubt that we'll see as many HTML5 based mobile > apps in the near future, as long as there's no app store integration. > The main reason why we have so many iOS and Android market apps today > is the fact you can good money by writing apps. If you have a customer > paying for the development, the Sencha approach is good, but for > individual developers or small companies planning to make money by > selling mobile apps, it's a different story. > > The other technical question is: how are you going to access native > APIs out of HTML5? If you are limited to what's exposed within the > mobile browser, that's not really that much. > > On Mon, Jun 21, 2010 at 5:00 PM, Sarah Allen <[email protected]> wrote: >> I saw a presentation on this last week. It runs on Android and iPhone for >> mobile. It's a very procedural approach. They have a designer app for Ext >> JS, but it doesn't seem to have been updated for mobile and either the app >> is really flakey or I haven't figured out how to use it in 5 mins :) >> >> Having jQTouch run on Android is pretty compelling for mobile developers. >> Apparently developers are seeing incompatibility in webkit versions across >> Android devices. I've only done Android on my Nexus One and not any fancy >> apps, so I haven't seen that personally. >> >> My $.02 >> Sarah >> >> On Jun 21, 2010, at 7:45 AM, P T Withington wrote: >> >>> Ext JS + jQTouch + Raphaël = Sencha — Sencha Blog — JavaScript Framework >>> and RIA Platform http://bit.ly/acgHmO >>> Source: http://www.sencha.com/blog/2010/06/14/ext-js-jqtouch-raphael-sencha/ >>> See who is talking about this page: http://bit.ly/acgHmO+ >>> Brought to you via http://bit.ly >> >> >> >
