Describe the bug
The UI of the launcher screen looks distorted in landscape mode.
Steps to reproduce the behavior:
Screenshots


Environment
Would like to work on this.
Maybe you can move text to one side and image to another and check how it looks. You may cross check with material guidelines how it should be done. You should describe your solution while creating an issue.
@abdulwd
There are two options:
Option1
A separate XML for landscape mode.
Option2
Another option is to change margin and spaces between them but I don't think it is recommended. I tried doing this and here is how it looks like.
Screen1

Screen2

Please let me know your opinion.
@sonusourav How about moving the Get Started button on the right side with a separator?
@iadeelzafar So, are you suggesting option 1 in some way that I have to create a new XML for landscape mode. But would that look good moving to the button to the right?
@abdulwd If I change just the spaces and positon in this XML only, then may be it will be different in different mobiles. Is it fine to make a new XML for landscape with the same design but proper space and position for the landscape mode?
Button and some text on one side with a separator for the image on the other. @abdulwd can suggest better.
Using a RelativeLayout for these erroneous layouts should work for uniformity in the landscape view too. The main content of the page could be designed as a Relative Layout with layout_below attributes to make sure there is no overlapping. And this RelativeLayout could in turn be a child of the parent layout with centerVertical and centerHorizontal attributes as true.
We're using constraint layout which is more powerful than relative layout. @sonusourav You should use a separate layout for the landscape keeping image on left and text on right. Do have a look at material guidelines to check how they should be positioned in landscape mode.
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.
@abdulwd @siddharth2010 MIght that be that this problem has been fixed in 3.0? I can not reproduce it?
Please reopen if not
It seems to work fine on my end as well..