# Criteria to ensure Discourse instance will work as a Chrome webapp on mobile

**URL:** <https://meta.discourse.org/t/criteria-to-ensure-discourse-instance-will-work-as-a-chrome-webapp-on-mobile/50112>\
**Category:** Product Support\
**Created:** [September 13, 2016, 10:00pm UTC](https://meta.discourse.org/t/criteria-to-ensure-discourse-instance-will-work-as-a-chrome-webapp-on-mobile/50112 "2016-09-13T22:00:34Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![auryn\_macmillan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/auryn_macmillan/32/56633_2.png) [@auryn\_macmillan](https://meta.discourse.org/u/auryn_macmillan)\
**Post date:** [September 13, 2016, 10:00pm UTC](https://meta.discourse.org/t/criteria-to-ensure-discourse-instance-will-work-as-a-chrome-webapp-on-mobile/50112/1 "2016-09-13T22:00:34Z")

</div>

I have a few of instances of Discourse running for different projects. They are pretty much identical, other than a couple of minor CSS differences, but are behaving differently when I try to use the “Add to homescreen” option on chrome for android. The majority work without a hitch (imitating a native app; splash screen, no URL bar, etc), however two instances seem to simply put a shortcut on the homescreen and open up in a new tab in chrome.

Are there any specific criteria that I might have neglected to set up in the two misbehaving that might be causing this? (I’ve tested it across a couple of devices, so I’m confident I’m not the only one experiencing it).

 ![](https://global.discourse-cdn.com/meta/original/3X/6/e/6e84a0edd22bfca9840c7f5075dc75176a93a6da.png) ![](https://global.discourse-cdn.com/meta/original/3X/3/6/36a703a7fca1a04ff1fef45d4994fc1c3993e09a.png)

---

_[View the full topic](https://meta.discourse.org/t/criteria-to-ensure-discourse-instance-will-work-as-a-chrome-webapp-on-mobile/50112)._