08-12-2009 10:56 AM
We would like to begin planning for the 5.0 browser launch and have many questions. Hopefully Tneil or others can help...
1. Has a release date been announced yet?
2. What devices will come with it standard?
3. What previous devices will be able to upgrade to it?
4. What will the upgrade process be?
5. Will a minimum OS level be required?
6. What device APIs will be accessible?
a. Blackberry GPS (lat/long reading)?
b. Blackberry Maps (location mapping, directions?
c. Blackberry Address Book (read from & write to)?
d. Blackberry Calendar (read from & write to)?
e. Blackberry Email (write to, with custom subject, body, and attachments).
7. Will an announcement be made on the Blackberry Developer's Blog site when available?
8. Is it too late to get in on the Beta?
Thanks for any and all info you can provide. This will really help us plan for future development activity.
Solved! Go to Solution.
08-12-2009 12:26 PM
FYI, this presentation from WES answered some of my questions around specific APIs:
08-13-2009 10:06 AM
Lots of questions... let me see what I can do to provide some answers. Lots of the questions are around 5.0 and supported devices so I can't really comment on those until RIM makes that information public. To be clear.. any new API's are in BlackBerry widgets and not in the general browser.
Too many to mention in this post We are hoping to get some of the API docs uploaded soon
08-13-2009 02:38 PM
Thanks Tneil. We'll try to be patient!
The details about how widgets will be run completely seperate from the browser was important to understand.
I am struggling to understand the value of widgets though. It would seem that the value of developing Web Apps for mobile devices is the "write once, deploy to many platforms" idea. However, with the widget approach I will have to write a platform specific Web Apps for Blackberry devices (that are later transformed into a widget) and another version of the same web app (without the Blackberry API calls) for other mobile devices. How can I use the widget technology but still write one Web App for all mobile devices?
This may need a separate thread!
08-14-2009 10:58 PM
The concepts behind our BlackBerry widgets are about building two main scenarios:
It really opens up a variety of new possibilities for unique applications that have not been possible before.
For any write once run anywhere functionality, you absolutely need to stick to standards oriented functionality. And we realize that and support that in our standards based browser. What we are doing with widgets is adding to this standards based browser by extending it in a BlackBerry widget. Leaving the browser to be standards oriented, and extending functionality only in a targetted BlackBerry widget.
You can write a BlackBerry widget that pulls in all your resources from you web server (as long as your domains are listed in a whitelist). In a BlackBerry widget you can specify your own custom header that is passed down on every web request so that you know the request for the content is coming from your widget. You can then have your server based web content react to this heeader and add functionality to the markup specific to the BlackBerry. It would be the same type of approach if you wanted to provide one website but target certain specific browser capabilities that are available in browser A and not in browser B.
Clear as Mudd?