Community Session: UX Enhancement Wishlist

[b3nedictvs]

• sponsored txn
• mirroring candidate flow of nouns.wtf (using attestations)
• dark mode
• base app feature requirements (https://docs.base.org/mini-apps/featured-guidelines/overview)
• Improve accessibility across the app

[swarthyhatter]

UX & Information Architecture Improvements for nouns.build

A Swarthy UX

Summary

This proposal refines nouns.build around a workspace-oriented UX model built on the concept of Hubs. The goal is to make governance activity easier to understand by improving layout, grouping, and visibility, while adding limited summary metrics where context is currently missing.

Design principles:

• Community-first navigation
• Persistent visibility into governance state
• Information-dense layouts for active contributors

Core Architecture: Hubs

nouns.build is organized around three Hub surfaces, each with a single, clear purpose:

• Global Feed Hub — cross-DAO awareness and discovery
• User Home Hub — a personal, cross-DAO governance identity
• Community Hubs — DAO-specific governance workspaces

Global Feed Hub

Purpose: Cross-DAO awareness with explicit context switching.

• Aggregates activity across Builder DAOs (auctions, proposals, drops, high-level treasury/escrow events)
• Adds a tab-style toggle:
  • Personal Awareness (relevant to the user)
  • Global Discovery (ecosystem-wide)
• Existing filters remain available and persist across modes

Answers: “What’s happening across Builder DAOs, and how does it relate to me?”

User Home Hub (Personal Governance Identity)

Purpose: Provide personal governance context for both self-appraisal and external appraisal.

• Communities, roles, token/NFT holdings
• Summary stats (auctions, proposals, votes, delegation)
• Onchain activity log
• Badges as lightweight identity signals
• Proof-of-work style participation visualization

Answers: “Who is this participant, and how do they engage in governance?”

Community Hubs (DAO Workspaces)

Purpose: DAO-specific workspaces with persistent state visibility.

• Left-hand community switching
• Auction visible as a funding “heartbeat”
• Reduced margins and better use of space
• Content grouped by function:

Participation

• Feed
• Drops
• Proposals
• Members

Operations

• Treasury
• Escrow
• Streams
• Auction Activity
• Contracts / Admin

Delegation, Escrow & Streams (Visibility)

• DAO- and member-level delegation
• Clear visibility into delegates, recipients, volumes, milestones, rates, and status
• Goal: immediate understanding of fund control and conditions

Supporting Layers

• Notifications for governance-relevant events
• Expanded DAO analytics (activity, proposals, auctions)
• Analytics inform context and badges, not privileges

Protocol Landing Page

Replace About with an interactive, scroll-driven walkthrough:

• Explains core primitives visually
• Transitions into the live app via “Enter” or “Buidle”

What this is / isn’t

• Is: UX and information architecture evolution with some added summary context
• Is not: A protocol rewrite

[swarthyhatter]

Re Above

The tool bar title's are not exact in this example. This arrangement makes ample room for additional information. For example, Fig4 a&b both represent ADMIN twice. Replace the second admin in section 3, with something else like "Delegates" or, "Analytics"

'Members" can now facilitate enhanced delegation info, voter participation stats, and vote distribution summary visualizations.

'Treasury' can now facilitate active escrow information and recent financial summaries ( inflows outflows )

• It is also worth noting that the above examples represent feeds in which a user can toggle between viewing "proposals" or "mints" when on a DAOs home page without needed to customize the filters. This is because the two types of content are distinctly different and the need to toggle between them will be prevalent. it should also provide a clean aesthetic for viewing Minted content in a gallery orientation, while allowing text to appear slightly more feed style.

• What I do not go in to in depth here is the idea of panels and their contents expanding based on current selections in the proceeding panel . For example:

  1. Panel 1 populates based on the selection in the left hand menu .
  2. panel 2 populates based on the view selected in panel 1.
  3. Panel 3 populates with content based on the selections made in panel 2.
     Though I do feel it is an option worth exploring.

[swarthyhatter]

Fig. 5 USER PROFILE

Fig 5 shows the proposed layout for an individual users profile page.

[swarthyhatter]

Fig 6. EXPLORE FEED

Section 1 - Essentially what currently exists in the "Dashboard"
Section 2 - NFT activity preview window ( leaderboard ?)
Section 3 - DAO ERC20 activity preview window ( leaderboard ?)

Continuing with the idea of nested panels and dependent content population , imagine the following.

1. The user scrolls panel 1 to view the social feed.
2. the user selects a post which highlight its border
3. panel 2 populates with a preview of the authors account information and community standing
4. panel 3 populates with the DAO / community summary info

[swarthyhatter]

The primary goals of this design are to:

1. Increase the amount and type of information which can be seen in a single view.
2. Reduce the need to switch back and forth between content views.
3. Provide fixed boarders to the application, with panels whose interiors scroll, to give the impression of a controlled work environment ( UX )
4. Provide increase transparency and insight into user/community activity/performance without overwhelming the user. By clearly segmenting the types of content for the user, the information is less overwhelming/ intimidating, and it is more intuitive for a user to navigate.

[swarthyhatter]

Thanks Benedict — let me restate this more clearly from the top, because I think we’re close but talking past each other.

Design approach (plainly)

The core unit of space in this design is the Hub.

• A Community Hub is a DAO’s workspace.
• A User Profile is a personal, cross-DAO Hub.
• The Global Feed is a Hub for ecosystem-level awareness.

This is not about adding more pages — it’s about treating each surface as a coherent workspace with a clear purpose.

---

Global Feed (cross-DAO awareness with explicit context switching)

The Global Feed already supports filtering by activity type, and that should remain.

What’s missing is an explicit, easy way to switch context between:

• Personal awareness (activity relevant to me / my DAOs)
• Global discovery (activity across Builder DAOs)

The suggestion here is a tab-style toggle at the top of the feed (e.g. Personal / Global) that encourages users to intentionally switch context.

Important clarification:

• The existing filters should persist regardless of whether the user is in personal or global mode
• The toggle changes scope, not filtering capability
• Filters remain available for fine-grained control; tabs provide fast, opinionated presets

This is not about replacing filters or adding new data — it’s about making context-switching obvious and low-friction.

---

User Profile = Personal Cross-DAO Hub (not a dashboard)

The profile is not a search surface or a dashboard.

It is a personal Hub that provides context — both:

• For you, to understand your participation and standing
• For others, to quickly appraise who you are in governance contexts

Profiles exist today, but they lack:

• Summary stats that contextualize activity (e.g. auctions participated vs won, proposals authored vs passed, delegation in/out)
• A clean, chronological onchain activity log
• Clear role and standing signals (badges, delegation weight, participation level)

So yes, we are adding metrics — but primarily to add context, not to turn profiles into analytics dashboards.

---

Community Hubs (DAO workspaces)

Community Hubs already exist functionally, but the request is about layout and configuration, not feature coverage:

• Keep more governance state visible at once
• Reduce margins and better use available space
• Shift toward panel-based layouts where helpful
• Introduce left-hand community switching
• Treat the auction as a persistent state indicator, not a page you leave and return to

The goal is that when you’re “inside” a DAO, you can reason about auctions, members, proposals, treasury, escrow, and streams without constantly navigating away.

---

UX justification

This approach:

• Reduces view switching
• Makes governance state legible at a glance
• Scales better as DAOs become more active
• Improves onboarding and power-user workflows
• Uses existing components more effectively rather than introducing new primitives

---

Implementation reality

Most of this is reconfiguration and consolidation, plus:

• Adding missing summary/context metrics
• Introducing feed context presets (tabs) on top of existing filters
• Enhancing escrow and stream visibility where the data already exists

This is not a claim that features are missing — it’s a claim that their current spatial organization makes them harder to reason about together.

That’s the problem this design is trying to solve.

[swarthyhatter]

@b3nedictvs
I updated the my OP to reflect more clearly the recommended design approach and considerations. It is quite long however, so I wanted to provide this more concise overview.

TL;DR

A Swarthy UX

This proposal is about reorganizing nouns.build around “Hubs” and improving how existing features and new summary metrics are laid out, grouped, and made visible, not about questioning whether features already exist.

The core idea:

• Treat DAOs, users, and the ecosystem as distinct workspaces (Hubs), each with a clear purpose
• Keep more governance state visible at once to reduce page-hopping

What changes conceptually

• Global Feed Hub

  • Remains cross-DAO
  • Adds a simple Personal / Global toggle (tab-style presets)
  • Existing filters stay and persist across modes

• User Home Hub

  • A personal, cross-DAO identity surface (not a dashboard or search page)
  • Adds summary stats (auctions, proposals, delegation, votes)
  • Shows a clean onchain activity log
  • Introduces lightweight badges (e.g. highest bidder, top delegate)

• Community Hubs

  • DAO pages become true workspaces
  • Left-hand community switching
  • Auction always visible as a funding “heartbeat”
  • Content grouped by governance function (Participation vs Operations)
  • Better visibility into delegation, escrow, and streams

Why this matters

• Less context switching
• Governance state is easier to understand at a glance
• Scales better as DAOs and contributors become more active
• Uses existing components more effectively, with targeted new metrics for context

This is primarily a UX / information architecture evolution, with incremental additions where context is currently missing — not a rewrite of core protocol features.

[swarthyhatter]

Difference View

A Swarthy UX

This document summarizes what changes vs what stays the same relative to the current nouns.build UX. It is intended to clarify scope and avoid restating existing functionality.

---

What stays the same

• Global feed continues to aggregate activity across Builder DAOs
• Existing feed filters (DAO, activity type, etc.) remain available
• User profiles and DAO pages continue to exist
• Core primitives remain unchanged:
  • Auctions
  • Proposals
  • Delegation
  • Escrow
  • Streams
  • DAO analytics (in progress)

---

What changes

Global Feed

Today

• Single feed with filters
• Blends personal relevance and global discovery implicitly

Proposed

• Add a tab-style context toggle:
  • Personal Awareness
  • Global Discovery
• Existing filters persist across both modes
• Tabs act as fast presets; filters remain for fine control

Net change

• Clearer intent
• Less noise
• Easier context switching without removing flexibility

---

User Profile

Today

• Profile pages exist
• Activity and data are fragmented and lack summary context

Proposed

• Profile becomes a User Home Hub (personal, cross-DAO)
• Add summary stats:
  • Auctions participated vs won
  • Proposals authored vs passed
  • Votes cast
  • Delegation in/out
• Add a clean onchain activity log
• Introduce badges as lightweight identity signals

Net change

• Profiles provide context, not just raw activity
• Easier for others to appraise a user’s governance participation

---

DAO Pages

Today

• DAO information exists across multiple views
• Key governance state requires navigation to understand

Proposed

• Treat DAO pages as persistent workspaces
• Introduce left-hand community switching
• Keep auction visible as a funding “heartbeat”
• Group content by governance function:
  • Participation: Feed, Drops, Proposals, Members
  • Operations: Treasury, Escrow, Streams, Auction Activity, Contracts/Admin

Net change

• Less page hopping
• More governance state visible at once

---

Delegation, Escrow & Streams

Today

• Core functionality exists or is emerging
• State is difficult to reason about at a glance

Proposed

• Improve visibility into:
  • Delegates and recipients
  • ETH/token volumes
  • Milestones, rates, duration, and status
• No changes to underlying mechanics

Net change

• Immediate understanding of fund control and conditions

---

Layout & Density

Today

• Center-weighted layouts
• Large margins
• Feed-first presentation

Proposed

• Reduced margins
• Higher information density
• Panel/workspace-style layouts where appropriate

Net change

• Better use of screen space
• UX scales better for active contributors

---

Net Effect

• Fewer full-page transitions
• Clearer governance state
• Better support for active DAOs and contributors
• Mostly reconfiguration and consolidation, with targeted new summary metrics

[b3nedictvs]

While I'm generally in favour of adding an aditional app view that is akin to a workspace "home" view connecting personal and DAO activities across DAOs a user is a member of or "interested in" (could be a favourite/ starring button), I am not convinced that remodelling all DAO pages into a workspace view has broad support. This is mainly due to the stark pivot from the existing UX vision this proposal suggests. It also reminds me a lot of how blank.space looks today, suggesting that DAOs should provide their workspaces if desired themselves.

Nonetheless, I think the activity bar could be a minimally invasive addition that MAY be feasible in the medium term.

Would you be able to provide the final draft of your proposal above as a coherent document that incorporates the feedback? This would significantly enhance the readability and reduce misunderstandings that MAY persist.

[swarthyhatter]

Enhance Delegation & Escrow Support

Facilitate Articulate use of delegation and escrow of DAO owned assets.

justifications:

• Regulatory Compliance Composability
• Nested SubDao Utility

Improve visibility of active escrows , streams, and delegates.

justifications:

• Governance Accountability
• Treasury Management

[b3nedictvs]

That should be prioritised if we can move on the L2 opportunity.

[swarthyhatter]

Enhance Treasury Oversight

Represent estimates of inflows and outflows based on some moving average whose interval could be adjustable

Provide Visualizations of Outflows in aggregate with toggle to view by category .

justification:

• Regulatory Compliance
• Governance Accountability
• Nested SubDao Utility
• Treasury Management

[b3nedictvs]

This is a good feature to take to the backlog.

[swarthyhatter]

Legacy Droposal Support ERC721

I would like to see the UI support multiple view's of legacy droposals. At both the protocol, and Dao level.

• as a user I want to browse droposals in a card gallery
• as a user, I want a studio / carousel view to view individual droposals at scale with the ability to skip back and forth.