Custom Themes Per App
A tool that looks generic feels generic. When every application looks the same — the same default blue, the same stock icons, the same uniform visual style — there's a low-grade sense that you're using someone else's tool, not your own.
Custom themes let each app look like it belongs to you.
Branding From the Ground Up
Each app has a theme configuration with a small set of high-leverage settings:
Primary color — the accent color used for primary buttons, active states, selected items, and focus rings. This single setting has the largest visual impact — it immediately makes the app look like it was designed with a specific brand in mind.
Logo — your organization's logo, displayed in the app header. Replaces the generic platform icon with something recognizably yours.
App icon — the small icon used in browser tabs and bookmarks. When the app is bookmarked or pinned, this is what users see.
Navigation style — dark navigation sidebar, light sidebar, or top navigation bar. The structural navigation layout affects the overall visual impression of the app.
Different Themes for Different Apps
When you run multiple apps in the same account, visual distinction between them is useful. The sales CRM in your brand's primary green. The internal operations tool in a professional navy. The admin console in a warning amber that reminds users it's a sensitive environment.
Distinct visual identities make it harder to accidentally act in the wrong app. The moment you see the wrong color, you know something is off.
Environments Are Visually Distinct
The same principle applies to environments. Your production environment has your normal brand colors. Your staging environment has a yellow warning stripe or a different color scheme that signals "this is not production."
When a team member navigates to staging to test a configuration change, the visual difference is immediate and obvious. The risk of making a test change in production — because the interfaces looked identical — is eliminated.
Configured, Not Coded
Theme changes apply immediately when saved. There's no compilation step, no deployment, no waiting. Change the primary color, preview it, save it — the theme takes effect on the next page load for all users.
The theme configuration lives in the app definition, so it's part of the blueprint export and can be moved between environments. Your staging environment can have the right theme for staging; promoting to production doesn't overwrite the production theme.