<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fabien Devos</title>
    <description>http://twitter.com/Fabien_devos</description>
    <link>https://speakerdeck.com/fabiendevos</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/fabiendevos.rss"/>
    <lastBuildDate>2016-12-14 18:52:31 -0500</lastBuildDate>
    <item>
      <title>Modern Android - How to ditch Activities &amp; Fragments</title>
      <description>Activities get destroyed when you rotate the screen and have a complex lifecycle. Using Fragments is error-prone and their lifecycle is even worse. 

How would you like a screen that doesn't get destroyed on rotation, and a navigation as simple as calling goTo(screen)? That's what modern Android development should look like.</description>
      <media:content url="https://files.speakerdeck.com/presentations/f1dfd38d525647ed9a2872b2d4d29b7a/preview_slide_0.jpg?7361185" type="image/jpeg" medium="image"/>
      <content:encoded>Activities get destroyed when you rotate the screen and have a complex lifecycle. Using Fragments is error-prone and their lifecycle is even worse. 

How would you like a screen that doesn't get destroyed on rotation, and a navigation as simple as calling goTo(screen)? That's what modern Android development should look like.</content:encoded>
      <pubDate>Tue, 13 Dec 2016 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/fabiendevos/modern-android-how-to-ditch-activities-and-fragments</link>
      <guid>https://speakerdeck.com/fabiendevos/modern-android-how-to-ditch-activities-and-fragments</guid>
    </item>
  </channel>
</rss>
