Routes define the complete navigation structure of your application, whether it is a Progressive Web App (PWA) or a Native Mobile App. They are the essential map that determines which screen, or Layout, a user sees when they navigate to a specific path.

The Role of Routes

• Structure Navigation: Every accessible screen in your application must have a corresponding Route.
• Pathing: They map a user-friendly path (like /products/detail/:productId) to a Layout created in the Shipcode editor.
• Centralized Control: All route configurations—including the main Home Route (/) and the default Fallback Route (404 screen)—are centrally managed in Project Settings.

Route Components

A Route is composed of three key properties:

• Path: The unique address that triggers the route (e.g., /about). Paths beginning with a colon (:) are Dynamic Routes, which accept variable data (e.g., /users/:userId).
• Title: The internal, descriptive name for the route, used for organization and reference within Shipcode.
• Assignment: The specific Layout (screen) from your project that is displayed when the Path is accessed.

Visit the Routes tutorial for more information on setting up a Route.