Java Reference
In-Depth Information
With this signature may come additional privileges, such as access to location-based
APIs. Negotiating operator partnerships can be an expensive and time-consuming task,
but without the help of an intermediate aggregator, you need to perform these negotia-
tions for each operator's network on which you want to deliver your application.
This issue of privileges and cryptographic signatures isn't just a business issue, but
can be a functional issue as well. This may very well affect the functional requirements
for your application; for example, Acme Wireless (a fictitious operator) might only permit
applications access to location-based interfaces for applications it signs and distributes.
If your application needs positioning data (say, to locate the user to recommend restau-
rants or services), that requirement won't be just a technical requirement but a business
requirement to establish the necessary operator relationship to ensure the required privi-
lege. This admittedly adds risk to your business model, because it's difficult to ascertain
in advance whether or not specific operators will carry your application, and obtaining
this information in advance can involve significant business investment. It does, how-
ever, give you certain assurances if you can bridge the gap and obtain operator signing
and distribution for your application, because this gives significant placement and mar-
keting clout for your application. While all of these comments apply primarily to Java ME
MIDP applications, due to the large number of MIDP applications and MIDP-capable
devices on the market, I suspect that the landscape for Java CDC applications will be sim-
ilar, given the rampant success of the MIDP distribution model.
Of course, if you're a developer involved in planning your business strategy, don't for-
get other avenues for distribution, too. Direct-to-manufacturer deals, while difficult to
obtain, are potentially lucrative sources of long-term revenue. Moreover, providing serv-
ices for Java consulting remains an important mainstay for many developers. Thinking
creatively, a host of business models can support your application's development and
distribution.
Wrapping Up
Java ME meets needs for operators, device manufacturers, and consumers. By providing
a rich set of platforms across devices from low-end mobile phones to high-end set-top
boxes, and from embedded devices to high-end PDAs, Java ME enables software develop-
ers like you to leverage your skills to bring new applications to market.
The Java ME platform is divided up into configurations, platforms, and profiles. Two
configurations are presently available: the CLDC, which is targeted for constrained
devices, and the CDC, which is targeted for more robust devices. Atop these configura-
tions are one or more profiles, such as MIDP for the CLDC, or the Foundation, Personal
Basis, and Personal Profiles for the CDC. These provide additional APIs in a standard way
that let you write your application for a family of devices. Finally, packages allow Sun and
third parties to extend the APIs on a device or suite of devices in a standard way, giving
access to new functionality in portable ways.
 
Search WWH ::




Custom Search