Skip to content

Make the admin SPA usable on mobile (read and act, not configure) #226

Open

Description

@shockalotti

From discussion #221 (adroual).

Goal: the admin SPA is desktop-only today. Scope is deliberately "read and act on mobile, configure on desktop" - view bookings, cancel/reschedule, glance at availability. Full configuration on a phone is out of scope.

Root cause

frontend/src/routes/+layout.svelte renders the sidebar as <aside class="w-56 shrink-0"> with no breakpoint. On a 390px phone that is 224px of chrome, leaving ~166px. The wrapper is flex flex-1 overflow-hidden, so content clips rather than scrolling. This alone makes every route unusable.

Phases (cheapest win first)

  1. Shell (do first, unconditional - does not depend on the prioritization answer below)

    • Sidebar becomes a drawer below md
    • Compact header with a menu button
    • Content area scrolls
    • One file: frontend/src/routes/+layout.svelte
  2. List views - stacked-card below sm instead of wide tables

    • bookings (raw <table>, 5-6 cols - the priority one)
    • members, event-types, webhooks, calendar, recordings
    • Pattern: each row becomes a small block with inline labels
  3. Forms and dialogs - two/three column grids go single column; dialogs need max-width clamp plus internal scrolling on short screens

  4. Touch targets - shadcn "nova" is compact (h-8) by design; revisit only after layout moves

Explicitly out of a first slice

Availability editor and calendar month view. A 7-column week grid with drag interactions does not shrink to a phone; needs a different presentation, not a smaller grid. Separate piece of work.

Constraints

  • Admin SPA only. No backend change, no public booking/manage/embed surfaces.
  • pnpm test:visual runs real browser assertions - hang viewport coverage off the existing suite, no new infra.
  • Shadcn/Tailwind conventions per docs/ARCHITECTURE.md §15: run pnpm test:visual after touching ui/** or app.css.

Open question (does not block phase 1)

Which pages does adroual actually need on a phone? If it is mainly the bookings list, phase 1 + phase 2 for bookings is a shippable slice on its own.

Discussion: #221

Activity

  1. pullfrog commented on Nov 5, 2026

    @pullfrog
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions