Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
Software Yahoo! Android Handhelds IOS Programming

Yahoo's Project To Disrupt Mobile Publishing 120

Posted by timothy
from the giving-you-the-once-over dept.
waderoush writes "Right now, content publishers who want to reach readers through dedicated mobile apps have to hire a separate engineering team to build each app — one for iOS (based on Objective-C), another for Android (Java), a third for Windows Phone (C#), etc. Yahoo's Platform Technology Group is working on an alternative: a set of JavaScript and HTML-based tools that would handle core UI and data-management tasks inside mobile apps for any operating system, moving developers closer to the nirvana of 'write once, run everywhere.' The tools are gradually being open-sourced — starting with Mojito, a framework for running hybrid server/browser module-widgets ('mojits') — and Yahoo is showing off what they can do in the form of Livestand, the news reader app it released for the iPad in November. In his first extensive public interview about Mojito and the larger 'Cocktails' project, Bruno Fernandez-Ruiz, chief architect at Yahoo's Platform Technology Group, explains how the tools work and why the company is sharing them."
This discussion has been archived. No new comments can be posted.

Yahoo's Project To Disrupt Mobile Publishing

Comments Filter:
  • by scottbomb (1290580) on Thursday January 26, 2012 @03:17PM (#38832819) Journal

    Having to write for multiple platforms... the humanity!

    Back in the 80s, they wrote for Commodore, Atari, Apple, Tandy, IBM, CP/M, a handful of others.

    Maybe they got spoiled by the 90s, where MS Windows pretty much ruled all computing platforms.

  • Re:Again? (Score:5, Interesting)

    by PCM2 (4486) on Thursday January 26, 2012 @04:43PM (#38833769) Homepage

    You end up having to write two apps within one app anyway, and in javascript...

    Then again, isn't this kind of like the browser compatibility problems that jQuery aims to solve? Sure, the user has to download some code that won't be used, but the upshot is that the same code will display and function in a useful way on browsers all the way back to IE6.

The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" (I found it!) but "That's funny ..." -- Isaac Asimov

Working...