Multiple Activity or Single Activity and multiple fragments

Viewed 14001

I have one very general question, I did not find a concrete answer for my question hence putting it again.

I want to decide between two approaches

  1. Dedicated activities for various various screens and tasks to avoid complexity and issues
  2. Single Activities and multiple fragments for different tasks and user can navigate like Activity holding Fragment A user will navigate to Fragment B, Fragment C , this can be back and forth transaction.

What I want to know?

  1. Is Activity transition is that costly for processor or to achieve simplicity memory overhead is negligible ?
  2. Fragment has overhead of managing life cycle with transition, so what all problem can come with this life cycler management?
  3. How easy is to deal with fragment transaction with saving state of the fragment?

We don't know right now what amount data will be there for fragment to hold.

4 Answers
Related