|
Diaspark's technical team develops the mobile-application/game following"Write once, Run anywhere" paradigm. Still as various handsets are not identical in terms of their capabilities, architecture and specification, making them compatible for the target devices becomes necessary. |
|
| The basic consideration that we address while porting are |
|
|
 |
Balancing the heap memory |
| |
|
|
Storage parameters |
| |
|
|
Screen size and color depth considerations |
| |
|
|
Network specifications |
| |
|
|
Device specific API Extensions |
| |
|
|
Device Specific VM Bugs |
| |
|
|
|
| Diaspark takes following approach for porting. |
|
|
|
Researching the target device from the application's perspective. This involves referring our device management system as well. |
| |
|
|
Optimizing the application in order to fit the properties of the new device. |
| |
|
|
Taking a sound decision on the devices, upon which porting will not involve much of the effort or realignment of the application. |
| |
|
|
Processing the graphics to deal with various screen sizes and colors of the handsets, using our proprietary logic to fit to as many devices as possible in one go. |
| |
|
|
After all the above steps, we modify the source code. We check the source code on the emulator with device specific APIs provided by the manufacturer. |
| |
|
|
Testing of the application on actual target device with the production version firmware. |
| |
|
|
| |
| |
|
