First, BREW is an abbreviation representative of wireless application downloads. From the developer's perspective, you can describe the BREW platform of Qualcomm:
1. An API function set that makes the developer can create applications for wireless devices (now wireless phones);
2. It is also a means to sell and hand it over to end users.
In terms of the phone, BREW is a customer (approximately 150K) in the two levels of application software and dedicated integrated circuits. Therefore, the developer can write to BREW without knowing or careing the device chip or an air interface. Moreover, BREW can operate on devices using other air interfaces.
Figure 1 shows the idea level of software applied to wireless devices:
The second important part of BREW is the BREW Distribution System (BDS). BDS covers the end user's ability to purchase, pay, download, and install software on a wireless carrier's network.
The BREW store allows users to browse operators' programs to download servers, let them know which applications can be purchased or tried. The entire transaction process is air happening. Operators generate a bill record for each transaction, and display the corresponding required payment on the monthly phone bill.
Operators retain any retail differences at the same time and Qualcomm share the 20% of the application of the application, and the remaining 80% return of developers.
Development BREW application
BREW applications can be developed with Java, C or C . At the 2002 BREGO in San Diego, IBM and Insignia showed the Java virtual machine in the BREW environment. HP also turned its Microchaivm platform to BREW. IBM will provide a BREW development plugin in WebSphere Studio Device Developer products.
Note SDK has three versions: 1.0, 1.1 and 2.0. Each SDK version has a supporting application execution environment (AEE) on the phone. Use the application written by the 1.0 version of the SDK to run on a phone with a later version AEE. This reverse support is not necessarily pair, because each subsequent version is integrated into new features.
Since the BREW upgrade is unlikely to provide the existing phone, if you want to maximize your target market, keeping the compatibility with the 1.0 version is wise.
Although SDK is free, developers must have Microsoft Visual C 6.0 or their subsequent versions to develop and test the BREW simulator provided by SDK. That simulator is a Windows program that is able to simulate aee on the phone. The application is running in the simulator in the form of Windows .dll. During the entire development process, the simulator is a good tool for learning API functions and test applications. It is necessary to warn in advance that there is a considerable difference between the analog environment and the real phone environment. Developers should introduce real hardware and architectural environments as early as possible in the development process to avoid cumbersome debugging work.
When a developer decides to take jump and start commercial development, different phases throughout the project will definitely produce some other costs. First, in order to obtain access to the basic tools required for the development of real hardware, the developer must be authenticated. Simply put, developer certification includes $ 400 to pay for the VeriSign Authentic Document Digital ID, thus having a 1 year validity period of the payment date or a number of numbers of 100 applications, or arbitrarily.
Certification gives the developer's access to the BREW developer's internal network, through it can access or download some important tools. For example, BREW CLASSID Generator ensures that a unique 32-bit ID is given for each application. BREW TESTSIG Generator provides a digital signature to allow developers to test applications in real hardware. In addition, BREW Apploader downloads the app to the phone.
In addition to certification, there are some other costs. The CPU used in the BREW phone is ARM7TDMI. Since C and C applications should be run on such devices, there is also an ARM compiler. Qualcomm now supports ARM BREW Builder ($ 1,500), ARM Developer Suite (ADS) 1.0.1, ADS1.1, may have ADS1.2. Suppose ADS1.2 needs to lock the node to the node to spend $ 5,500, spend $ 6,500 for mobile license, the $ 1,500 price sign on the Brew Builder is like a trading stealing! A free, 45-day ADS1.2 trial version has been launched. Developers also need a BREW phone to test applications. There are currently only two commercial models: Sharp Z800 ($ 399.99, Verizon Wireless) and Kyocera QCP3035E (price unknown, but definitely lower than Z800). Note that these two calls are equipped with a 1.0 version of the AEE, so the applications developed to them must use the 1.0 version of SDK. The three new phones have version 1.1 AEE and CDMA 1x air interfaces, will be launched in September 2002 as planned. The price is now inappropriate. Equipped 2.0 version of AEE is expected to be launched at the end of 2002 or in 2003.
As shown in Table 1, the TRUE BREW certification test of NSTL organization represents another cost that may require the developer's cost. An application must be certified by True Brew before being used by operators for the network. The purpose of the certification is to ensure that the operator's network is from viruses and harmful or unstable procedures.
Table 1 Application test fee
Privileges RequiredStandardExpeditedBasic API functionality, file and shared directory access. $ 750.00 $ 950.00Above & data calls or Above & telephony / SMS (TAPI) .1,500.001,900.00Above & data calls & TAPI & position location.2,500.003,200.00Functional testing required by some Carriers, Add: 400.00400.00
Get profit
Once the developer passed True Brew certification, it is necessary to negotiate a pricing plan with the operator through Qualcomm Maintenance. This plan involves some resolutions, including both the overall sales price of each download also has a license type of end users.
Developers can choose to sell applications to end users, or provide a free DEMO with a monthly manner. For example, the developer must think long-term consideration: the license is based on the number of specified number (unlimited is a choice), the expiration date, specifies the number of days, or actually uses the time. The DEMO option includes 1-5 times, 1-10 minutes use time long, and 1-24 hours that have fallen in the mobile phone.
Once developers and operators agree on the pricing plan, operators can provide users with new applications, just add it to the BREW store directory accessible via mobile phone.
in conclusion
Chip irrelevant, integrated distribution and checkout characteristics, and operators' direct participation to make BREW different compared to other wireless development platforms. BREW picked up most of the APIs discarded - it provides a large road to profits without the need for developers to cross the "operator barriers".
Author
Murray Bonner is the general manager of Golden Creek Software Co., Ltd. The company focuses on wireless software development, which is currently prepared for a BREW application to be prepared by TRUE BREW certification.
