<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Navigation on Ash Davies</title>
    <link>https://ashdavies.dev/tags/navigation/</link>
    <description>Recent content in Navigation on Ash Davies</description>
    <generator>Hugo -- 0.150.1</generator>
    <language>en</language>
    <lastBuildDate>Fri, 01 Nov 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ashdavies.dev/tags/navigation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Navigation in a Multiplatform World: Choosing the Right Framework for your App</title>
      <link>https://ashdavies.dev/talks/navigation-in-a-multiplatform-world-london-droidcon/</link>
      <pubDate>Fri, 01 Nov 2024 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/navigation-in-a-multiplatform-world-london-droidcon/</guid>
      <description>&lt;p&gt;Navigation in mobile, desktop, and web applications is such a fundamental part of how we structure our architecture. In order to both obtain functional clarity, and abstraction from platform level implementation.&lt;/p&gt;
&lt;p&gt;For a long time, there have been options available specific to each platform, and even options part of the platform framework itself. Though it can be difficult to find the right option for platform-agnostic code, ensuring consistency. Some go one step further, providing an opinionated guide on how to architecture your application.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Navigation in a Multiplatform World: Choosing the Right Framework for your App</title>
      <link>https://ashdavies.dev/talks/navigation-in-a-multiplatform-world-new-york-droidcon/</link>
      <pubDate>Thu, 19 Sep 2024 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/navigation-in-a-multiplatform-world-new-york-droidcon/</guid>
      <description>&lt;p&gt;Navigation in mobile, desktop, and web applications is such a fundamental part of how we structure our architecture. In order to both obtain functional clarity, and abstraction from platform level implementation.&lt;/p&gt;
&lt;p&gt;For a long time, there have been options available specific to each platform, and even options part of the platform framework itself. Though it can be difficult to find the right option for platform-agnostic code, ensuring consistency. Some go one step further, providing an opinionated guide on how to architecture your application.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Navigation and the Single Activity: Learnings from a Skeptic</title>
      <link>https://ashdavies.dev/talks/navigation-and-the-single-activity-droidcon/</link>
      <pubDate>Thu, 11 Jun 2020 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/navigation-and-the-single-activity-droidcon/</guid>
      <description>&lt;p&gt;Fragments have often been controversial, and to some, the stuff of nightmares, with the inconsistency of lifecycle events, complex UI interaction, and unexpected behaviours making many Android developers suspicious of their usage.&lt;/p&gt;
&lt;p&gt;But with the development and recent stable publication of the navigation library, it may be the right time to give them a chance. Giving Fragments a second chance is not something I’d ever thought I’d be saying, but it’s a fantastic opportunity to find a solution to sharing data across a single screen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Navigation and the Single Activity: Learnings from a Skeptic</title>
      <link>https://ashdavies.dev/talks/navigation-and-the-single-activity-coimbra/</link>
      <pubDate>Sat, 16 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/navigation-and-the-single-activity-coimbra/</guid>
      <description>&lt;p&gt;Fragments have often been the controversial, and to some, the stuff of nightmares, with the inconsistency of lifecycle events, complex UI interaction, and unexpected behaviours making many Android developers suspicious of their usage.&lt;/p&gt;
&lt;p&gt;But with the development and recent stable publication of the navigation library, it may be the right time to give them a chance. Giving Fragments a second chance is not something I’d ever thought I’d be saying, but it’s a fantastic opportunity to find a solution to sharing data across a single screen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Navigation and the Single Activity: Learnings from a Skeptic</title>
      <link>https://ashdavies.dev/talks/navigation-and-the-single-activity-lisbon/</link>
      <pubDate>Mon, 09 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/navigation-and-the-single-activity-lisbon/</guid>
      <description>&lt;p&gt;Fragments have often been the controversial, and to some, the stuff of nightmares, with the inconsistency of lifecycle events, complex UI interaction, and unexpected behaviours making many Android developers suspicious of their usage.&lt;/p&gt;
&lt;p&gt;But with the development and recent stable publication of the navigation library, it may be the right time to give them a chance. Giving Fragments a second chance is not something I’d ever thought I’d be saying, but it’s a fantastic opportunity to find a solution to sharing data across a single screen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Navigation and the Single Activity: Learnings from a Skeptic</title>
      <link>https://ashdavies.dev/talks/navigation-and-the-single-activity-berlin/</link>
      <pubDate>Tue, 02 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/navigation-and-the-single-activity-berlin/</guid>
      <description>&lt;p&gt;Fragments have often been controversial, and to some, the stuff of nightmares, with the inconsistency of lifecycle events, complex UI interaction, and unexpected behaviours making many Android developers suspicious of their usage.&lt;/p&gt;
&lt;p&gt;But with the development and recent stable publication of the navigation library, it may be the right time to give them a chance. Giving Fragments a second chance is not something I’d ever thought I’d be saying, but it’s a fantastic opportunity to find a solution to sharing data across a single screen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Android Jetpack: Navigation Component</title>
      <link>https://ashdavies.dev/talks/android-jetpack-berlin/</link>
      <pubDate>Tue, 07 May 2019 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/android-jetpack-berlin/</guid>
      <description>&lt;p&gt;A brief overview of the Navigation Component presented at Google IO Extended at the Google office in Berlin.&lt;/p&gt;
&lt;hr&gt;
&lt;script async class=&#34;speakerdeck-embed&#34; data-id=&#34;5105f7285d2147f3ba0902a42d476a7a&#34; data-ratio=&#34;1.77777777777778&#34; src=&#34;//speakerdeck.com/assets/embed.js&#34;&gt;&lt;/script&gt;</description>
    </item>
  </channel>
</rss>
