Adobe CEO: Flash coming to Android, WebOS and BlackBerry ‘smartphones and tablets’ in 2H 2010

This week Adobe released version 5 of its Creative Suite software compilation. CEO Shantanu Narayen has naturally hit the interview trail to promote his company’s wares, but the biggest news from him is actually a delay of sorts. We’d previously heard that Android, WebOS and BlackBerry versions of Flash 10.1 would be available in the first half of 2010, but Adobe’s chief now places delivery to those platforms in the second half of the year. At least consolation may be found in his teasing of new Flash-enabled tablets — most likely to be running Android or Chrome OS — which we’re told to expect to see within the same time frame. As to the question of Apple’s holdout from Flash nirvana, Narayen describes it as a business rather than technology decision, which “hurts consumers” and will ultimately be judged by people voting “for the experience that they want through their wallet.” Can’t really argue with that. Skip past the break for the full interview.

Update: The blog of Adobe’s Lee Brimelow gives us a likely reason for the delay: Flash Player 10.1 for Android has just entered private beta, as has AIR 2.0, with public betas on the way. Devs can sign up to be notified about both right here.

Continue reading Adobe CEO: Flash coming to Android, WebOS and BlackBerry ‘smartphones and tablets’ in 2H 2010

Adobe CEO: Flash coming to Android, WebOS and BlackBerry ‘smartphones and tablets’ in 2H 2010 originally appeared on Engadget on Sun, 18 Apr 2010 06:07:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceFox Business  | Email this | Comments

PhoneGap framework fine for App Store development, sez Apple

Now, we’ve all been concerned about recent updates to the iPhone dev agreement — you haven’t been sleeping and your parents are, quite frankly, worried for your sanity. And it’s a heady subject: “what is the fate of PhoneGap in the wake of the iPhone OS 4 beta SDK?” Well, worry no more, little one — it seems that Jesse Macfadyen, a contributor to the project, pinged Apple to make sure that users of the mobile development platform wouldn’t find their apps rejected simply for using the tool. As you remember, the agreement states: “Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine” (and of course HTML and CSS are cool), so PhoneGap — which indeed sticks to HTML, CSS and Javascript — is totally safe. Now developers can get back to having their apps rejected for any number of other silly reasons.

[Thanks, Bea]

PhoneGap framework fine for App Store development, sez Apple originally appeared on Engadget on Thu, 15 Apr 2010 03:04:00 EST. Please see our terms for use of feeds.

Permalink Mac Stories  |  sourceJesse Macfadyen’s Blog  | Email this | Comments

Skyfire boss on possible iPhone port: ‘stay tuned for news’

So Opera Mini for iPhone has proved to be kind of a big deal, and that HTML-laden beacon of hope is putting a twinkle in some other developers’ eyes. Take Skyfire, for instance. CEO Jeff Glueck posted this week a congratulations to the Opera team for its inclusion in the iTunes app store — a surprise to many, us included. He also explained that “this will certainly accelerate our strategy on iDevices,” and seeing as its only product is a mobile browser with Flash and Silverlight, Jeff certainly has our attention here. That said, we’re not exactly getting our hopes up, especially since the App Store’s rules have always forbidden any app from running a code interpreter and we don’t see how SkyFire can bypass that aspect of Flash and Silverlight entirely, even though it uses a server-side rendering model similar to Opera Mini’s. We’ll see what happens.

Skyfire boss on possible iPhone port: ‘stay tuned for news’ originally appeared on Engadget on Wed, 14 Apr 2010 21:57:00 EST. Please see our terms for use of feeds.

Permalink Download Squad  |  sourceSkyfire blog  | Email this | Comments

MeeGo Gone Wild! Features detailed, companies come on board at IDF 2010 (updated)

Wow, the MeeGo news is flying fast and furious today! Our first stop is the Intel Developer Forum, where a recent talk detailed feature lists for netbooks and handhelds running (presumably) 1.0. For the former, you can expect to see it rockin’ Chrome (or Chromium), and overhauled social messaging, media, camera, email, and calendar apps. That’s in addition to touch and gesture support. As for handhelds, Fennec with Flash support popped up on the slides (probably a carry-over from Maemo, since they already have Mozilla with Flash), VOIP (at least until the carriers get involved), instant messaging, social networking, location-based services, cloud data syncing, and portrait mode support — not to mention “the Intel app-store framework that can be used to make branded 3rd-party app stores.” But that ain’t all! According to some freshly minted PR, the Hotel Kabuki in San Francisco will be lousy with developers starting Wednesday when the Linux Foundation Collaboration Summit begins in earnest. To be announced at tomorrow’s keynote are a host of companies that are throwing their lot in with the mobile OS, including: EA Mobile, BMW Group, Acer, Gameloft, Novell, ASUS, and more. Which is all well and good, but the question remains: when are we finally gonna get our hands on an LG GW990? PR after the break.

Update: We added a couple shots of the very in-progress UI from Intel’s slide show. See more after the break.

Continue reading MeeGo Gone Wild! Features detailed, companies come on board at IDF 2010 (updated)

