@gakisstylianos Because the configuration values depended on the insets, a lot of strange edge cases show up, especially around almost square windows.

It has been possible that Configuration.orientation is portrait, but Configuration.screenWidthDp > Configuration.screenHeightDp.

It's also been possible that rotating a device would always report a landscape Configuration.orientation.

This will affect qualified resource resolution, but it should be in an overall positive way.

Size is my favorite one:

DeviceConfigurationOverride(
DeviceConfigurationOverride.ForcedSize(DpSize(1280.dp, 800.dp))
) {
MyScreen() // will be rendered in the space for 1280dp by 800dp without clipping
}

Through a bit of trickery by overriding the density, MyScreen() will be guaranteed to have 1280dp by 800dp space to render, regardless of the actual device size.

You can test layouts big and small on a single test device!

Want to test a component with an increased font scale?

DeviceConfigurationOverride(DeviceConfigurationOverride.FontScale(1.5f)) {
MyComponent()
}