05-26-2010 06:55 PM
05-26-2010 09:15 PM
For integrating with specific smartphone platforms you really have to leverage the APIs provided by that platform. In my opinion, a write once deploy everywhere solution is every developers dream but the only way I ever see this happening is if there ends up only ever being one mobile OS
There are too many players in the game to make this come true. But using web standards makes this porting effort much easier.
There are many efforts out there to create a higher level abstraction of APIs and packaging such as PhoneGap, JIL, W3C widgets, BONDI and the list goes on. In many of these scenarios they are standards based and pick a lowest common denominator and each one has their own desires. This approach works for some applications, but we feel that the stickiest most used applications are those that are deeply integrated with the BlackBerry experience. We have been calling this deep integration concept Super Apps. Typically higher level abstraction frameworks or lowest common denominators do not address this type of deep platform integration.
As far as Web vs Java it really comes down to what you are comfortable with and where your development background lies. If you are a web developer then pursue building a BlackBerry Widget. If you are a Java developer then pursue building a BlackBerry Java application.
We have really been trying to gear the Widget functionality towards web developers. There are many conversations around functionality with our internal Java developers that just don't jive in the web world. This is simply because things are done differently and we want to really stick to what our web developers know and are comfortable with. Our goal is that we don't want our Widget developers to even have to think about Java. We want them to concentrate on what they know best... Web technologies
So when you think about functionality it is hard to go on a apples-to-apples comparison between the two because they accomplish the same desired end result in different ways.
Hopefully that helps and doesn't further confuse the topic
05-27-2010 10:49 AM
I'm imagining that the choice of which technologies to use for your BB dev has a lot to do w/ how familiar the programmer is w/ either the web tech's or Java dev.
My question would then be, how well does each technology integrate w/ the Blackberry Enterprise Server ?
I'm in the process of selecting a technology to write an app that will interface w/ some internal systems and wanted to get some imput as far as people's experiences when writing apps for business use, specifically if the app will need to do a lot of say database 'seach and reterieval of information'
05-27-2010 11:11 AM
Integrating in a BlackBerry Enterprise Server environment is the same for both a Widget and a Java application.
Both have access to the same internal resources and both would typically be interacting via HTTP requests.
Searching and displaying results is actually easier with a web solution as your server can serve up the actual UI to be displayed on the device, where Java must parse an XML response and dynamically generate the UI.