Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>First, for best practices in "Android" UI, see <a href="http://developer.android.com/design" rel="nofollow noreferrer">http://developer.android.com/design</a>. But I would not recommend this site for a complete beginner. Take some time to get acquainted with basic Android development first, so that you will have the perspective to understand what the <a href="http://developer.android.com/design" rel="nofollow noreferrer">Design</a> pages are talking about. Build and run some of the sample apps, and read some of the lessons at <a href="http://developer.android.com/training" rel="nofollow noreferrer">http://developer.android.com/training</a>.</p> <p>Now that I've covered the basics: Are you really sure you want to implement the UI that you have illustrated above, even if it goes against Android UI recommendations? If so, you are signing up for extra work.</p> <p>Android already provides an <a href="http://developer.android.com/guide/topics/ui/actionbar.html" rel="nofollow noreferrer">ActionBar</a> at the top of the display. If you really want your menu on the side or bottom, then you will have to reinvent what it does yourself. If that's still your plan, then I recommend using a <a href="http://developer.android.com/reference/android/widget/LinearLayout.html" rel="nofollow noreferrer">LinearLayout</a>.</p> <p>For your broader layout, I agree with <a href="https://stackoverflow.com/users/427763/prolink007">prolink007</a>: Your Menu1, View1, and View2 should probably be implemented in 3 Fragments. You can use LinearLayout again as a container to hold your Fragments.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload