Run mobile-first rendered QA for the six newly deployed Litify attorney hubs and team dashboards.
Ran viewport-controlled rendered QA using Salesforce LITIFY_ORG frontdoor access and Playwright. Tested 24 rendered states: six custom Attorney Hub tabs on phone, tablet, and desktop, plus six standard Team Dashboard tabs on phone.
Created and pushed QA report: Litify_AI_Integration_Project/handoffs/QA-attorney-hub-mobile-rendered-results-2026-05-28.md.
Commit: ae75bb0 on branch codex/attorney-hubs-all-from-mdt-2026-05-28.
Evidence directory: /tmp/litify-hub-mobile-qa-2026-05-28-full.
All 24 routes loaded with expected Salesforce page titles and no page-level JavaScript errors.
All six custom Attorney Hub pages failed the phone-width check. At 390px phone viewport, each hub rendered with documentElement.clientWidth = 390 and documentElement.scrollWidth = 727, causing clipped content and horizontal panning. Affected: Abigail, Austin, Jimmy, Nick, Terry, Trent.
All six standard Team Dashboard tabs passed the 390px mobile page-width check.
All six custom Attorney Hub pages passed tablet and desktop page-width checks.
Later repeated hub loads began showing the in-hub error: Live numbers could not load. Open the reports in the right column, or refresh the page. This appeared after the QA run had exercised many report-heavy hub loads and likely points to the same synchronous report execution pressure observed during deployment testing.
Representative mobile workflow test: Abigail's internal hub More menu can expose Action Items, but the page also has a Salesforce global More control, so the mobile path is too easy to miss. Action Items rendered, but live numbers had failed by then, leaving no actionable work rows visible in that pass.
The hubs have meaningful attorney-level data, including time on desk, settlements, fees, new cases, offers, demands pending review, stale, missing, client, demand, treatment, settlement, risk, and review signals.
They are not yet strong enough as assistant/case-manager operating centers. The first mobile screen does not clearly show owner, next action, backlog age, stale client communication, or role-specific work queues. Recommended future layer: Attorney Review, Case Manager Today, Assistant Today, Client Follow-Up, Missing Documents, Stale Files, templates, stage playbooks, Agentforce-assisted drafts, follow-up automation, and task creation.
Do not broadly share as finished mobile experiences yet. Fix the custom hub phone-width overflow, reduce report execution load, re-test all six hubs at 390px, and then share as a pilot with attorneys and team leads.
If Sam wants to share immediately, frame it as a live pilot and ask recipients to focus feedback on mobile usability and whether they can identify next actions quickly.