I've read on how adding
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="mobile-web-app-capable" content="yes">
to your HTML will allow users to add that page to their home screen and use it as an App. So I'm wondering whether it would make sense to add these meta tags to pretty much all the HTML I generate. After all, the user doesn't have to install them as apps, but if they choose to do so, why should I prevent that?
I'm mostly thinking about unauthenticated content here which is static from a HTML server perspective, although it may well be interctive thanks to client-side JavaScript. To give you an idea, think about single-page tutorials, perhaps with some interactive code demo in it. Something like that.
Chrome on Android now supports a meta-tag mobile-web-app-capable : Since Chrome M31, you can set up your web app to have an application shortcut icon added to a device's homescreen, and have the app launch in full-screen "app mode" using Chrome for Android's "Add to homescreen" menu item.
apple-mobile-web-app-capableSets whether a web application runs in full-screen mode. If content is set to yes , the web application runs in full-screen mode; otherwise, it does not. The default behavior is to use Safari to display web content.
Our general advice is, unless your idea relies on a native mobile app, start with a web app and add the mobile apps further down the line. A web app can often give your users everything they need from your product, on both desktop and mobile devices, without the additional resources required to build mobile apps.
The major difference between a mobile app and a mobile website is that the mobile website is accessed by the user via the Internet (therefore requires being online) and the downloadable application is a separate app installed on the phone and can be accessed both online as well as offline.
The only "promise" that you are making by using those tags is that your website can be used navigated without the browser buttons. Most websites don't have dedicated "back" buttons, and users would end up hitting dead ends.
You do suggest that a basic portion of the site can be run without an internet connection, otherwise, why bother? There should be some reason to add it to your homescreen over simply using bookmarks. You should avoid using these tags when there is no clear benefit to the user over a regular bookmark.
With your example, tutorials could be pretty cool as a app-like shortcut, especially if all of the content is cached and users can access it instantly, without an internet connection. However, you should consider that your users might want to reference multiple tutorials while they are working. Filling your users' homescreens up with icons for one-page "apps" that they need to switch between would be less convenient than just using browser tabs.
If you can add features that improve the "multiple browser tabs" scenario, that would be the ideal way to use the mobile-web-app-capable
tag. Try making an app that combines multiple related tutorials together, and simple searching through the content in the front-end.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With