I’ve really enjoyed this book and working along with the sample apps. I was surprised to not find any debate within this forum about the scope of fragment usage throughout your examples. I can definitely see the advantage of managing views with fragments if there is the potential to combine views on larger display devices ( i.e. the master detail pattern). Beyond that , I think it may be a tough sell to convince my organization to adopt this pattern for every view. For example consider a login screen that may vertically stack user and password fields in portrait orientation, and horizontally in landscape. Or consider a more complex layout requiring many layout.xml files across various screen densities ( all containing relatively the same content). Are you suggesting that fragments should be used in these scenarios and if so is the implication that there would be a reduction of redundant layout xml files?