Optimize Overview
For as long as developers have been building applications for mobile devices, they have been contending with the challenges of device differentiation. This issue has become even more important as the number of devices has grown and the promise of "write once, run anywhere" has become harder to realize.
However, device manufacturers are not creating different devices just to make developers' lives more difficult. Each unique device targets a different market niche - a combination of form, functionality, and price - which expands the total addressable market for mobile applications. And within the Nokia portfolio, device differentiation does not mean market fragmentation, but instead the expansion of the Platforms.
The Develop/Optimize Process
Nokia recommends building applications starting with the key technology enabler (such as Symbian C++or Java MIDP), which you will have selected based on the application's requirements, your expertise, preferences, and the desired market.
Next, you can target specific Platforms and develop your applications against the Platform specifications
The next step is to optimize the applications for the different UIs on a given Platform (such as screen size and keymapping) and then accommodate any device-specific hardware limitations or issues, such as file size limitations or processor speeds.
You can also add functionality for specific devices that have lead software that adds capabilities to the base software of the Platform.
Here are some of Nokia's resources to help progammers understand the Platforms:
The Platform Advantage
Nokia currently offers three Platforms:
* Series 40 Platform
The mass-market platform for Java™ applications.
* Series 60 Platform
The No. 1 smartphone, available from six different manufacturers.
* Series 80 Platform
Designed for business productivity applications.
Nokia's platform approach provides a common software implementation across a range of Nokia devices. This consistency minimizes the differences between devices at a functional level, although there are some differences based on hardware and UI implementations that developers must address.
The key to leveraging the Platforms and minimizing device-specific development when building mobile applications is to stay as abstract as possible for as long as possible. By separating the business and application logic from the UI and taking device-agnostic programming into account from the outset, support of multiple devices - and even multiple Platforms - becomes significantly easier.
By starting in the abstract and gradually narrowing your focus, your application will be much more portable and device variation will have minimal impact. This is in stark contrast to developing your application for a specific device and then later trying to retrofit it to other devices, which often requires rewriting significant portions of code that may be tied to a particular device implementation.
For as long as developers have been building applications for mobile devices, they have been contending with the challenges of device differentiation. This issue has become even more important as the number of devices has grown and the promise of "write once, run anywhere" has become harder to realize.
However, device manufacturers are not creating different devices just to make developers' lives more difficult. Each unique device targets a different market niche - a combination of form, functionality, and price - which expands the total addressable market for mobile applications. And within the Nokia portfolio, device differentiation does not mean market fragmentation, but instead the expansion of the Platforms.
The Develop/Optimize Process
Nokia recommends building applications starting with the key technology enabler (such as Symbian C++or Java MIDP), which you will have selected based on the application's requirements, your expertise, preferences, and the desired market.
Next, you can target specific Platforms and develop your applications against the Platform specifications
The next step is to optimize the applications for the different UIs on a given Platform (such as screen size and keymapping) and then accommodate any device-specific hardware limitations or issues, such as file size limitations or processor speeds.
You can also add functionality for specific devices that have lead software that adds capabilities to the base software of the Platform.
Here are some of Nokia's resources to help progammers understand the Platforms:
The Platform Advantage
Nokia currently offers three Platforms:
* Series 40 Platform
The mass-market platform for Java™ applications.
* Series 60 Platform
The No. 1 smartphone, available from six different manufacturers.
* Series 80 Platform
Designed for business productivity applications.
Nokia's platform approach provides a common software implementation across a range of Nokia devices. This consistency minimizes the differences between devices at a functional level, although there are some differences based on hardware and UI implementations that developers must address.
The key to leveraging the Platforms and minimizing device-specific development when building mobile applications is to stay as abstract as possible for as long as possible. By separating the business and application logic from the UI and taking device-agnostic programming into account from the outset, support of multiple devices - and even multiple Platforms - becomes significantly easier.
By starting in the abstract and gradually narrowing your focus, your application will be much more portable and device variation will have minimal impact. This is in stark contrast to developing your application for a specific device and then later trying to retrofit it to other devices, which often requires rewriting significant portions of code that may be tied to a particular device implementation.
0 comments:
Post a Comment