Message of the day:
Welcome. Latest release: https://www.silverstripe.org/download Community Forum: https://forum.silverstripe.org Features: https://forum.silverstripe.org/c/feature-ideas Archive: https://slackarchive.silverstripe.org
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
Archive temporarily at https://archive.codingplayground.nl (redirect)
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.
It sounds more like "we want an app, because that's what all the cool kids did 12 years ago" kinda situation.
@vanny make a PWA
"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.
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
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.
Otherwise I would have taken my own advice.
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.
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
Progressive Web App would be another option