# Device Info to tailor table width

**URL:** <https://community.glideapps.com/t/device-info-to-tailor-table-width/62539>\
**Category:** Ask for Help\
**Created:** [June 7, 2023, 1:17pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539 "2023-06-07T13:17:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [June 7, 2023, 1:17pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539/1 "2023-06-07T13:17:30Z")

</div>

@Darren_Murphy - I use the cool tables you first suggested for lots of in-line snapshot report in Glide Classic. - Looks like this and this:

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/1/514c06df48b02426e25cfeccfd0a5c50706f0c35.png)

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/7/87b2f4594b6eaec6649066f93da0078cb2cf39df.png)

One downside is the width is fixed at 350 pixel so it displays sub-optimal on iPad/tablets (and bigger screens like computers). WIth the new device info integration can this data be used to better optimize the width? I have no experience with using device info and was wondering if you have given it a go and have some advice.

Regards - Matt

---

<div class="post-metadata">

**Author:** ![Structure\_Art\_DIGITA](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/structure_art_digita/32/59811_2.png) [@Structure\_Art\_DIGITA](https://community.glideapps.com/u/Structure_Art_DIGITA)\
**Post date:** [June 7, 2023, 1:20pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539/2 "2023-06-07T13:20:47Z")

</div>

convert to %

---

<div class="post-metadata">

**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:** [June 7, 2023, 1:20pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539/3 "2023-06-07T13:20:56Z")

</div>

Rather than a fixed width, why not use a percentage?  
Then it will auto adjust to all screen sizes.

---

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [June 7, 2023, 1:33pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539/4 "2023-06-07T13:33:16Z")

</div>

Just saying I copied the exact example you suggested about 9 months ago blindly and with minimal understanding…98% seems to do the trick!

Life doesn’t have to be complicated!

---

<div class="post-metadata">

**Author:** ![Structure\_Art\_DIGITA](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/structure_art_digita/32/59811_2.png) [@Structure\_Art\_DIGITA](https://community.glideapps.com/u/Structure_Art_DIGITA)\
**Post date:** [June 7, 2023, 1:34pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539/5 "2023-06-07T13:34:18Z")

</div>

98 on fixed… 100 on absolute 😉

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [June 8, 2023, 1:34pm UTC](https://community.glideapps.com/t/device-info-to-tailor-table-width/62539/6 "2023-06-08T13:34:19Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
