# Button visibility - mobile vs. desktop/tablet **URL:** \ **Category:** Ask for Help\ **Created:** [August 29, 2023, 1:01pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531 "2023-08-29T13:01:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![metamads](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/metamads/32/61990_2.png) [@metamads](https://community.glideapps.com/u/metamads)\ **Post date:** [August 29, 2023, 1:01pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/1 "2023-08-29T13:01:39Z")
Hi there, We are developing an app that will be used primarily on iPhones and iPads. When navigating through the app on mobile view, there is a back button to navigate backwards. There is no back button present on desktop view. This was a major UX flaw when testing our app with users - testers could not figure out how to navigate backwards when using an iPad (desktop view). I have inserted a Button component with the action “Go Back” which allows desktop view users to navigate backwards. Now, I am met with the issue of having two back buttons when on mobile view. Perhaps this is a feature request, but I am wondering if there is a way to target component visibility for mobile vs. desktop views? Could I hide the button from mobile view using Custom CSS? We are on a Glide Business plan. Images below of the confusing UI double back button conundrum! ![Screenshot 2023-08-29 at 2.46.02 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/d/cdff20bda537245e32db44b0efeb94d4e568eef5.jpeg) ![Screenshot 2023-08-29 at 2.45.53 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/5/c521233a9b608e2bd6f73e266c6767a04dee759f.jpeg) Thanks in advance for any assistance 🙂 ---
**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\ **Post date:** [August 29, 2023, 1:11pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/2 "2023-08-29T13:11:28Z")
Get the users device information and set a viability condition based on operating system or screen width. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [August 29, 2023, 1:21pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/3 "2023-08-29T13:21:08Z")
> [@metamads](#): > > When navigating through the app on mobile view, there is a back button to navigate backwards. There is no back button present on desktop view. Have you tried adding a Breadcrumbs component at the top of the screen? ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [August 30, 2023, 12:57am UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/4 "2023-08-30T00:57:29Z")
Breadcrumbs should be good enough. It shows only on desktop. If that doesn’t work, Eric’s suggestion would be the way to go. Get the screen width and then show/hide components accordingly, I think. ---
**Author:** ![metamads](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/metamads/32/61990_2.png) [@metamads](https://community.glideapps.com/u/metamads)\ **Post date:** [September 1, 2023, 1:23pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/5 "2023-09-01T13:23:36Z")
Clicking the breadcrumbs isn’t as intuitive as one might hope for first time tablet users, but appreciate the suggestion! Curious about Eric’s suggestion…how would one get the user’s device information/screen width? Thanks all for the help! ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [September 1, 2023, 1:27pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/6 "2023-09-01T13:27:18Z")
> [@metamads](#): > > Curious about Eric’s suggestion…how would one get the user’s device information/screen width? > **[Device Info](https://www.glideapps.com/docs/automation/integrations/device-info)** > > Get information about the users device. ---
**Author:** ![metamads](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/metamads/32/61990_2.png) [@metamads](https://community.glideapps.com/u/metamads)\ **Post date:** [September 1, 2023, 1:29pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/7 "2023-09-01T13:29:09Z")
Oh brilliant, thanks Darren! ---
**Author:** ![metamads](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/metamads/32/61990_2.png) [@metamads](https://community.glideapps.com/u/metamads)\ **Post date:** [September 1, 2023, 2:11pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/8 "2023-09-01T14:11:01Z")
It seems like the Device Info is only computed once, the first time a user logs in. So, for example, when a user logs in on a tablet, then logs in on an iPhone, the Device Info for only the tablet is recorded in the Data Editor. Expected behavior or a bug? ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [September 1, 2023, 2:24pm UTC](https://community.glideapps.com/t/button-visibility-mobile-vs-desktop-tablet/65531/9 "2023-09-01T14:24:04Z")
> [@metamads](#): > > So, for example, when a user logs in on a tablet, then logs in on an iPhone, the Device Info for only the tablet is recorded in the Data Editor. No, you should get the info for whichever device they are using at the time. Can you describe how you’ve set it up, and how you got that result?