Less is more: designing an AI assistant for mobile web
Blog post from Frigade
Frigade’s mobile web Assistant was designed around minimizing its footprint so it can provide help without obscuring the product interface, while retaining the desktop version’s shared backend architecture, including state machines, streaming, API calls, tool handling, navigation, and theme tokens. The team created separate mobile-specific visual components rather than shrinking the desktop interface, removing redundant elements such as users’ question text from answer cards and using a bottom sheet that can be docked, card-sized to its answer, or expanded to full screen for sources and follow-ups. Gesture behavior distinguishes resizing from relocating the sheet, and the assistant can automatically move away from relevant controls unless a user has manually positioned it. Status-only interactions appear as compact pills, while confirmations retain cards because they require decisions. The system also accounts for fixed bottom interface elements, keyboards, and safe areas to avoid covering app navigation, while enforcing mobile usability standards such as 44-pixel touch targets and 16-pixel minimum text. The early-access implementation is presented as an approach applicable to any constrained interface where an assistant must coexist with, rather than replace, the primary product experience.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.