# Designing for Different Devices (Touch & Hover)

**URL:** https://meta.discourse.org/t/designing-for-different-devices-touch-hover/367810
**Category:** Developer Guides
**Created:** [May 27, 2025, 6:17pm UTC](https://meta.discourse.org/t/designing-for-different-devices-touch-hover/367810 "2025-05-27T18:17:05Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [October 17, 2025, 12:56pm UTC](https://meta.discourse.org/t/designing-for-different-devices-touch-hover/367810/8 "2025-10-17T12:56:29Z")

</div>

The general recommendation is: don’t do that. Why should those kind of experiences differ based on the size of the screen?

A useful thought experiment is: how do you expect it to behave on folding phones or tablets, which don’t explicitly fit into the mobile/desktop buckets.

If you really do want this kind of behaviour change to be based on the user-agent of the browser (as the old mobile/desktop modes worked), then we have `capabilities.isMobileDevice`, which quite literally checks for the word “mobile” in the user-agent string:

> <https://github.com/discourse/discourse/blob/e65395cce490c9a7ecd974ca9c8803a38f26c3cc/app/assets/javascripts/discourse/app/services/capabilities.js#L105C3-L110C4>

---

_[View the full topic](https://meta.discourse.org/t/designing-for-different-devices-touch-hover/367810)._