Mobile porting has been gaining it’s momentum with time and the increasing use of different applications over all mobile platforms. There has been number of applications launched every single minute and therefore it’s not feasible to develop the same application for different categories of handsets on the same platform. This is when mobile porting comes in handy. This reduces the overall cost and the time for having a particular application on multiple handsets for the same platform.
There are few things which help us to determine how we can have an application ported to multiple handsets. An application initially developed on a single handset is called build and the numbers of builds are decided depending on the list of handsets we have to target. The targeted handsets are then categorized based on their screen sizes and the handset features. Porting is generally done through two strategic ways. One is family porting and the other is on device porting. In the family porting, list of handsets with similar screen sizes and features are put in a single family and another family is formed with another list of handsets with their features in common. This way we determine the number of builds for mobile porting, as one build is considered for one family. In the other way of porting for on-device porting, there is no family formed and each handset to be ported is considered a single build and in this case each handset are with different screen sizes and features.
This is a general overview of an idea followed in mobile porting. I hope the concept of mobile porting is clear from this perspective. Please feel free to contact if you have any questions on the above information provided on mobile porting strategies.
RSS