# Appmenu

## Usage

- Application Switching: Enable seamless navigation between different applications within your ecosystem
- Service Discovery: Showcase available services and upgrades to users
- Unified Navigation: Provide consistent access to all services from any application
- `ATS products` should display all connected Add-On products in navigation
- `Add-On products` should display the connected ATS product in navigation

### Placement

- The AppMenu should be the first item in the main navigation.
- Use the default activator when possible.
- If your navigation requires a custom activator, use the `activator` slot.
- Always use a button that clearly and textually indicates the action to be performed.

### Group services

Services can be given to the component by using an array of `AppMenuItems` items or by using the default slot to generate required markup using `nav` `nav-group` and `nav-group-app` components. Either way, organize services into clear, logical groups to help users understand their current services.

#### Active services

- Use clear, descriptive heading for the group (e.g., "Your Applications")
- Place current application first with `selected` status
- Include other active, accessible services for the current client user
  - Use client company-level integration status
  - Or use client department-level integration status if supported
- Use action-oriented descriptions for the services
- If possible route to the service with preserved authentication
  - If not possible, use automatic SSO routing when enabled for organization
  - If not possible, provide pre-filled credentials like username or email in the login of the service
  - In general, the login should be as simple as possible

#### Complementary services

- Use heading to indicate that the group contains services that can be purchased (e.g., "More services")
- Group complementary services together
- Mark services requiring activation with `purchase` status
- Use action-oriented descriptions
- Route to appropriate promotional page of the service in user's current language

## Design Rationale

The AppMenu uses a two-level structure (groups and services) to:

1. Clearly separate active and available services
2. Reduce cognitive load through logical grouping
3. Enable quick access to frequently used applications

Clear visual indicators help users understand:

- Current application context (`selected`)
- Available upgrade opportunities (`purchase`)
- Service relationships and groupings