<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Navigation on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/navigation/</link>
    <description>Recent content in Navigation on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 16:51:00 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/navigation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Flutter routing inside of the Scaffold</title>
      <link>https://www.bradcypert.com/flutter-routing-inside-of-the-scaffold/</link>
      <pubDate>Tue, 11 Aug 2020 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/flutter-routing-inside-of-the-scaffold/</guid>
      <description>&lt;p&gt;If you’re coming from React Native to Flutter, one of the first things you’ll likely ask is “How do I do routing?” First, I’d ask you to consider if you actually need routing. Instead, could you just have a global state that determines which screen to show? In most cases, probably. But if you want things to feel right when building Flutter for Web (or want decent deep linking support), you’ll probably want to build your flutter app with routing.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
