FAQs - General BREW FAQs

1. How does BREW solve the issue of developing applications and services for wireless handsets?
2. What do I need to create a BREW application from beginning to end?
3. How do I get the BREW SDK®?
4. How do I make money writing BREW applications?
5. What other costs must I incur to develop for the BREW platform?
6. How do I get my application on a particular handset or adopted by a particular operator?
7. How long does it take to write an application for BREW?
8. What programming languages does the BREW platform support?
9. Which wireless networks will BREW work with?
10. If I have problems with BREW, where can I go for help?
11. Now that my application is in the operator catalog, how can I monitor usage?
12. How can I get my device test enabled, re-flashed, or my software upgraded?

1. Q: How does BREW solve the issue of developing applications and services for wireless handsets?
A: The BREW platform is a standard environment for applications development for wireless handsets - from inexpensive, mass-market phones to high-end multi-purpose wireless devices. The platform lets you write applications that can be used on a wide variety of phones, without requiring modification of the app for each new phone model. BREW eliminates current programming challenges such as not having internal knowledge of the phone and its software.

2. Q: What do I need to create a BREW application from beginning to end?
A: You will need the BREW Software Development Kit (SDK), a Windows® development environment and an ARM compiler (ARM has created the RealView™ Compilation Tools for BREW, available to BREW developers for $1,500, specifically to support BREW.) You will also need to plan for TRUE BREW® compatibility testing for your applications. Some operators require BREW applications to pass TRUE BREW testing before being made available to wireless subscribers. Applications that pass this testing will receive a digital signature from Qualcomm. Handsets will use this signature for authentication purposes before permitting an application to be downloaded or run.

3. Q: How do I get the BREW SDK?
A: Just click here and download it.

4. Q: How do I make money writing BREW applications?
A: After your app. is TRUE BREW tested (if required by operator), Qualcomm will post it on the BREW operator extranet with your term sheet. Once you've agreed to terms with operators, they will offer your application to their subscribers on their BREW application download server. As consumers adopt your applications, you will be paid according to the terms you agreed to with each operator. Qualcomm is putting middleware in place linked to operator networks to manage apps. distribution and payment back to you. The developer extranet you have access to as a BREW developer allows you to track operator and, ultimately, end user adoption of your software.

5. Q: What other costs must I incur to develop for the BREW platform?
A: The BREW Software Development Kit (SDK) is available to developers at no charge. Qualcomm will also provide free web-based developer support. You will be responsible for acquiring your own development tools, including the RealView™ Compilation Tools for BREW.

6. Q: How do I get my application on a particular handset or adopted by a particular operator?
A: Qualcomm will ensure that operators and manufacturers have access to all applications that have passed compatibility testing and are TRUE BREW tested. We would encourage you to also market your applications to operators and manufacturers.

7. Q: How long does it take to write an application for BREW?
A: It depends on the complexity of the application. Many applications could be completed in one to two months. Very simple applications could be written in weeks. BREW makes writing applications easier because it provides a standard and familiar environment for today's Windows, Palm and other mass-market developers. BREW also eliminates difficult integration issues that have added months to implementation schedules in the past.

8. Q: What programming languages does the BREW platform support?
A: BREW is intended to be neutral about development languages. Native C and C++ applications will run most efficiently. While there are currently certain limitations on the use of C++, we're working to remove these. BREW will also support integration of Java applications, provided a Java Virtual Machine is available on the device, browsers (WAP, CHTML, etc.) and other environments.

9. Q: Which wireless networks will BREW work with?
A: To see which operators have launched BREW services, please check the Operator Directory.

10. Q: If I have problems with BREW, where can I go for help?
A: In addition to this FAQ and the documents in the BREW SDK, you can find more in-depth Knowledge Base articles at https://brewx.qualcomm.com/brew/sdk/download.jsp?page=appseng/en/knowledgebase. If you don't find the answer you're looking for in the SDK documents, this FAQ, or the Knowledge Base, and if you are registered as a BREW Developer, you can email Qualcomm's developer support team.

11. Q: Now that my application is in the operator catalog, how can I monitor usage?
A: 1. Go to http://notarization.verisign.com/pta from the machine that has your Qualcomm Authentic Document ID on it. The service will ask you to authenticate yourself based on your Authentic Document ID or Qualcomm Digital Notarization Certificate. Select this certificate and continue.

12. Q: How can I get my device test enabled, re-flashed, or my software upgraded?
A: BREW developers may request test-enabling and software upgrades of devices via the BREW Customer Support Portal website which allows you to track the status of your Service Request, review responses and provide follow-up information. For detailed information on the BREW Customer Support Portal, please log into the BREW Developer Extranet, click on Document tab and choose the BREW Customer Support Portal from the list of documents.

1. Access the BREW Customer Support Portal at http://qishelp.qualcomm.com or from the Technical Support link under Support & Services tab on the Developer Extranet.

   Complete a Service Request by clicking on the Submit a Service Request folder.
   • Select product
   • Select Issue Category
   • Quick Summary click
   • Select Service Type click
   • Boxes with red star ** requires entry

   When you reach the Successful Submission page, print out the Service Request by clicking on More Details on the Detailed Summary Tab.

2. Ship your devices to:
   Qualcomm
   QIS Device Support Center, R-220L
   6455 Lusk Blvd
   San Diego, CA 92121
3. Please include the following with your package for more efficient processing of your request.
   1. Printed copy of Service Request-IMPORTANT!!
   2. Phone battery fully charged
   3. Label device with company name
   4. Return shipping address, contact name, phone number and email address.
4. Please ship device and battery only. Do not include charger, data cable or box, we are not responsible for lost items. Please note that new phones do not always have fully charged batteries right out of the box.
5. Turn-around time is at least ten (10) business days from the day your package is received.
6. If you want to know if Qualcomm received your package, please track it with your shipping provider (FedEx, UPS, etc.) using their tracking number.
7. If ten (10) business days have passed and you have not received your device, please contact the QIS Phone Center at 858-845-3489 for the status of your request.

back to top