Our approach in mobile application

Our approach in mobile application development which combines native mobile programming and mobile web
by utilizing Web API has its own upside and downside. On the upside, mobile web technology is truly versatile and
correctly rendered across multi-platform as long as it is used for online viewing and this approach still let the
developer use any native functionality while at the same time utilizing the mobile web’s versatility. This approach
does not only let developer to get the best from the world of native mobile programming and the world of mobile
web programming but also simplifying the code base management because all of business logic is gathered in a
single code base. When multiple business unit exist in a single mobile application, each business unit can have their
own managed business logic code base. WebView approach also let the business logic developer to flexibly update
their content without having the need to update the mobile platform’s store application. On the downside, the
developer still needs to manage multiple code-base of the native side of the application which depends on how many
mobile platform they target. For application performance, this research shows that WebView application and Hybrid
application is smooth enough compared to the native mobile application, this result is in accordance with other
research which states that while web technology stack has not achieved the level of performance that can be attained
with native code, it is getting close [9]. Data consumption over a network might also become an issue especially
with an unstable mobile carrier network. The mobile application will become more prone to error when consuming
larger data over the network, and consuming data using web services is obviously more efficient rather than
consuming the whole web page. Regarding other issues, currently niche features such as saving offline web page
completely for later execution might not be directly achievable through platform’s API on some version. While it is
possible to find a roundabout way to overcome this issue, the time taken to solve such problem might cause a
setback in the project’s timeline. Although this issue might be solved externally by the platform’s developer team,
but there is no way to verify the exact date of the next update. In the end, depends on the application’s requirement it
might be sensible to trade over the small print network consumption with the development simplicity over multitude
mobile platform by using combination of native mobile programming and WebView API.