Commentary

Qualcomm Wants To Foster Better Relationships Between Hardware OEMs And Developers

While Qualcomm is not exactly trying to be a matchmaker like your Aunt Tilly, it hopes the new BREW Client 4-Series developer tools will help hardware manufacturers and developers work together better. The end goal? Cooler stuff for mobile phones that is easier to make and costs less.

While Qualcomm is not exactly trying to be a matchmaker like your Aunt Tilly, it hopes the new BREW Client 4-Series developer tools will help hardware manufacturers and developers work together better. The end goal? Cooler stuff for mobile phones that is easier to make and costs less.The new client architecture was announced this morning in San Diego at Qualcomm's annual BREW conference and is all about better visibility. The new platform lets OEMs expose hardware and software layers to their developer partners and gives developers content-framework support that allows for improved discovery, delivery and installation of content. In other words, creating content for BREW-enabled phones just got a whole lot easier.

Developers were clearly excited about it. "BREW Client 4-Series will lay the groundwork for compelling new phone features that we can pass on to the end-user in the form of a dynamic entertainment experience," said Travis Boatman, vice president of worldwide studios at EA Mobile.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Bob Briggs, senior vice president and general manager, BREW for Qualcomm Internet Services, believes that harmony begets better BREW apps. "By creating more opportunities for meaningful collaboration among critical members of the wireless value chain, Qualcomm's ultimate goal is to deliver new and compelling applications to the wireless end user."

There's nothing wrong with trying to spread a little love. Collaboration, after all, often leads to good things. In this case, 'good things' means richer content for BREW phones.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links