Why It’s Currently Impossible to Publish a Properly Responsive Android App in Thunkable

Hi Martin,

Thanks a lot for taking the time to dig into this and for sharing your testing and blocks. I really appreciate the effort you’ve put in here :+1:

I’ve tried a very similar approach myself and I agree with you on the core observation: the status bar is definitely interfering with layout sizing, and toggling it on/off to force a recalculation does improve things on a number of devices. On some phones, this workaround gives exactly the result you’d expect.

However, after testing across a wider range of devices, I’m still seeing cases where:

  • layouts clip on taller phones, or

  • white space appears on shorter / squatter devices,
    even with this approach in place.

So while your solution clearly works for some screen configurations (and is a really useful data point), it doesn’t fully generalize across all Android devices yet. That’s what I’m trying to get to the bottom of.

The main issue at the moment is that we don’t have enough cross-device data to say why it works on some phones and not others. That’s why I’ve put together the small test app and opened this up to the forum, so we can collect real measurements across different aspect ratios, and device classes.

This post here explains what I’m trying to do and has the download link for anyone who’s willing to help test:
https://community.thunkable.com/t/lets-fix-layouts-on-android-once-and-for-all-help-needed/4108099

Really appreciate you sharing your findings, they’ve definitely helped narrow the problem space. Hopefully with a few more test cases we can either formalize something like this properly, or at least understand its limits so people know when it will and won’t work.

Thanks again :folded_hands:

1 Like