World Builder is a graphical tool that allows users to create, update, and deploy world configurations — the foundational blueprints that define how a decentralised world is structured, including its default apps, naming, and community guidelines. Before it existed, this process was entirely technical, requiring developers to manually edit configuration data. My job was to turn that into a product experience accessible to non-technical users.
// the design challenge
Simplifying without hiding
World configurations have real downstream effects on decentralised systems. Abstracting too much would mean users couldn't trust what they were deploying. The UI had to simplify interaction without obscuring the system logic.
Extension-based UX
Delivered as an installable extension within AKASHA's Extensions app. It needed to feel discoverable, immediately usable after installation, and focused — not a full app experience crammed into a small surface.
Decentralised data constraints
Every configuration field maps to a decentralised storage model. UX decisions couldn't be made independently of the data architecture — designs had to be validated against model structure constantly.
Confidence before deployment
Deploying a world configuration is not easily undone. Users needed a way to verify their settings before committing — reducing trial-and-error and the anxiety of irreversible actions.
// WORLD BUILDER — CONFIGURATION UI
// process
01
Configuration as guided experience
Turned raw configuration data into a structured form flow. Related fields were grouped logically, progressive disclosure reduced cognitive load on first use, and inline help text explained technical fields in plain language.
02
Build Preview page
A dedicated preview step before deployment — showing exactly what the world would look like. This single addition dramatically reduced anxiety around irreversible actions and eliminated the most common support queries.
03
Continuous dev collaboration
Designs iterated alongside implementation every sprint. UX decisions were validated against model structure and hooks — not spec'd in isolation and handed off.
// outcomes
Non-technical access
Community managers and world owners can now configure worlds through a UI — previously only possible for developers.
Reduced dev dependency
Configuration changes no longer require engineering time — teams are unblocked and can iterate independently.
Build preview = confidence
Visual verification before deployment eliminated the most common source of configuration errors and support requests.
Foundation for future tools
The extension pattern and configuration UX established a template for future configuration-driven tools in the ecosystem.
