Interaction recipe

Reuse the launcher, not a copy of it.

This page runs Composer’s maintained Apps menu. Change its density, open it, and the search, keyboard, focus and page-position behaviour stay the same because they still come from the one controller.

The runnable study

The trigger below mounts the same AppLauncher component as the site header. This page omits the shell instance because the controller binds one dialog by ID.

Apps and shortcuts

    Browse all apps
    Presentation

    Current presentation selected.

    What stays identical

    • Search across labels, descriptions and reviewed aliases, with a live destination count and a no-results state.
    • Arrow keys, Home, End and Enter; typing after an arrow returns to search.
    • Escape closes even with a query, and focus returns to the control that opened the menu.
    • Body lock and page-position restoration; only the destination list scrolls.
    • One controller, one classic deferred launcher.js, no second search or focus implementation.

    What the study changes

    • Row height, artwork size and section spacing only.
    • Descriptions clamp to one line on wide screens and two on narrow ones; the full text stays in the row for search and screen readers.
    • The close button and footer keep their shipped 44px targets; the search field stays above 44px and the focus outline is unchanged.
    • No change to destinations, access, persistence or app assets.

    Try the behaviour that must survive

    1. Open the menu and type photo. Here / there should remain; the count updates.
    2. Press ↓ then ↑; press End andHome. The active row moves and stays visible.
    3. With text still in search, press Esc. The menu closes and focus returns to the trigger.
    4. Scroll until the position check below is at the top of the viewport, open the menu, then close it. The page should return to the same offset.
    5. Switch to Compact and repeat. Only the density should differ.

    These are browser checks on this page. Physical-device IME, iOS zoom and screen-reader acceptance remain the boundaries recorded in the recipe.

    Position check

    Put this line at the top of the viewport, open the menu, close it, and compare.

    Page position after the menu closes:0 px

    What this recipe is not

    An interface recipe, not a new app operation or permission. The destinations are the ordinary public catalogue; the study reads no owner data, calls no model and stores nothing. Each independent app still commits its own launcher assets and releases them through its own path. Adopting the beta UI SDK is deferred: the current controller already supplies the proven behaviour, while an adapter would add bundle and maintenance cost without replacing app-owned navigation. Revisit that decision if a custom interaction grows beyond this controller.

    Read the contract and the worked refinement