Is it recommended to create all applications using fragments?

In modern Android development, is it recommended to completely switch to development fragmentation?

How to create applications for mobile phones and tablets using fragments, and not make distinctions between applications exclusively for activity and activity + fragments?

Is there an official recommendation by the Google Android Team to completely switch to "fragments" or not to completely move?

+2
android android-fragments
source share
1 answer

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 .

+3
source share

All Articles