Popular posts

I have no experience in Native app development but i would like to point out that instead of building a native app you can also use the same app to be deployed for a mobile or tablet by converting the app to a Progressive Web App. In this you would have to create a service worker which will be installed on the target device, which is much like a bookmark but will be along with an Icon and would feel like an app. So it is essentially the web app being served to the user making it feel like a native Andriod app. You can read more about them in the below mentioned links.

developers.google.com/web/progressive-web-apps developers.google.com/web/fundamentals/codelabs/y…

Also to get a feel of what i am saying try and visit trivago website on your phone, then it will ask you to install on your phone. This is will install the service worker on your phone and then you can use trivago just as you would if it would be an app.

I like the service worker approach but I don't feel convinced with the idea of app in the browser you have lesser capabilities. And that's why I added Native Solution because, to leverage the device capabilities, Native is the way to go.

As it is Dashboard app, and I am not sure about the scale of data being managed, I would consider data like 1000+ rows of complex touples at a time. And in that scenario, Native will give the optimum performance.

Hybrid have a bit of advantage as they are just the WebView, not browser itself. So you can store and cache the things more persistently.

In Service Worker, it is exact browser; so it will be limited and with large amount of Data, Mobile Browsers are famous for throttling the JS thread.

For Small amount of Data and simple Dashboard, Service Worker is really good idea.