MeeGo Gone Wild! Features detailed, companies come on board at IDF 2010 (updated) originally appeared on Engadget on Tue, 13 Apr 2010 12:33:00 EST. Please see our terms for use of feeds.

Permalink Carrypad  |   | Email this | Comments

Steve Jobs responds directly to developer over new iPhone SDK rules, cites blog for explanation

Plenty ink has already been spilled about the new restrictions in clause 3.3.1 of the new iPhone SDK terms of use. The new wording disallows developers to use third party, cross platform development tools (like Flash CS5) to build their apps, and plenty of folks (like Adobe) are angered by it. Now it seems Steve Jobs has chimed in as well. Developer Greg Slepak reached out to Steve, citing the large outpouring of negativity on the topic, including a post by John Gruber of Daring Fireball, who Greg calls Apple’s “biggest fan.” Steve apparently responded, citing a newer post by Gruber that explains Apple’s theoretical reasoning for locking down the platform like this. Steve called the post “very insightful.” When Greg replied, raising some very legitimate defense that highly popular, important apps like Mozilla Firefox are built with cross platform frameworks, Steve Jobs had a slightly less terse response:

We’ve been there before, and intermediate layers between the platform and the developer ultimately produces sub-standard apps and hinders the progress of the platform.

On Greg’s blog he breaks down some of Gruber’s claims and makes a pretty compelling case for third party toolkits — important examples of which can be found all over the Mac and Windows landscape. We get the feeling his impassioned pleas, and the oft-bandied threat of developer migration, will fall on deaf ears at Apple as always, but at least he helps shape this debate somewhat, which will no doubt rage on for months and years to come. Check out the full conversation between Greg and Steve, including Greg’s final response, after the break.

Continue reading Steve Jobs responds directly to developer over new iPhone SDK rules, cites blog for explanation

Steve Jobs responds directly to developer over new iPhone SDK rules, cites blog for explanation originally appeared on Engadget on Sat, 10 Apr 2010 20:48:00 EST. Please see our terms for use of feeds.

Permalink Mashable  |  sourceTao Effect Blog (Greg), Daring Fireball (Gruber)  | Email this | Comments

Firefox Lorentz beta doesn’t crash entirely when plug-ins get fussy

Admit it, your love for Firefox is tempered by sometimes sluggish performance and a penchant for perennial plugin crashes. Google did what it could with Chrome to isolate such issues by ensuring the entire browser didn’t crash when Flash (or any other add-on, for that matter) went belly up. Now it looks like the gang at Mozilla are adopting a similar tactic, and if you want to try it out for yourself, the Lorentz beta is now available for download. So sayeth the site, “If a plugin crashes or freezes, it will not affect the rest of Firefox. You will be able to reload the page to restart the plugin and try again.” Whodathunk we’d ever feel actual elation at such a proclamation?

Firefox Lorentz beta doesn’t crash entirely when plug-ins get fussy originally appeared on Engadget on Sat, 10 Apr 2010 05:39:00 EST. Please see our terms for use of feeds.

Permalink Lifehacker  |  sourceMozilla  | Email this | Comments

Adobe Reacts to New iPhone App Policy (Updated)

flash

The introduction of multitasking in iPhone OS 4 was great news for app developers and consumers, but Apple left unmentioned one policy tweak that could significantly change the App Store game.

As Wired.com reported Thursday, Apple previewed its next-generation iPhone operating system and released a beta to developers, which included a new developer’s agreement stipulating that iPhone apps must be originally programmed using Apple-approved languages (such as Objective-C).

The official iPhone OS 4 won’t be available until summer, so the exact implications of the policy change have yet to be seen. However, the consensus among several developers and tech observers is that the biggest and most obvious loser is Adobe, who has been touting a new tool called Packager for iPhone, which would enable Flash developers to easily port their apps into iPhone-native. This solution, which is set for an April 12 release as part of Adobe CS5, would partly address the lack of native Flash support for the iPhone and the iPad.

Adobe’s reaction to the news on Thursday wasn’t substantive (”We are aware of the new SDK language and are looking into it”), but Lee Brimelow, Adobe’s Flash evangelist, had some more colorful words today.

“Adobe and Apple has had a long relationship and each has helped the other get where they are today,” Brimelow wrote in his blog. “The fact that Apple would make such a hostile and despicable move like this clearly shows the difference between our two companies. All we want is to provide creative professionals an avenue to deploy their work to as many devices as possible. We are not looking to kill anything or anyone.”

Brimelow ended his post with, “Go screw yourself Apple.”

Meanwhile, Adobe has issued a filing with the Securities and Exchange Commission stating that “our business could be harmed” as “new releases of operating systems or other third-party products, platforms or devices, such as the Apple iPhone or iPad, make it more difficult for our products to perform, and our customers are persuaded to use alternative technologies,” as Bloomberg first reported.

The clause from the iPhone developer’s agreement in question is 3.3.1, which reads:

3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

Apple did not return a phone call requesting comment on the new developer agreement.

Update 5:55 p.m. PT: Kevin Lynch, Adobe’s chief technology officer, has posted his level-headed response to the revised iPhone developer agreement:

