URL-Based Workspace Routing
URLs matter more than they get credit for in business applications. A URL that encodes application state is a URL you can bookmark, share with a colleague, paste into a ticket, or link from documentation. A URL that depends on session state or cookies is a URL that only works for the person currently logged in, on the current device.
Swifty uses URL-based workspace routing, where your workspace identity is always part of the URL.
Your App Has Its Own URL
Every app has its own URL. In production, it looks like yourapp.swifty.build. For internal apps with multiple environments, staging lives at its own subdomain, distinct from production.
The URL is the workspace. Navigate to it and you're in that app. Bookmark it and you can return directly. Share it and the recipient reaches the same app (subject to authentication, naturally).
No Session-Dependent State
Traditional multi-tenant applications often store the current workspace in session or cookie state. This means the same URL can mean different things to different users depending on which workspace their session is currently pointed at.
With URL-based routing, the workspace is in the URL itself. The same URL always refers to the same workspace, regardless of session state. This is a more predictable model that makes link sharing, bookmarking, and debugging significantly more reliable.
Deep Links Work
Because workspace context is in the URL, deep links to specific records and views work correctly. Link someone to yourapp.swifty.build/customers/12345 and they land on that customer's detail page in the correct workspace. The link doesn't require any session context to resolve correctly — it's self-contained.
This makes it practical to share links to specific records in messages, tickets, and documentation. The recipient follows the link and arrives at exactly the right place.
Multiple Apps, Clear Separation
When you're working with multiple apps, the URL always tells you which one you're in. There's no ambiguity, no "wait, which workspace is this?" The URL is the context.
Switching between apps is switching URLs — navigating from app1.swifty.build to app2.swifty.build. Browser tabs represent different workspaces cleanly, and there's no risk of actions in one workspace accidentally affecting another.
URL-based routing is a simple concept with meaningful consequences for how predictably the platform behaves at scale.