Title: About Apps detect
Last modified: August 30, 2016

---

# About Apps detect

 *  [thedepi](https://wordpress.org/support/users/thedepi/)
 * (@thedepi)
 * [11 years ago](https://wordpress.org/support/topic/about-apps-detect/)
 * Hi,
 * when it detects a mobile device, can it detects if a page is loaded in an App
   or in a Browser window?
    Thanks
 * [https://wordpress.org/plugins/mobble/](https://wordpress.org/plugins/mobble/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Scott (@scottsweb)](https://wordpress.org/support/users/scottsweb/)
 * (@scottsweb)
 * [11 years ago](https://wordpress.org/support/topic/about-apps-detect/#post-6411435)
 * That depends on how the app browser identifies itself. mobble simply inspects
   the user agent ([http://whatsmyuseragent.com/WhatsAUserAgent](http://whatsmyuseragent.com/WhatsAUserAgent)).
   If there are clear differences in the app useragent then yes it can be detected.
 * Visit: [http://demo.mobiledetect.net/](http://demo.mobiledetect.net/) from both
   browsers and make a note of the user agent string, see if there are any obvious
   differences. If there are then we might be able to use some hidden features of
   mobile detect (upon which mobble is based) to create some code that works.

Viewing 1 replies (of 1 total)

The topic ‘About Apps detect’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/mobble_f5f5f5.svg)
 * [mobble](https://wordpress.org/plugins/mobble/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mobble/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mobble/)
 * [Active Topics](https://wordpress.org/support/plugin/mobble/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mobble/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mobble/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Scott (@scottsweb)](https://wordpress.org/support/users/scottsweb/)
 * Last activity: [11 years ago](https://wordpress.org/support/topic/about-apps-detect/#post-6411435)
 * Status: not resolved