nightjarnz

if your app offers no benefit over the website, you have no value in an app. You're just making people install things for no reason, other than you (person who decided this) thought it'd be cool. Sometimes there's some wild idea that "so they can open my site with as few taps as possible" but really, it's a website. No one is that desparate to visit it.

nightjarnz

It sounds more like "we want an app, because that's what all the cool kids did 12 years ago" kinda situation.

👍 (1)
SilentDesigns

"It is becuase, my users want to feel like it is an app not a website." <-- Users or client? Sometimes an exercise in education is a better approach, but of course you cannot always convince them.

vanny

Also the target market, would find it easier to download something from the app store that just takes them to what is needed, rather than have to "remember" a website and add a shortcode to their phone

vanny

It is becuase, my users want to feel like it is an app not a website. Sometimes the terms make them feel more confident in the technology.

SilentDesigns

The reason I did it was because we needed to have a full screen, skinned experience on a specific piece of hardware, which was proving impossible to achieve in a browser.

null

But yeah, I agree. Loading a website into Webview tends to create a poor experience. It's basically another browser to support that's difficult to test

null

Progressive Web App would be another option

👍 (1)