Become a BREW Developer/Authentication

To become a commercial BREW Developer you must be authenticated. The process contains four parts:

Applying for the Authentic Document ID for BREW.
Completing the BREW ISV registration form and reviewing and accepting the BREW Developer Agreement.
Registering with the BREW 3rd Party Test House, National Software Testing Laboratory (NSTL).
Reviewing Operator Guidelines.

Once authenticated, developers receive all the benefits of the BREW Alliance Program. Registered members of the developer company will receive a user name and password providing access to a variety of BREW Developer benefits and tools located in a password-protected section of the brew.qualcomm.com web site, known as the BREW Developer Extranet.

To apply for a VeriSign Authentic Document Digital ID and become an authenticated BREW Developer, a developer needs to follow these four steps:

Step One: Applying for the VeriSign Authentic Document Digital ID

A: Complete the on-line VeriSign application located at the following URL:
http://www.verisign.com/products-services/security-services/code-signing/brew-document-ids/index.html. An email will be sent containing the order number and confirming the request for an Authentic Document Digital ID.

The following bundles are available for purchase:
Digitally notarize 100 applications for $400
Digitally notarize 500 applications for $895
Digitally notarize 1000 applications for $1295

The purpose for this bundle of notarizations is to protect your BREW application by digitally signing your code using the BREW AppSigner tool. The BREW AppSigner tool provides a seamless interface to VeriSign's Authentic Document Service and is accessible from the BREW Developer Extranet.

B: VeriSign will go through its developer company verification process (this takes on average five business days). Upon approval, an email will be sent to the developer verifying their approval.

C: Once the developer company has been approved, the technical contact identified on the developer company's VeriSign application, will receive an email with instructions to pick up and install the Authentic Document Digital ID.

D: Qualcomm will send an email to the business contact identified on the developers company's VeriSign application shortly after VeriSign notification of the approved Authentic Document Digital ID. The email will provide the developer company's business contact with a temporary user name, password and URL specifically set up to access the BREW Developer Agreement.

Step Two: Completing the BREW ISV registration form and reviewing and accepting the BREW Developer Agreement

A: The developer company's business contact then links to the following URL:
https://brewx.qualcomm.com/signup/index.jsp?return=companysignup.jsp and signs in with their temporary user name and password. Upon login they complete the ISV registration form, register the developer company's BREW Developer Extranet users with individual levels of security access, and review and sign the BREW Developer Agreement by clicking "I accept."

B: Qualcomm sends an individual email to each member of the developer company designated to gain access to the BREW Developer Extranet. This email will contain a user name, password and URL enabling login to the BREW Developer Extranet based on their individual security levels.

Step Three: Registering with the BREW 3rd Party Test House (NSTL)

Once you have completed the BREW Developer agreement, have received your permanent username (typically your email address) and initially logged into the BREW Developer Extranet, you must register with NSTL. Please allow one business day from the time you log on to the Developer Extranet to the time you register at NSTL.

Go to the following URL: https://www.nstl.com/brew/

Step Four: Reviewing Operator Guidelines

A. Most BREW Operators require developers to sign the operator's Developer agreement prior to accepting BREW applications on their commercial catalogs. It is highly recommended that you review each operator's guidelines and contact the designated business contact or web site to ensure you have fulfilled the operator's legal agreement requirements. Access to specific operator guidelines require authentication.