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

Questions about Thunkable AI
1

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

2

I would recommend using the layout component

3

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

4

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?

5

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

6

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.