The Road Ahead for WebWorks

crickettachyphagiaMobile - Wireless

Dec 10, 2013 (3 years and 9 months ago)

77 views

The Road Ahead for WebWorks
JAM32
Ken Wallis – Product Manager, WebWorks
@ken_wallis
Jeffrey Heifetz – Software Developer
May 14-16, 2013
Where we are
2
Web Strategy
HTML5Test.com/compare/browser/index.html
Mobile
Desktop
ringmark
The first vendor mobile
browser to pass ringmark
ring 1!
A web-based test suite for
capabilities that modern
web apps require.
The BlackBerry web platform
 Performance is always feature #1
 New CSS support
 File System APIs
 getUserMedia
 indexedDB
 WebGL

WebWorks Today
 “Proprietary” SDK

built on web standards, BlackBerry specific SDK

Native side

Client APIs
 SDK for each platform (BlackBerry OS, PlayBook,
BlackBerry 10)
 BlackBerry specific API signatures
Alignment with Cordova
8
Alignment with Apache Cordova
 BlackBerry 10 WebWorks built on Apache Cordova
 Ensure top level Adobe PhoneGap BlackBerry 10 support
 Leverage wider selection of frameworks, tools
 Extended with BlackBerry goodness
WebWorks SDK still exists!
 BlackBerry distribution
 All BlackBerry plugins bundled
 Supported, documented, etc.
 In time, bundle in complimentary, industry leading
frameworks/tools
 Priority on developer experience
Migrating to Cordova
General
 Apache Cordova CLI

Project creation

Plugin (API) management

Build

Target management and deployment

webworks.js cordova.js

APIs
 Apache Cordova core APIs

“Replaces” some WebWorks APIs

Many signatures almost identical
 All Existing WebWorks APIs will exist in the
Cordova world
 Will be available as Cordova plugins for PhoneGap devs

 Added by command line, not <feature> elements
Config.xml
 More is auto-populated

command line management
 No longer whitelist API per domain
 Still configure APIs with feature/param elements
DEMO
Cordova Roadmap
 Everything is a plug-in

Plugman
 More platforms
 New APIs

Notifications

Native pickers


Future focus areas
Alignment with Web Frameworks
 Continue to ensure best-in-class support

jQuery Mobile

Sencha

PhoneGap
 Work with framework providers around Cordova
 General Apache Cordova evolution

Tooling

 Focus on areas of developer experience and pain points
 Take advantage of Apache Cordova momentum
 Partner with industry “heavyweights”
 Build with a focus on Apache Cordova

 Ripple

Contributed to Apache

Another tool in the belt


APIs
 Web Platform improvements:

IndexedDB enhancements

Graphics and JS performance
 WebRTC and Web Audio on the roadmap

 Continue to build BlackBerry specific differentiators
 Built as plugins available to all Cordova devs and
downstream implementations (eg. Adobe PhoneGap)


THANK YOU
JAM32
Ken Wallis @ken_wallis
Jeffrey Heifetz
May 14-16, 2013