You do not need to develop using fragments, but if you want to provide the maximum number of consumers / devices with the best possible environment, you should switch to fragments. However, if you really think fragments are the work of the devil, you can only stick to action-based development and provide a sloppy user interface.
Regarding Google’s feelings, I think this sums it up -
Embedded actions through an ActivityGroup were a good idea, but it was always difficult to cope with them, since the Activity is intended for an independent stand-alone component, and not for interacting with other actions. The Fragment API is much better suited for this and should be seen as a replacement for inline actions.
For more information on using fragments, check out here and for most of the design philosophy, check out this post .
MrEngineer13
source share