Developing Hybrid applications
Posted on June 24th, 2016
When it comes to mobile, native vs hybrid vs web is among the most common debates. The trade offs are not very complicated.
Native means you have to re-implement similar features across at least 2 platforms but likely a couple more. It also tends to mean you have some sort of shared back-end anyway that doesn't have any user interface but still provides a bunch of common APIs to persist and share data across platforms. It often requires 2 or more teams to handle all the multiple specific platform changes and peculiarities but it often provides a more natural and better experience for the users.
Web only tends to the easiest and quickest to achieve. HTML, CSS and JS are now decently standardized enough that the many mobile browsers around can handle a good chunk of what you need to generate a page that looks very similar across platforms. Those also tend to include the backend and the sharing. One platform for all. Obviously the look and feel won't quite match the user's usual platform but, then again, they likely have noticed it's only a website anyway. You also get limited when it comes to device specific hardware (camera, gyroscope, 3D accelerators, etc) and certain types of notifications.