Indeed. Especially if you want to piss off potensial users/customers.
> There's a difference between asking a question, making a suggestion and shoving ideals down somebody's throat.
Unfortunately, the "ideal" for many is to have an app for their - well - app, or service, whatever it might be. Usually it's just a perfectly functioning responsive web service that is turned to a native app instead of just going for a hybrid app (at least to start with).
In this specific case, there's is _absolutely no reason_ it should be provided as an app, at least not a native one.
Because:
The user already has everything installed on his phone to use the service; a browser.
To me, _as a (potential) user_, having to install this app would have been showing something down my throat. To solve that problem, the developer could have created it as a responsive web application first, and maybe made an hybrid app, and then decided if it is worthwhile creating a native app.
Why the desparate need to create native apps and have to maintain two totally different projects when there's no need to?
Then why make an app out of something that would work just as well with something I have already installed on my phone?
In this case it's very easy: if all the functionality can be run in the browser, which already is an app installed on my computer, don't make it an app. At least not a native one.
I said: don't _create_ apps that shouldn't be apps.