n the old days, building mobile applications involved using the ASP.NET mobile controls which were a subset of the larger ASP.NET. ASP.NET developers had to learn new concepts (for instance,
n my last article, I showed you how to get started with the QUALCOMM BREW UI toolkit and introduced BREW’s notion of forms and widgets. In this article, you’ll build
he design of J2ME provides a flexible architecture that allows additional APIs to extend the application specifications such as MIDP and Personal Profile. One such extension is the Wireless Messaging
he Evans Wireless Development Survey is a detailed report of extensive, in-depth interviews with almost 500 developers active in wireless application or infrastructure development. It was conducted in the Fall
ast June, Qualcomm took the wraps off one of the most significant changes to Qualcomm Brew in over two years: the Brew UI Toolkit, an entirely new paradigm for Brew
n July, the Java Community Process released JSR 211, the Content Handler API (also known as CHAPI), for public review. The release counts as one of the most useful and
Short Messaging Service (SMS) services are becoming near-ubiquitous. Who among us has not used their cellphone to check the latest cricket score or to get the latest news? One very
rom the earliest days of J2ME, network connectivity has been a central focus of the design. So much so that a generic architecture, referred to as the Generic Connection Framework
s a BREW developer, you’re probably intimately familiar with the process of writing applications, but perhaps not as familiar with the process of writing extensions. In BREW, an application is