World Builder
The World Builder is a graphical tool that allows users to create, update, and deploy world configurations, the foundational blueprints that define how a world is structured, including default apps, naming, and community guidelines.
Overview
Role
Lead Product Designer
Developer-friendly tool for configuring and previewing decentralized worlds
Problem & Context
Configuring a world in a decentralized system requires working with
-
Structured configuration data.
-
Decentralized storage models.
-
Multiple foundational settings that affect downstream behavior.
​
​​Before the World Builder, this process was
-
Highly technical.
-
Difficult to iterate on.
-
Inaccessible to non-technical users.
The Challenge
To design a configuration experience that
-
Simplifies interaction without hiding system logic.
-
Works within decentralized data constraints.
-
Can scale as configurations become more complex.​​​​
Goals & Success Criteria
Design Goals
-
Enable users to create and update world configurations through a UI.
-
Reduce friction and errors in configuration workflows.
-
Make configuration outcomes visible and verifiable.
-
Support future integration with AKASHA World.
​
Success criteria
-
Non-technical users can complete a valid configuration without technical experience.
-
Configuration data is reliably saved to decentralized models.
-
Users can preview a world build before deployment.
-
The UX scales with additional configuration fields and logic.
Design Process
Configuration as a Guided Experience
The core design challenge was turning configuration data into a product experience.
Design decisions focused on:
-
Clear grouping of related configuration fields.
-
Progressive disclosure to reduce cognitive load.
-
Direct mapping between UI inputs and underlying models.
The goal was clarity, not abstraction.
​
Extension-Based UX
Designing the World Builder as an installable extension required:
-
Clear discoverability within the Extensions app.
-
Immediate usability after installation.
-
A focused, task-oriented interface.
-
The extension was designed to feel lightweight but powerful.
Build Preview as Validation
Designing the World Builder as an installable extension required:
-
A separate build preview page was introduced to:
-
Let users verify configurations visually
-
Reduce trial-and-error
-
Create confidence before deployment
This page acted as a bridge between configuration and execution.
Collaboration with Developers
-
Worked directly with developers throughout all sprints.
-
UX decisions validated against model structure and hooks.
-
Designs iterated alongside implementation.
-
Close alignment on feasibility and scalability.
This tight feedback loop ensured design intent translated accurately into the product.
Impact & Outcomes
-
Enabled non-technical users to configure worlds via UI
-
Reduced reliance on developers for configuration changes
-
Improved confidence through visual build previews
-
Created a foundation for future configuration-driven tools