BREW

BREW
Name	BREW
Developer	Qualcomm
Released	2001
Latest release	4.0 (example)
Programming languages	C, C++
Operating system	Proprietary RTOS
Platform	Mobile phones
License	Proprietary

BREW

BREW was a proprietary application development platform and runtime created to enable native and interpreted mobile applications on feature phones and early smartphones. It provided a device-level application binary interface and distribution channel that linked handset manufacturers, wireless carriers, and independent developers through a curated ecosystem similar in intent to later platforms like Apple Inc.'s iOS App Store and Google's Android (operating system). The platform influenced handset software strategies at companies such as Nokia, LG Electronics, Samsung, Sony Ericsson, and operators including Verizon Communications, AT&T, and Vodafone Group.

Overview

BREW functioned as both a runtime and a marketplace control point, allowing carriers like Sprint Corporation and platform vendors like Qualcomm Incorporated to vet and monetize applications. It provided APIs for telephony, messaging, multimedia, and graphics that interoperated with device components designed by manufacturers such as Motorola, HTC Corporation, and BlackBerry Limited. The model emphasized signed binaries and certification processes reminiscent of later practices at Microsoft Corporation with Windows Phone and app distribution frameworks used by Amazon (company) for its Amazon Appstore.

History and development

BREW originated at Qualcomm in the late 1990s and was formally introduced to the market in 2001 as part of efforts to commercialize third-party software on CDMA handsets and to extend value-added services for carriers such as Nextel Communications. Early commercial deployments targeted models from Kyocera Corporation, Sanyo Electric Co., and Sharp Corporation, and the platform saw rapid uptake among CDMA operators in the United States, Japan, and parts of Asia-Pacific where companies like NTT DoCoMo and KDDI influenced mobile content strategies. Over subsequent years BREW evolved through multiple SDK revisions and partnerships with middleware providers such as Openwave Systems and device vendors including Panasonic Corporation. The platform's lifecycle intersected with major industry shifts driven by the launch of Apple's iPhone (1st generation) in 2007 and the rise of Android in 2008, prompting adaptations in certification, distribution, and support policies at Qualcomm.

Architecture and features

BREW's architecture incorporated a native application runtime, an application programming interface set, and a secure application signing and provisioning framework. Core components interfaced with modem stacks developed by E-Plus, Vodafone, and other carriers and leveraged multimedia codecs from vendors such as Fraunhofer Society and MPEG LA licensors. The platform exposed APIs for audio, video, camera, file I/O, graphics acceleration, and network communications that developers accessed using C and C++ toolchains akin to those used for Symbian development. BREW implemented an application lifecycle and permissions model that paralleled concepts later formalized by Open Handset Alliance members. Security and distribution were enforced through a certification process coordinated with entities like Global Certification Forum and joined to operator billing systems operated by companies such as Cisco Systems and Verizon Wireless’s content portals.

Applications and devices

Commercial applications for BREW spanned games, multimedia players, messaging clients, and location-based services provided by content aggregators like EA (company), Sega, Namco and regional publishers including DeNA and GREE, Inc.. Devices running BREW ranged from entry-level handsets by Alcatel-Lucent and ZTE Corporation to higher-end models from Samsung Electronics, LG, and Sony Mobile Communications. In many markets, major titles and utility apps were monetized through carrier billing accounts maintained by Telefónica, Deutsche Telekom, and Orange S.A.. The platform also supported embedded OEM apps and operator-customized user interfaces comparable to initiatives by HTC and Motorola Mobility to differentiate hardware through software.

Developer ecosystem and tools

Qualcomm distributed BREW Software Development Kits (SDKs) that integrated with toolchains from vendors like Microsoft Visual Studio and build environments using compilers from GCC-derived toolsets. The SDKs included emulators, debugging tools, and API documentation, and Qualcomm operated developer programs with certification workflows and revenue-sharing arrangements similar to those later adopted by platform owners such as Apple and Google. Independent developer resources and forums were sustained by third-party training organizations, regional incubation programs backed by investors such as SoftBank Group, and code examples published by companies including Accenture and IBM. Commercial middleware providers and analytics vendors like Flurry and Nielsen monitored BREW application performance and distribution metrics for publishers and carriers.

Criticism and legacy

BREW faced criticism for its closed nature, operator-controlled distribution, and certification overhead, which developers compared unfavorably with the more open models promoted by Android and web-based platforms advocated by W3C. Analysts at firms such as Gartner, Inc. and IDC cited fragmentation, licensing costs, and the shift of consumer demand toward touchscreen ecosystems as contributors to BREW's decline. Nonetheless, the platform's emphasis on secure application signing, carrier billing integration, and close coordination among chipset makers, handset OEMs, and operators left a legacy that influenced later mobile platform policies and app store governance seen at Apple, Google, and Microsoft. Elements of BREW's provisioning, monetization, and certification practices persist in modern mobile distribution channels and in specialized embedded application environments used by industries served by companies like Bosch and Siemens AG.

Category:Mobile software