Please enable JavaScript.

Coggle requires JavaScript to display documents.

Native, Hybrid or Mobile Web Application Development - Coggle Diagram

- - - - Native apps have direct access to all a mobile device’s features including ones that are unique to the platform. These include graphics hardware, motion, location, proximity, visual and audio sensors.
    - - Native applications run with the highest performance possible. Native IDEs offer the best runtime optimizations as well
    - - The ability to directly access UI components of specific platforms means that apps can seamlessly blend with the operatingenvironment. Given that native UI layout and functionality also matches the platform, this eliminates disruption to the user experience.
- - - - Although libraries for web-based apps
        are able to access many mobile device hardware
        capabilities, this is done via abstraction layers that must necessarily take an LCD approach to these capabilities. Web-based apps are improving in this regard.
    - - Because web-based mobile apps must code through abstraction layers and execute a step removed from the actual hardware and OS, their performance can never approach that of a native app.
    - - The ability to mimic a platform’s native UI/UX features will always have a meaningful gap compared to a native app, but that gap is gradually shrinking thanks to improvements in HTML5 and JavaScript. If the app is designed to access a mobile website specifically designed to render as an app and offline execution abilities are maximized, the UI/UX distinctions blur even further.
- - - - Depending on how a hybrid mobile app is partitioned, there is no reason that it cannot approach the functionality in terms of platform feature access and on-platform device access that native apps enjoy.
    - - A hybrid app can match the performance of native apps for
        the portion of the app that runs natively, especially in offline mode.
    - - Just as for performance and functionality, the ability to create a fully functional, seamless UI/UX depends on how these characteristics are partitioned between the native and web-based portions of the app.
    - - Costs are more or less midway between those for native and web-based apps. Where the actual costs lie depends on the balance between native and web-based development efforts and the effort to merge the two.
  - - - Though the native portion enjoys high performance, the web-based portion of a hybrid mobile app suffers from the same deficiencies as any web-based application. The degree to which this reduced performance affects the app overall mainly depends on how much of the app’s web-based logic executes on the device, how much is on a server component and the network latency between the two.