# How do you handle layout sizing across different devices and OS?

**URL:** https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643
**Category:** Questions about Thunkable AI
**Created:** [May 18, 2026, 8:17am UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643 "2026-05-18T08:17:52Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![cicraf](https://avatars.discourse-cdn.com/v4/letter/c/cdc98d/32.png) [@cicraf](https://community.thunkable.com/u/cicraf)
#### Post date: [May 18, 2026, 8:17am UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/1 "2026-05-18T08:17:52Z")

</div>

Hi everyone,

I’m struggling with layout sizing across different Android and iOS devices. The standard Thunkable approaches don’t seem to work reliably in production:

- **Fill/Stretch** — doesn’t work on the outermost layout container

- **Computed Height** — returns 0 in production, only works in live testing

- **Static values** — work on one device but break on others

How do you handle this? Is there a reliable approach that works consistently across different screen sizes and both iOS and Android?

Thanks

---

<div class="post-metadata">

### Author: ![brianl](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@brianl](https://community.thunkable.com/u/brianl)
#### Post date: [May 18, 2026, 5:43pm UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/2 "2026-05-18T17:43:45Z")

</div>

I would recommend using the [layout component](https://docs.thunkable.com/app-design/ui-components/basic-components/layout)

---

<div class="post-metadata">

### Author: ![at8995753damihe](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/at8995753damihe/32/225011_2.png) [@at8995753damihe](https://community.thunkable.com/u/at8995753damihe)
#### Post date: [May 24, 2026, 4:22am UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/3 "2026-05-24T04:22:27Z")

</div>

Hi everyone,

I’m struggling with layout sizing across different Android and iOS devices. The standard Thunkable approaches don’t seem to work reliably in production:

Fill/Stretch — doesn’t work on the outermost layout container

Computed Height — returns 0 in production, only works in live testing

Static values — work on one device but break on others

How do you handle this? Is there a reliable approach that works consistently across different screen sizes and both iOS and Androi

d?

Thanks

---

<div class="post-metadata">

### Author: ![at8995753damihe](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/at8995753damihe/32/225011_2.png) [@at8995753damihe](https://community.thunkable.com/u/at8995753damihe)
#### Post date: [May 24, 2026, 4:23am UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/4 "2026-05-24T04:23:11Z")

</div>

Hi everyone,

I’m struggling with layout sizing across different Android and iOS devices. The standard Thunkable approaches don’t seem to work reliably in production:

- **Fill/Stretch** — doesn’t work on the outermost layout container

- **Computed Height** — returns 0 in production, only works in live testing

- **Static values** — work on one device but break on others

How do you handle this? Is there a reliable approach that works consistently across different screen sizes and both iOS and Android?

---

<div class="post-metadata">

### Author: ![martint](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/martint/32/96689_2.png) [@martint](https://community.thunkable.com/u/martint)
#### Post date: [May 26, 2026, 2:40pm UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/5 "2026-05-26T14:40:35Z")

</div>

> [@\[Solved\] How to make Android layouts fit correctly on every device](https://community.thunkable.com/t/solved-how-to-make-android-layouts-fit-correctly-on-every-device/4108120):
>
> The Solution After a lot of testing across different Android devices, I have landed on a solution that actually works. This is a small, lightweight set of blocks that automatically calibrates your layout height so it fits the screen perfectly on any device. It runs once per device, stores the correct layout height locally, and from that point on every screen in your project just uses that stored value. No guessing, no formulas, no device checks. You can see the blocks I am using for: the f…

Use with ‘if platform is Android’ block as Ios devices seem to be ok.

---

<div class="post-metadata">

### Author: ![cicraf](https://avatars.discourse-cdn.com/v4/letter/c/cdc98d/32.png) [@cicraf](https://community.thunkable.com/u/cicraf)
#### Post date: [May 27, 2026, 8:51am UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/6 "2026-05-27T08:51:08Z")

</div>

Thanks for sharing your experience. You’ve identified the core issue — Computed Height/Width are unreliable, especially on iOS when navigating between screens.

We ended up using Thunkable’s native Resize - Stretch mode without additional calculations. It’s not perfect (especially on Android with the notch area), but it’s stable and doesn’t cause major layout issues across all devices. Accepted margins on the sides are better than chasing unreliable Computed values.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)
#### Post date: [August 16, 2026, 8:18am UTC](https://community.thunkable.com/t/how-do-you-handle-layout-sizing-across-different-devices-and-os/4108643/7 "2026-08-16T08:18:22Z")

</div>

This topic was automatically closed after 90 days. New replies are no longer allowed.
