Product design

Account Connectivity Dashboard

I turned wallet state, deed context, account assets, and activity into a real-estate dashboard that makes Web3 information readable as product state.

Company
Propy
Industry
Real Estate
Role
UI Design / Web3 UX Consultant
Year
2022–2023

Project context

Case narrative leads with the challenge and problem solved.

Real-estate users need a calmer way to understand wallet connection, property-related blockchain assets, and ongoing account activity without feeling dropped into crypto tooling. The case is intentionally text-led for now, focusing on challenge, constraints, decisions, and problem solved.

Web3 dashboardWallet connectivityAccount UXReal-estate blockchain

Case opening

Web3 dashboard UX, wallet-connectivity translation, account information architecture, and product-system hierarchy.

What was broken
A signed-in Web3 real-estate account can become a junk drawer of wallet state, token holdings, blockchain deeds, marketplace activity, and product news.
What I owned
I concentrated the Web3 portal into a dashboard where account state, asset context, and next actions stay readable without forcing users through crypto mechanics first.
What changed
The case explains how wallet connection, token portfolio, MetaAgents, MetaRooms, deed context, news, and activity became one readable account workflow.
Senior judgment

Separated wallet mechanics from real-estate meaning, then rebuilt the dashboard around account state, ownership context, and next action.

Product clarity index

What this case teaches.

State clarified
Wallet, deed, asset, and activity signals become account meaning.
Handoff stabilized
Dashboard regions map cleanly to live account/product services.
Constraint

Wallet status, deeds, tokens, marketplace activity, and Web3 features could easily read as unrelated crypto clutter.

Decision

Translate each crypto signal into account meaning: ownership context, asset status, activity, and next real-estate action.

Proof

The dashboard workflow groups wallet, token, deed, MetaAgents, MetaRooms, news, and activity into one command center.

Ownership / workflow

What I owned in the product story.

This is the strongest fintech/Web3 evidence: account state, wallet context, asset meaning, and dashboard hierarchy made understandable for real-estate users.

Role
UI design, Web3 UX consulting, dashboard information architecture, high-fidelity interface direction.
Scope
Wallet connection, token holdings, blockchain deeds, MetaAgents, MetaRooms, news, activity, and account navigation.
Tools / workflow
Figma interface design, product-state mapping, modular dashboard patterns, implementation-aware handoff.
Hiring signal
Can translate complex financial/crypto primitives into calm consumer-facing product surfaces.

Challenge / response / outcome

From scattered Web3 account signals to one real-estate command center.

A signed-in Web3 real-estate account can become a junk drawer of wallet state, token holdings, blockchain deeds, marketplace activity, and product news.

I concentrated the Web3 portal into a dashboard where account state, asset context, and next actions stay readable without forcing users through crypto mechanics first.

Design response

The product challenge became an information-architecture problem.

  • Grouped wallet connection, token holdings, and blockchain deed context into a single account dashboard rather than scattering them across separate crypto surfaces.
  • Used modular cards for MetaAgents, MetaRooms, news, and activity so the dashboard can grow without losing scanability.
  • Prioritized real-estate meaning over crypto novelty: ownership, account status, asset context, and next action come before jargon.
  • Kept the surface production-minded with clear regions, predictable hierarchy, and data modules that could be wired to live account services.

What to notice

Interface decisions that prove the product thinking.

  1. Account stateTranslate wallet connection and token holdings into readable product status.
  2. Ownership contextKeep deeds, assets, marketplace activity, and updates grouped around the real-estate account.
  3. Expandable modulesUse cards and activity regions that can grow with live account services without becoming dashboard noise.

Mess

Wallet stateToken holdingsBlockchain deedsMetaAgentsMetaRoomsNews and activity

Design move

From scattered Web3 account signals to one real-estate command center.

Give each account signal a clear module, then prioritize the dashboard around status, ownership context, and recent activity.

Clarity

Connect walletReview assetsCheck deed contextScan marketplace/newsReturn to account actions

Next step

Need someone to untangle a product flow like this?

Bring me in for senior product design, interface systems, workflow cleanup, and production-aware UI direction.