RIM’s expanded App Ecosystem: the benefits for developers

Announcements

BlackBerry PlayBook tablet

Jim Tobin, SVP of the Software, Services & Enterprise Markets business unit at Research In Motion® (RIM®), has a great blog post on Inside BlackBerry highlighting the benefits of our recent platform announcements for customers and developers. For your convenience, we’ve pulled out the developer-related information. Click the link at the end to read Jim’s full post!

We recently announced plans to enable developers to leverage existing assets for the BlackBerry® Java® Development Environment and Android® platforms to be easily ported to the BlackBerry® Tablet OS via ‘application players’. The application player for supported Android apps will be available this summer, followed soon after by the application player for supported BlackBerry JDE apps. Both will be available through the BlackBerry App World™ storefront.

What does this mean for Developers?

  • For the majority of developers, the way to go is still the BlackBerry platform and the widened set of tools we’ve made available. Only these can ensure that the developer harnesses the full power of the BlackBerry PlayBook tablet in terms of extremely rich graphics, full multitasking, and ultrafast processing. BlackBerry smartphone development options include the BlackBerry® WebWorks™ platform. BlackBerry WebWorks offers leading HTML5, CSS3 and JavaScript support on a mobile platform. The BlackBerry WebWorks platform also supports modern web frameworks such as Sencha, PhoneGap, jQuery and Dojo.
  • BlackBerry PlayBook tablet development options currently include BlackBerry WebWorks as well as Adobe® (Flash® and AIR®).
  • RIM will add full tooling support for native C/C++ development for the BlackBerry PlayBook tablet over the coming months. We’re highly confident about this. The QNX team RIM acquired to develop our BlackBerry Tablet OS has won awards for its Eclipse-based native Integrated Development Environment (“IDE”).

Because of the app players we’re providing, if there are developers currently developing for the Android platform, they can now rapidly move onto our platform while they evaluate our other development paths. We can now offer such developers an on-ramp to package and distribute their apps to our growing customer base of consumers, enterprises and governments.

Going forward, we will continue to evolve our various development technologies to deliver the most powerful, flexible and open experiences for developers whether they choose to build with HTML5, Java®, Adobe Flash, Adobe AIR, or native C/C++. And for those developers using our BlackBerry platform tools, we will continue to offer access to a growing set of on-device API’s to enable best-in-class integration with core BlackBerry applications and features (which we call “Super App” experiences). We are also planning to provide a range of advanced cloud-based services including the BlackBerry Payment and Advertising Services, advanced location-based services, application analytics, and powerful Push services. Stay tuned for more details on these future release plans.

Read the entire post on the Inside BlackBerry Blog »

About Douglas Soltys

Word Czar. Web 7.0 (in beta). Blogs and tweets and wonders.

Join the conversation

Show comments Hide comments
+ -
  • http://twitter.com/yousifabdullah Yousif Abdullah

    Any word on the availability of final AIR / WebWorks SDK?

    • http://www.blackberry.com/developers Mike Kirkup

      We will have a final gold 1.0 version available at launch of the PlayBook.

  • http://www.smugrik.aunetic.org Smugrik

    I think it is really nice to have such a broad range of technologies to choose from when developping for BlackBerry devices. I really like to develop apps on the PlayBook with the Tablet OS SDK for Adobe, are there any plans to port these tools for BlackBerry smartphones, so an Adobe PlayBook app could be also easily exported and packaged for BB phones?

  • http://blog.restphone.com/ James Moore

    “Because of the app players we’re providing, if there are developers currently developing for the Android platform, they can now rapidly move onto our platform while they evaluate our other development paths. We can now offer such developers an on-ramp to package and distribute their apps to our growing customer base of consumers, enterprises and governments.”

    I’m an Android developer.

    I don’t care about your other paths. They’re cute, but they’re dead ends. You’re getting destroyed in the market, right? Tell us how you’re just going to run plain Android apps, and we can consider adding some Blackberry-specific features if your marketshare happens to pull out of its death spiral.

    And please let us know that you’re going to just be able to run unmodified Android apps. Anything less is a complete waste of everyone’s time. There are some bits in there that indicate we might have to make modifications to run on Blackberry; that’s rolling-on-the-floor-laughing-so-hard-I-can’t-breathe stupid, so I doubt it’s true, but it’s tough to read your articles. They’re light on facts and heavy on marketing gibberish.

    • Todd

      I highly doubt you’re an Android developer. If you were, you would already know about repackaging your Android app. and submitting it. Nice try though.

      • http://pulse.yahoo.com/_YMJPRVT7Q2DXUE2RGLGHQODYNY Anonymous

        There is no information anywhere on the blackberry site about re-packaging an Android app for use in the Playbook as of yet. From what I can tell they have not released this for broad developer use yet.

        Please tell me I’m wrong and post the links on the info developers need !!!!!

  • Anonymous

    This is not only good for developers but will also benefit end consumers a lot as well. It’s quite a win-win solution, a right move for RIM. However I hope that it would be the same with BlackBerry smartphones OS as well.

  • Anonymous

    Any idea if this will include a plug in that for Eclipse? I bought Flash Builder and it would be very nice if I could have Actionscript/MXML and C++ open in the same editor.

blog comments powered by Disqus