Hi everyone! I have a question: Which is the best way to manage with compose all the variation that ...

# compose

[Cacato86]

Hi everyone! I have a question:
Which is the best way to manage with compose all the variation that I can have in one screen? I mean, how to manage portrait - landscape / mobiles - tablet
The typical example with List-Detail (Navigation on phone, same screen in Tablet)

[Olivier Patry]

I went for smoothing like that during the first compose challenge.
https://github.com/opatry/android-dev-challenge-compose-week1/blob/438b33ced24fc0512264490b7d22adef74c4853d/app/src/main/java/net/opatry/adoptacat/MainActivity.kt#L82

[Olivier Patry]

⚠️ this was my very first compose app so I guess there are a lot of mistakes 😉

That being said, the rough idea is here I think.
I think you should rely on LocalXxx API instead of bool resources using Android resource qualifier and/or maybe withConstaints

[Ryan Simon]

This is something I'm tackling on a project that supports tablet, phone and foldables. My solution was to use a sealed class to hold the different UI modes my app can be in and like Olivier mentioned, add the mode to a CompositionLocal

[Ryan Simon]