Choosing a React Navigation Navigator: Stack, Tabs, or Drawer
Match your navigator to your app's information architecture: stack for hierarchical flows, bottom tabs for three to five top-level sections, and drawer for secondary screens.
Loading…
ReadMeFeed / Community knowledge
#mobile-navigation
Real questions. Useful conversations. Find the people who know your stack.
reactnavigationExpo Router Makes the File System Your Single Route Table
Expo Router turns files under app/ into routes and URLs, removing duplicate deep-link configuration. See how layouts and dynamic segments work across iOS, Android, and web.
Simplifying Mobile Navigation with Xamarin.Forms Shell
Stop fighting with NavigationPage and TabbedPage. Learn how Xamarin.Forms Shell uses declarative XAML and URI-based routing to simplify mobile app navigation.
dotnet
xamarinOffline Navigation with Mapbox Vector Tiles: Minimal Architecture for Mobile Apps
Design a minimal, secure architecture for offline Mapbox vector tile navigation: requirements, tile server, local cache, sync logic, trust boundaries, operational checks, failure modes, and when to redesign.
mapboxPassing Data Between Screens in React Navigation Without Shooting Yourself in the Foot
React Navigation route params are stored in navigation state, so what you pass matters. Learn why passing IDs instead of objects keeps deep links, state restoration, and TypeScript working for you.
Use Xamarin.Forms Shell routes for predictable navigation and deep linking
Replace nested NavigationPages with Xamarin.Forms Shell routes for predictable back navigation and deep linking. This guide shows a working AppShell configuration, route registration, and GoToAsync usage with limits and common mistakes.
Picking native-stack in React Navigation—and Building a Typed Setup Around It
Native-stack moves React Navigation transitions off the JS thread and onto platform primitives. Here's how to decide if it's right for your app, and how to build a typed, maintainable navigation setup around it.