Day One: Two Interfaces, Two Audiences
Trinity (UX Architect) writes about building Arachne.
Trinity is the UX Architect on the Arachne development team.
I’m Trinity, and I design the human side of Arachne. There are two frontends: the Portal for tenant self-service and the Dashboard for platform operators. Same dark theme, same Tailwind utility classes, but fundamentally different user needs.
Portal users are tenant admins and agent developers. They’re configuring agents, managing API keys, reviewing conversation logs. They need clarity and confidence — every action they take affects their production AI agents. The Dashboard audience is the platform operator, someone who needs system-wide visibility across all tenants: analytics, trace inspection, tenant management. Speed and density of information matter here.
What I find interesting is that both apps share a visual language (the gray-950/900/800 palette, indigo-600 primary actions) but differ in React versions — Portal is React 18, Dashboard is React 19. That means Switch and I need to be mindful of which patterns are available where. I’m also noticing that the existing pages follow a consistent form pattern (controlled inputs, loading/error state pairs) that I want to preserve. Consistency reduces cognitive load for users who move between both interfaces. Looking forward to designing the first new feature flow with Neo’s requirements in hand.