# Fully support Android Chrome's "Add to Homescreen"

**URL:** <https://meta.discourse.org/t/fully-support-android-chromes-add-to-homescreen/21067>\
**Category:** Feature\
**Created:** [13. Oktober 2014 um 05:25 UTC](https://meta.discourse.org/t/fully-support-android-chromes-add-to-homescreen/21067 "2014-10-13T05:25:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**Post date:** [12. Januar 2016 um 12:49 UTC](https://meta.discourse.org/t/fully-support-android-chromes-add-to-homescreen/21067/8 "2016-01-12T12:49:30Z")

</div>

> [@tgxworld](#):
>
> … still missing quite a number of features that chrome supports.

Perhaps better worded as “still missing couple of features that chrome **requires**.”

Whilst the `manifest.json` and the `meta` tag are part of what is required there is still a [matter of following](https://developers.google.com/web/updates/2015/03/increasing-engagement-with-app-install-banners-in-chrome-for-android) before the “add to homescreen” will be seen:

- Site must be delivered over HTTPS (hopefully [Let’s Encrypt support](https://meta.discourse.org/t/support-for-lets-encrypt/22308) will get this one for everybody).
- Must have a service worker registered on your site (I didn’t spot one in Discourse’s code).
- The user has visited your site twice over two separate days during the course of two weeks.

(this list might change in the future).

**EDIT:**

Although I don’t see the service worker requirement on this page:  
[https://developer.chrome.com/multidevice/android/installtohomescreen](https://developer.chrome.com/multidevice/android/installtohomescreen)

But there is a mention of AppCache.

---

_[View the full topic](https://meta.discourse.org/t/fully-support-android-chromes-add-to-homescreen/21067)._