BlackBerry App World™ Development

[erotsppa]

We are about to start app world development for an app that relies heavily on push notifications. I have spent many hours researching on this matter and it seems RIM has not done a good job in guiding developers. Can anyone point me to the right place to get started? Here are some more details:

-The app will only be distributed through app world. 

-We want to avoid using polling and it drains the battery.

-I've seen that we want to use BIS and not BES although I am still not too sure what both of them are. 

-How much will this cost us? We have a background in iPhone development and push notifications are free from that side.

Any help is much appreciated!

[br14]

Unless you're a registered ISV, or developing for enterprises running BlackBerry Enterprise Server, you're unlikely to be able to access push services.

I suppose it's possible a carrier could allow PAP push over it's internal infrastructure.

Checkout elsewhere to see the detail of network transports - there's a great video in the video library. In brief BIS-B Push API is based on the BlackBerry Internet Service implemented with the carriers. If registered you can push data from your server to any registered device using the device PIN as the means of ID. The push I've used was effectively PAP, but I understand Web-signals is more like browser push (see next paragraph).

BES is BlackBerry Enterprise Server, a server that resides inside an organizations network and generally integrates the corporations email and other services with the BlackBerry.

Part of the BES is the Mobile Data Service . MDS listens for push connections, and supports several types of "browser" push including Message Push, Cache Push and Channel Push to push to corporate (and other) devices managed by the BES. This is a pretty cool technology that allows organizations to send web content to a device without needing to code apps on the device. They even allow offline connectivity using cache push and offline queues. (So HTTP posts can be queued pending coverage).

If you are a registered ISV then you should contact your RIM support person, alternately you can wait until RIM releases BIS-B Push API to App World developers (some time next year if the Dev Con is to be believed).

I was under the impression the iPhones push isn't really push - hence the battery drain. It a while since I researched it though so maybe things have changed.

There is documentation available on RIM's website that describes the browser push options. PAP Push (which is effectively what you'd be using if you don't have a BES) is a public API now managed by the Open Mobile Alliance. You might also want to check out web-signals.

RIM provides documentation if you're permitted to use BIS-B Push. The price depends upon the number of pushed data requests. I believe the first 15000 pushes are free (or some number of that order of magnitude). After that there's a sliding scale.

[erotsppa]

Great explanation thank you. However I am confused:

1) Yes, we will not be using BES as I have studied this further and that many users from the app world will not be provisioned for this.

2) The other route is to use BIS like you said, but I thought this is already available? From this page, you can already sign up for it as long as you are a registered ISV? http://na.blackberry.com/eng/developers/javaappdev/pushapi.jsp#tab_tab_pricing

3)Getting registered as a ISV is not going to be a problem because anyone developing for app world will already be one isn't it?

4) What is PAP? Yet another (third) option?

[br14]

BIS push is already available if you're an ISV member under the old relationship structure. The ISV Alliance Program was recently changed to include developers for App World, however, as yet BIS push is only available to those that pay for annual support. Check the following link for a detailed guide. Section 2.4 has the program details. Pricing starts at USD$2000

http://partners.blackberry.com/c/document_library/get_file?uuid=18f828cc-240a-471c-8b70-6cadd8fc5ed2...

BIS push is "Access to BlackBerry Internet Service-B Connectivity".

At the recent developer conference, RIM announced that they will be releasing BIS push for registered developers, but I believe this will not be until some time in 2010 - my guess it will be limited in some form since it would be easy to do damage if released in an uncontrolled manner.

PAP is push access protocol. It's an open standard WAP protocol that is available when using BIS push.

[erotsppa]

It gets confusing because ISV alliance program is suppose to include app world developers but yet they don't have access to BIS push?

I think first of all, I need to understand, is having a vendor account for app world the same as ISV alliance member? If they are seperate things, then I can assume that being an ISV alliance member will cost me at least 2000 per year?

In order words, don't exepct to have an app in appworld that can push without paying 2000 a year or more is the conclusion?

[br14]

"In order words, don't exepct to have an app in appworld that can push without paying 2000 a year or more is the conclusion?"

That is correct at this moment in time.

However, next year RIM plans to release push to App World developers.

App World developers are already at the lowest level of ISV, the Registered Member. Push is only available to Alliance Members and above.