I would like to share some good FAQs on BREW technology It's really helpful to understand the BREW specially for beginners:
What is BREW technology?
What is BREW technology?
BREW stands for Binary Runtime Environment for Wireless. As the term 'Binary Runtime' suggests, BREW runs on top of hardware platform and can be ported to different hardware platforms. BREW is a product of QUALCOMM Internet Services (QIS, a division of Qualcomm Wireless & Internet (QWI) group of QUALCOMM. And currently supported on all QUALCOMM handset hardware but like other application development platforms, can be ported to non-QUALCOMM Handsets. It can co-exist in a handset with any other mobile operating system. Size wise it is about 150k much smaller than most of other handset operating systems available in the market To the telecom domain guys, it is said to be air interface independent i.e. it can run on CDMA or GSM/GPRS or UMTS handsets. But again currently it is running only on CDMA handsets. And also enables native application development in C, C++. Applications can also be developed in Java using a Java Virtual Machine (JVM) developed for BREW platform. Recently, IBM has come up with a Java Virtual Machine for BREW Handset manufacturers can integrate BREW into their device by using the BREW Porting kit provided by QUALCOMM.
Explain BREW Application Development Cycle
1. Download BREW SDK used for development of applications in C/C++.
2. The SDK includes BREW Emulator. It simulates the interface and conducts of BREW device, is used to test and debug BREW applications in the course of development process.
3. Applications for BREW Emulator are compiled to native code of the operating system on which the Emulator is running
4. After thorough testing with Emulator, application must be compiled and link into ARM binary form to run on BREW handset.
5. Different from other mobile platforms, BREW applications cannot be tested directly on BREW handsets for security reasons
6. To test applications on BREW handhelds, they must be digitally signed. QUALCOMM provides special tools for generating digital signatures only to content providers and Authenticated BREW Developers
7. Upon digital signing, applications can be uploaded to a BREW handset via USB port or AppLoader tool – part of the BREW Testing and Commercialization Utilities
8. After thorough internal testing, application must be submitted QUALCOMM for TRUE BREW Testing – this testing type is also available only to BREW Authenticated developers
9. As application is approved by True BREW testing, it may go to CDMA Mobile Network providers
Merits of BREW Platform
1. Since BREW runs directly on top of hardware layer, application execution is fast as compared to other application frameworks like Java Mobile Edition.
2. BREW API is consistent across supported handsets than other application frameworks like Java Mobile Edition API
3. Since BREW from version 2.0 allows direct access to screen buffer, developers have lot of control while creating Graphics intensive applications like Games
4. Handset manufacturers can add new features and fix bugs over-the-air to already deployed BREW handsets by using BREW extensions. BREW extensions are additional code modules written by OEMs and third party software vendors to include additional functionalities in the handsets. Some Examples for BREW extensions are Java Virtual Machine, Game engines etc.
Demerits of BREW Platform
1. Unlike other handset platforms, applications cannot be directly tested on BREW handsets
2. Only BREW Authenticated Developers can test and deploy applications in handsets. Becoming a BREW Authenticated Developer involves a set of procedures which is not freely available for individuals
3. Testing and debugging of BREW applications difficult and cumbersome due to differences in emulation and actual hardware environments
Explain BREW Application Development Cycle
1. Download BREW SDK used for development of applications in C/C++.
2. The SDK includes BREW Emulator. It simulates the interface and conducts of BREW device, is used to test and debug BREW applications in the course of development process.
3. Applications for BREW Emulator are compiled to native code of the operating system on which the Emulator is running
4. After thorough testing with Emulator, application must be compiled and link into ARM binary form to run on BREW handset.
5. Different from other mobile platforms, BREW applications cannot be tested directly on BREW handsets for security reasons
6. To test applications on BREW handhelds, they must be digitally signed. QUALCOMM provides special tools for generating digital signatures only to content providers and Authenticated BREW Developers
7. Upon digital signing, applications can be uploaded to a BREW handset via USB port or AppLoader tool – part of the BREW Testing and Commercialization Utilities
8. After thorough internal testing, application must be submitted QUALCOMM for TRUE BREW Testing – this testing type is also available only to BREW Authenticated developers
9. As application is approved by True BREW testing, it may go to CDMA Mobile Network providers
Merits of BREW Platform
1. Since BREW runs directly on top of hardware layer, application execution is fast as compared to other application frameworks like Java Mobile Edition.
2. BREW API is consistent across supported handsets than other application frameworks like Java Mobile Edition API
3. Since BREW from version 2.0 allows direct access to screen buffer, developers have lot of control while creating Graphics intensive applications like Games
4. Handset manufacturers can add new features and fix bugs over-the-air to already deployed BREW handsets by using BREW extensions. BREW extensions are additional code modules written by OEMs and third party software vendors to include additional functionalities in the handsets. Some Examples for BREW extensions are Java Virtual Machine, Game engines etc.
Demerits of BREW Platform
1. Unlike other handset platforms, applications cannot be directly tested on BREW handsets
2. Only BREW Authenticated Developers can test and deploy applications in handsets. Becoming a BREW Authenticated Developer involves a set of procedures which is not freely available for individuals
3. Testing and debugging of BREW applications difficult and cumbersome due to differences in emulation and actual hardware environments
