The pattern: define the user workflow, pick navigation type, populate tabs and utility bar to match, assign to the right population, iterate based on usage. The cost is low; the productivity gain compounds across thousands of user sessions.
- Define the user workflow the app should serve
One sentence: "This app serves [population] doing [workflow]." If you cannot finish the sentence, you are not ready to build the app.
- Pick standard vs console navigation
Standard for one-record-at-a-time workflows; console for multi-tab workflows. The choice gates which features are available.
- Open App Manager, New Lightning App
Setup, App Manager, New Lightning App. Walk the wizard: name, description, image, primary color, navigation type.
- Add tabs in the order users will use them
Six to twelve tabs is the sweet spot. Order matters; users gravitate to leftmost. Pick tabs that serve the workflow, not every available object.
- Configure utility bar items for console apps
Console apps support the utility bar. Pin frequently-used items, pop-up occasional ones. Standard apps skip this step.
- Assign profiles or permission sets
Permission sets for org-chart resilience, profiles for small orgs with stable roles. Avoid assigning broad profiles; the App Launcher gets cluttered.
- Pilot with five users for a week
Real user feedback catches navigation and tab-order issues lab testing misses. Iterate then broad rollout.
- Schedule quarterly app inventory review
Lightning Usage Report shows app usage. Deactivate apps no one uses; the App Launcher stays clean.
Standard (one record at a time) or console (multi-tab). Drives feature availability.
The in-app navigation items. Six to twelve is the sweet spot.
Console-only productivity shelf. Pin frequently used; pop-up occasional.
Gates who sees the app in the App Launcher.
Per-app record page variants for objects shared across apps.
- Too many tabs in one app produces an overwhelming workflow. Six to twelve is the sweet spot; more usually means two apps that should be split.
- Standard-navigation apps cannot use the utility bar. Pick console if utility bar is core to the workflow.
- Profile-based app assignment breaks on org-chart changes. Permission sets survive; default to permission sets.
- Custom Apps accumulate. Quarterly inventory and retirement is the discipline that keeps the App Launcher clean.
- Per-app Lightning Record Pages add configuration burden. Use only when the workflow genuinely needs different layouts per app.