On Apr 15, 3:07 pm, Fabrizio Giudici <[email protected]> wrote: > PS I'd be curious to read a good written analysis on why Sun's attempt > with OpenMoko (which could be considered as an Android precursor, at > least as a marketing concept) failed: how many technological reasons, > and how many business errors.
If I'm not mistaken, the "Java on mobile after JME" story contains three chapters: First was JavaFX Mobile as a full stack (including OS), built on the remains of SavaJe, announced at JavaOne 2007. That didn't ship because the operators didn't want to use a Sun OS on their phones (or hand over control of their platform to Sun, as we would say today in the days of the Apple-Adobe-Google wars). Then JavaFX Mobile sat on top of JME and paper-launched in Mobile World Congress 2009 with JavaFX 1.1 (and a text field as the only native component). For the proverbial 5 billion JME phones, JavaFX wouldn't do JIT compilation or use hardware-acceleration for graphics and video, unlike phones built with JavaFX in mind (if I recall an interview with Josh Marinacci correctly). That didn't ship in meaningful numbers on phones, either. The current state is hard to grasp - still no phones with JavaFX and no announcements in Mobile World Congress 2010. I read somewhere that JME and JSE are supposed to merge in the future (which would make JME even deader than it is today, if that is possible). I guess we'll hear something with the next JavaFX release (June?). Between Android and the Flash Player 10.1 being free on one hand and HTML 5 and the explosion of native mobile apps on the other hand, it's hard to see how Oracle will make money from JavaFX Mobile. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
