Develop Reference

Is there compulsion of using `FrameLayout` for loading fragments?

I have seen that most of the people use FrameLayout for loading Fragments.My question is Why FrameLayout ? and why not the others like LinearLayout,RelativeLayout or ConstraintLayout.Most of the answers on StackOverflow says FrameLayout is designed to block out an area on the screen to display a single item. But the others can also block the whole screen if the its height and width set to match_parent.What is the difference ?Why most of the people choose FrameLayout if others can do the same job ?
Thanks in advanceCheers

You can use anything (LinearLayout, RelativeLayout or ConstraintLayout).
FrameLayout is just the most basic ViewGroup that provides the least functionality. It is ideal to use if you only need to hold a single child - in this case, a fragment.

FrameLayout To load child one above another, like cards inside a frame, we can place one above another or anywhere inside the frame.
Designed to display a stack of child View controls. Multiple view controls can be added to this layout. This can be used to show multiple controls within the same screen space.
LinearLayout Designed to display child View controls in a single row or column. This is a very handy layout method for creating forms.
RelativeLayout Designed to display child View controls in relation to each other. For instance, you can set a control to be positioned “above” or “below” or “to the left of” or “to the right of” another control, referred to by its unique identifier. You can also align child View controls relative to the parent edges.
For more information, please check this
https://developer.android.com/guide/topics/ui/declaring-layout#CommonLayouts
I hope it's helpful to you!

I'm not so much good at programming but I can give you some reasons.
First, have a look at official docs.
In order to replace one fragment with another, the activity's layout includes an empty FrameLayout that acts as the fragment container. https://developer.android.com/training/basics/fragments/fragment-ui#AddAtRuntime
This means for switching between multiple fragments we have to use FrameLayout. Why Framelayout then? Another look at the official docs.
FrameLayout is designed to block out an area on the screen to display a single item. Generally, FrameLayout should be used to hold a single child view, because it can be difficult to organize child views in a way that's scalable to different screen sizes without the children overlapping each other. You can, however, add multiple children to a FrameLayout and control their position within the FrameLayout by assigning gravity to each child, using the android:layout_gravity attribute.
https://developer.android.com/reference/android/widget/FrameLayout.html
It can block out an area of the screen to display a single item. Other layouts could do the same thing too. So Frame?
Because FrameLayout has one characteristic that other layouts don't have.
FrameLayout can hold its child one above another, like a deck of cards. In a deck of cards, one card is placed above other.
FrameLayout does the same job. When you use FrameLayout as a fragment container it holds the child fragment one above other as your code wants. Then it shows one and left others behind it, you switch back to other fragments then it comes above and others go behind again.
That's all I know.

Use of Frame Layout in a project

there are many question about "FrameLayout". But i need the exact use of this different from LinearLayout, RelativeLayout. And in a project when we have to use this?

FrameLayout is designed to block out an area on the screen to display a single item. Generally, FrameLayout should be used to hold a single child view, because it can be difficult to organize child views in a way that's scalable to different screen sizes without the children overlapping each other. You can, however, add multiple children to a FrameLayout and control their position within the FrameLayout by assigning gravity to each child, using the android:layout_gravity attribute.
LinearLayout arranges elements side by side either horizontally or vertically(rows vs columns).
RelativeLayout is a layout manager that helps you arrange your UI elements based on some rule. You can specify thisngs like: align this to parents left edge, place this to the left/right of this elements etc.
Check these links
http://logc.at/2011/10/18/when-to-use-linearlayout-vs-relativelayout/
http://developer.android.com/reference/android/widget/FrameLayout.html

RelativeLayout: Many options if elements are GONE

Isn't there a way to tell declaratively an element, position relative to many elements - if one is GONE then use the other? Of course if all elements are not GONE take only one (e.g. the first one).

A very simple solution is to use a LinearLayout inside of your RelativeLayout. So you can place elements inside the LinearLayout which then align to the previous element in the LinearLayout - either horizontally or vertically.
The framework itself does not support the feature to position an element relative to the visibility of many other elements.

The only thing I see even remotely related to that is android:layout_alignWithParentIfMissing and that says:
If set to true, the parent will be used as the anchor when the
anchor cannot be be found for layout_toLeftOf, layout_toRightOf,
etc. [boolean]
So I believe to get the functionality you want you would have to code it in yourself.

which layout should be used for this example

Which Android layout would be best suited for this example. Inside each box would be a picture. I am mainly wondering what would be the best parent layout for the entire screen.
I was probably going to use TableLayout for each of the rows of boxes. Then have each column in the TableLayout be a FrameLayout. Then have each FrameLayout contain the picture.
But i am not sure what parent Layout i should use to contain the entire screen.
I would like this to be able to fit in Landscape on the majority of the phones on the market. Maybe it resizes everything to fit those screens in landscape.
I would also like there to be spacing between those TableLayouts.
Any assistance is greatly appreciated.
Thanks.

If I were building that, and the number of images/boxes in each set was static, I would probably use RelativeLayout as the parent and LinearLayout for each of the "rows." Then just use ImageView directly as children of the LinearLayout. RelativeLayout allows you to position things relative to each other or the parent.

Either RelativeLayout or GridView whichever fulfills the exact requirement.

Android Layouts, Table, Relative and Linear, i am confused in their differences

I have read many articles regarding layout, but I am still quitely confused. My questions are:
When to use relative layout? Example?
When to use table layout and why we can't use it instead of relative layout?
When to use linear layout?
I just need brief answers.

When use which layout?
I think It depends on your UI, and most important thing that how you create optimized layout.
From definition : -
LinearLayout – designed to display child View controls in a single row or column. This is a very handy layout method for creating forms.
RelativeLayout – designed to display child View controls in relation to each other. For instance, you can set a control to be positioned “above” or “below” or “to the left of” or “to the right of” another control, referred to by its unique identifier. You can also align child View controls relative to the parent edges.
TableLayout – designed to organize child View controls into rows and columns. Individual View controls are added within each row of the table using a TableRow layout View (which is basically a horizontally oriented LinearLayout) for each row of the table.
References :
Creating Efficient Layouts
Common Layout Objects
And most important Hierarchy Viewer

at first there is some confusion about these layouts but as you start playing with these three layouts u will get idea where to use what.. I worked on relative-layout the most.
Consider i want to use a widget always at bottom of screen then with table or linear layout this is not possible always.. without feeling screen other two can not make item at bottom but relative can do.use of any type of layout depends on your screen requirements.

I started out using relativelayout. But recently I've switched to using mostly linearlayout.
The reason is kind of hard to explain, but take this as an example: Say I want a layout that has two images centered in the middle of the screen. Both images should take up 1/4 of the screen width and 1/4 of the screen height. This is impossible to do with relativelayout assuming you want it to work exactly the same on all devices. But you can do this with Linearlayout. By creating vertical and horizontal parents, you can create "boxes". To accomplish this you must learn about weigthsum and weigth. Parent layouts should have the weigthsum attribute and children should have the weight attribute.
Anyway, my point: Relativelayout is easy to use but it's also deceptive. You may think that your layout will look exactly alike on all device, but most likely, they won't look alike. The reason for this is:
With relativelayout you must define size with either dp or px(assuming you don't fill parent or wrap content).
Different devices have different aspect ratios.
I hoped that helped in terms of understanding relative and linearlayout.