It is up to Apple whether they choose to allow or disallow applications as their rules shift over time,” Lynch wrote. “Secondly, multiscreen is growing beyond Apple’s devices. This year we will see a wide range of excellent smartphones, tablets, smartbooks, televisions and more coming to market and we are continuing to work with partners across this whole range to enable your content and applications to be viewed, interacted with and purchased.”

See Also:

Photo: Brian X. Chen/Wired.com


Adobe says iPhone / iPad adoption and ‘alternative technologies’ (cough, HTML5) could harm its business

Adobe might continue to crow about Flash and its importance on both the desktop and mobile devices, but there’s no lying to investors, and the company is pretty blunt about the threat of the iPhone and iPad in the end-of-quarter Form 10-Q it just filed with the Securities and Exchange Commission: it flatly says that “to the extent new releases of operating systems or other third-party products, platforms or devices, such as the Apple iPhone or iPad, make it more difficult for our products to perform, and our customers are persuaded to use alternative technologies, our business could be harmed.”

Now, Adobe has to make doom-and-gloom statements in its SEC filings — it also says that slowing PC sales or a failure to keep up with desktop OS development could harm its business — but the timing is crazy here, since just yesterday Apple changed the iPhone OS 4 SDK agreement to block devs from using the upcoming Flash CS5 iPhone cross-compiler to build iPhone apps. What’s more, Apple’s also using HTML5 for its new iAd platform, which could potentially undo Flash’s stranglehold on online advertising as well. Yeah, we’d say all that plus the recent push for HTML5 video across the web — and from Microsoft — could harm Adobe’s business just a little. Better hope that final version of Flash Player 10.1 is everything we’d hoped and dreamed of, because Adobe’s going to have to make a real stand here.

Adobe says iPhone / iPad adoption and ‘alternative technologies’ (cough, HTML5) could harm its business originally appeared on Engadget on Fri, 09 Apr 2010 11:50:00 EST. Please see our terms for use of feeds.

Permalink BusinessWeek  |  sourceAdobe Form 10-Q  | Email this | Comments

Adobe distances itself from JooJoo, cites lack of ‘direct relationship’

Well, this is just a huge surprise. In response to our not entirely glowing review of the JooJoo, Adobe’s PR team has gotten in touch to inform us that Fusion Garage “has no direct relationship with Adobe.” Citing the young startup’s non-participation in the Open Screen Project and use of “a public beta release [of Flash] designed only for desktop use,” Adobe is drawing a thick line between itself and the JooJoo, and urges us to instead look at the alternatives from its partners like HP, Dell and Lenovo. Mind you, not one of those companies is (as yet) selling a competing tablet, and it’s not like there’s some magical formula that will make 720p Flash video run smoothly on a bare Atom CPU (remember, Ion GPU acceleration is not yet available for the Linux-based JooJoo), but who are we to stand in the way of a carefully worded damage limitation statement? Click past the break for the entire thing.

Continue reading Adobe distances itself from JooJoo, cites lack of ‘direct relationship’

Adobe distances itself from JooJoo, cites lack of ‘direct relationship’ originally appeared on Engadget on Fri, 09 Apr 2010 08:12:00 EST. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Apple’s iPhone lockdown: apps must be written in one of three languages, Adobe in the hurt locker

Apple’s already got a veritable novella describing things you can’t do with the iPhone as a developer — create apps that execute their own code is the biggie, obviously, blocking technologies Flash and Java in the absence of a loophole — but it seems they’ve locked down the ecosystem just a little further today with the release of the iPhone OS 4 beta SDK. Check out this snippet from the developer’s agreement:

Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

What does that mean, exactly? Well, it means that technologies like Adobe’s iPhone compiler in Flash CS5 won’t be allowed, simply because the source code of the app that you’re writing isn’t in a language Apple’s comfortable with. The compiler had been seen as a potential boon for Flash devs that had already been blocked out of the iPhone ecosystem for lack of a true Flash player, but Apple’s found a way to block even this workaround — technically you don’t need to be using Apple’s own tools, but you’ve got be using one of three variants of a single programming language. It’s hard to say why Apple cares, exactly, but we suspect that the company would have to analyze your app pretty closely to detect variances in how the compiler produced your machine code in order to determine that you’d violated the rule.

This could be a blow to publishers — Condé Nast included — who’d been banking on Adobe Air to lead the digital push, since those guys presumably won’t be able to bring their issues to the iPhone (and, more importantly, the iPad) without violating the terms of Apple’s agreement. Protectionism is a core element of the iPhone’s success, in Apple’s view — but ultimately, this might come out as a decision that’s difficult to defend, unnecessarily sours publishers to the platform, and turns Flash devs’ heads just a little grayer than they already were.

Apple’s iPhone lockdown: apps must be written in one of three languages, Adobe in the hurt locker originally appeared on Engadget on Thu, 08 Apr 2010 22:59:00 EST. Please see our terms for use of feeds.

Permalink Daring Fireball  |  sourceApple  | Email this | Comments