Nexus App UX&UI
Introduction
Problem
Research
Design Goal
Iterations
Outcome
Reflection
Nexus App UX&UI
Team
Kevin Z (Developer)
Contributions
Founding UI/UX Designer Co-Founder
Categorization
Startup
Time
2025
Introduction
ArchNexus is a platform that gives users access to the best AI models with pay-as-you-go pricing. Unlike subscription-based services that lock users into one provider, ArchNexus prioritizes flexibility, transparency, and exploration.
My role as the sole designer on the team is to design the end-to-end user experience. From researching pain points in existing AI services to iterating the product’s interface, flow, and brand positioning.
Problem
As users ourselves, here are some assumptions from our personal experience:
AI is overpriced: Most users don’t use enough volume to justify $20+/month subscriptions.
Subscriptions discourage exploration: Users are tied to one provider and can’t easily try others.
Best AI models are gatekept: Advanced models are barred behind premium tiers.
Research
User Research
I began by analyzing the current AI landscape and speaking to students who use AI in various stages of intensity. Key takeaways:
Competitive Landscape
Competitors either lock users into a single LLM or force them into flat-fee subscriptions. We aim to give choice and flexibility for cost cost-conscious users who want power without overpaying.
Design Goal
Transparency → show real-time cost and usage at a glance.
Flexibility → enable seamless switching between models/providers.
Clarity → simple onboarding, minimal jargon, user-first flows.
Iterations
Wireframing
Early sketches explored token cost dashboards and model-switching workflows. I tested low-fidelity wireframes with target users to validate flows.
Before & After
At first we designed to implement token system to simplify pricing calculation to reduce cognitive load, yet users feedback mentioned preferring transparency and feels token system to be scummy. We thus removed the token and shows the detailed cost breakdown so that users know how they are being charged.
We observed that users have to go through multiple clicks after a response to compare models and perform other relevant actions, so we modified the response to have a quick action tool belt that allows users to compare models and regenerate more easily.
Higher Fidelity
Dashboard with cost transparency (see usage + spend in real time).
Scan friendly model switcher for jumping between AI models quickly.
Quick access tool bar for more control and convenience with the response.
Outcome
Deliverables
Full design system + UI prototype
Branding + product positioning
Collaboration with a developer for a fully functional MVP
Roadmap
ArchNexus is now in closed beta. We mostly ready to launch but are still testing more usability and polishing the experience.
Reflection
I'm incredibly grateful for my partner in crime Kevin, who's coding made this entire project possible. There are so many things we learning in the process of building ArchNexus, here are some of the best:
Developer-designer collaboration: Working with Kevin the full-stack developer has helped me understand some of the best practices for optimizing design for dev handoff.
More features are nice, but priority matters: We originally envisioned the app the have more features and available on more devices, but soon realized that getting a MVP out is more important.
Startups are not for the fainthearted: Building on ArchNexus with only my buddy and I had me experience the demanding work of startups. Having ideas and plans aren't enough, hard work and persistence