I have a background as an iOS developer and I am currently porting an app from iOS to Android using Xamarin. In this regards, I have some question regarding the view hierarchi on Android.

The attached UML diagram shows a subset of the interaction between fragments for the app. I want my view controller classes to have limited responsibility, encapsulating the functionality in a neat and clear way by nesting fragments (equivalent to container view controllers on iOS).

However, I was told by an Android developer, that nesting fragments is bad due to a severe performance degradation. I don't care about a small performance degradation, but the app should of course be responsive. We're only targeting newer tablets and phones.

Should nesting of fragments be avoided on Android? And what is the performance degradation, if any? (~1 ms for the example given here: <http://developer.android.com/training/improving-layouts/optimizing-layout.html>)

Thanks!
[![enter image description here](https://i.stack.imgur.com/mmfey.png)](https://i.stack.imgur.com/mmfey.png)

*Update*: The layout of the app is shown below. The functionality inside the ModelControllerFragment is rather complicated, since 2D/3D models are loaded and model manipulations can be done (in full screen) and the flow from ImageEditFlowActivity is used from several places in the app. The CommentListFragment also has some non-default behavior. Having all this functionality inside one fragment is not desirable.
[![enter image description here](https://i.stack.imgur.com/jPA18.png)](https://i.stack.imgur.com/jPA18.png)