# Default width of number field shouldn't be full width

**URL:** <https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352>\
**Category:** Feature Requests\
**Created:** [January 4, 2023, 10:44pm UTC](https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352 "2023-01-04T22:44:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![blairrorani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blairrorani/32/43426_2.png) [@blairrorani](https://community.glideapps.com/u/blairrorani)\
**Post date:** [January 4, 2023, 10:44pm UTC](https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352/1 "2023-01-04T22:44:44Z")

</div>

![Screen Shot 2023-01-05 at 9.39.29 am](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/e/fe44d81a8aa770abb104936622b56133b2012215.png)

**Problem**  
The maximum size of a number in Glide is the number + any decimal places.  
The default width of a number field seems to be full width.  
However, anything wider than a phone-sized device and the increment up/down controls are really far away from the number you’re incrementing.

**Suggested solution**  
If not on phone-sized device, then make max width = enough room for say 1,000,000.000, or something more common sense, not full width.

(There is a similar UX issue with toggle switches, the field label is on the left and the toggle control is waaaay on the right, even on mobile devices this looks weird.)

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [January 4, 2023, 11:39pm UTC](https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352/2 "2023-01-04T23:39:30Z")

</div>

if this is App… use CSS to make the size that you want… If Pages, put in the 4 columns container, it will make it 4 times shorter.

---

<div class="post-metadata">

**Author:** ![blairrorani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blairrorani/32/43426_2.png) [@blairrorani](https://community.glideapps.com/u/blairrorani)\
**Post date:** [January 4, 2023, 11:57pm UTC](https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352/3 "2023-01-04T23:57:44Z")

</div>

**What if the field is in a form though?**  
You can’t add a container within a form container 😢

Rather than hacking around poorly designed defaults, my suggestion is to redesign the feature.

For example, Tally uses common sense field widths in their form builder.  
 ![Screen Shot 2023-01-05 at 10.56.39 am](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/e/6eeb7600eeb6b2763352ac98712000f02155eada.png)

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [January 5, 2023, 12:06am UTC](https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352/4 "2023-01-05T00:06:03Z")

</div>

yes, but they won’t do it… so your only solution… is your own creativity 😉  
Check my **[Code BOOK](https://code-book-desktop.glideapp.io/)**, I have a code for that there… look for 3 elements in a row.

---

<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:** [January 5, 2023, 2:02am UTC](https://community.glideapps.com/t/default-width-of-number-field-shouldnt-be-full-width/56352/5 "2023-01-05T02:02:38Z")

</div>

> [@blairrorani](#):
>
> However, anything wider than a phone-sized device and the increment up/down controls are really far away from the number you’re incrementing.

Agreed. It looks stupid. I almost never use full width forms in Pages for exactly this reason.