title: Activity embedding vs Fragments, when to use each one?
body: <p>Until now, <code>fragments</code> were the recommended solution for having one screen inside another main screen, for example for list-detail pattern.</p>
  <p>Now google has released Activity embedding: <a href="https://developer.android.com/guide/topics/large-screens/activity-embedding" rel="nofollow noreferrer">https://developer.android.com/guide/topics/large-screens/activity-embedding</a></p>
  <blockquote>
  <p>With Activity embedding APIs you can take advantage of the extra
  display area on large screens by showing multiple activities at once,
  such as for the List-Detail pattern, and it requires little or no
  refactoring of your app.</p>
  </blockquote>
  <p>Is Activity embedding replacing <code>fragments</code>? or will <code>fragments</code> be a better solution for some cases? If so, for which cases will be better each solution?</p>