BlackBerry WebWorks Updates: Ripple Emulator and API Reference


Updates to BlackBerry WebWorks

We’re happy to announce that shortly after joining Research In Motion® (RIM®), the tinyHippos crew have an update available for the Ripple emulator BETA program, which now includes support for most of the BlackBerry® WebWorks™ APIs. It also provides skins for the BlackBerry® Bold™ series of smartphones, the BlackBerry® Torch™ 9800 smartphone and the BlackBerry® PlayBook™ tablet.

This BETA update will allow you to place your BlackBerry WebWorks app on a local web server, point the Ripple emulator at your website and test your BlackBerry WebWorks application without having to compile or load it onto a simulator during your development process. Of course, we recommend performing your final testing on a simulator – or even better, a live device – to ensure your application works the way you intend before making it available to your users.

This update is just one step forward towards how the Ripple emulator will evolve over the course of this year. Stay tuned for more updates on the direction of the Ripple tooling along with further steps towards bringing the smartphone and BlackBerry Tablet OS BlackBerry WebWorks SDKs together.

We’re also excited to announce further steps towards a converged BlackBerry WebWorks platform between BlackBerry smartphones and BlackBerry PlayBook tablet OS. We have now released an updated version of the BlackBerry WebWorks API Reference that brings both the smartphone and tablet OS APIs together in one consolidated reference guide.

This reference guide also includes documentation for all the HTML5 and web application APIs that are available within BlackBerry WebWorks applications. New documentation features have been added including filters based on OS version, table of contents and object listing views, updated look and feel, and tabling tools showing which APIs are supported on which platform. This new API documentation is also available for community collaboration on along with the project’s roadmap.

About Tim N.

Tim leads Application Platform & Tools Product Management at Research In Motion. This includes APIs, Frameworks and Tools for the BlackBerry Platform. He can be found hanging out in the development forums or Twitter (@brcewane) trying to help out where he can and to bring your feedback into the next releases of BlackBerry tooling. You’ll also see Tim presenting various topics at the BlackBerry Developer Conferences and BlackBerry World so be sure to stop by and say hi. Just don’t start talking about cars or Batman or you won’t be able to get rid of him.

Join the conversation

Show comments Hide comments
+ -
  • tinyHippos Ripple Emulator Beta Now Supports WebWorks APIs Along With Better Documentation - BerryReview - Mobile Edition

    […] especially with HTML5 mobile apps (think WebWorks).I have not had a chance to play with it yet but according to RIM the new Beta of Ripple will let you place your BlackBerry WebWorks app on a local web server and […]

  • Anonymous


  • BlackBerry WebWorks Tooling Evolved | BlackBerry Developer's Blog

    […] is where tinyHippos and the Ripple Emulator becomes an important piece of the puzzle. Being able to point to a website (local or remote) […]

  • Porting your BlackBerry WebWorks application from the BlackBerry PlayBook to the BlackBerry Smartphone (and vice versa!) | BlackBerry Developer's Blog

    […] smartphone and tablet platforms. Check out the blog post on the Ripple Emulator beta program here. We highly recommend using this tool to develop your BlackBerry WebWorks applications as it […]

  • a letter from the outer space: why developing apps for BlackBerry ? | ekkes-corner: eclipse | osgi | mdsd | erp | mobile

    […] Ripple eases testing and debugging of mobile WebApplications directly inside the Browser. Only one mont after tinyHippos was acquired by RIM they presented first results: BlackBerry WebWorks 2.0.0 was supported now together with first 3 simulators for BlackBerry Torch, BlackBerry Bold and BlackBerry PlayBook. read more at BlackBerry Developer Blog: […]

blog comments powered by Disqus