Design Review
Artifact info
Title:

Holomovement App UI & Profile System Design Review

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
February 19, 2026
Next Meeting Date:
February 16, 2026
Hide This
February 9, 2026
Hide This
February 2, 2026
Hide This
January 26, 2026
Hide This
January 22, 2026
Hide This
January 19, 2026
Hide This
January 14, 2026
Hide This
December 30, 2025
Hide This
December 23, 2025
Hide This
December 22, 2025
Hide This
December 12, 2025
Hide This
November 21, 2025
Hide This
November 14, 2025
Hide This
October 24, 2025
Hide This
People
Michael Shaun Conaway
James Redenbaugh
Hera Rose
Mariko Pitts
Artifact Image
Meeting Summary

First Impressions & Design Direction

The session opened with James Redenbaugh sharing the latest round of UI refinements, and the overall reaction from the team was strongly positive (05:50). The deep teal dark mode background was a clear hit — James noted he's "falling in love with it," and Michael Shaun Conaway confirmed his first impression was a "solidly yes." Light mode will still be available, but the dark teal direction is locked in as the primary aesthetic.

Vertical card styles were confirmed as the preferred orientation, framed by the team as feeling like "doorways" — inviting entry into someone's world rather than presenting a flat list (07:44). The signup flow will include three profile image preview styles (circle, square, and doorway/vertical) to ensure photos work across all use cases.

[technology="Custom Membership System"]

🎨 Color System & Visual Hierarchy

The current highlight color was flagged as slightly too dark to be readable at a glance (08:30). James walked through the emerging color language:

  • Teal for Holons
  • Yellow for Ambassadors/Synergists
  • Green for Alliances
  • Distinct colors for Seeking and Offering states
  • Individual colors per domain tag

Mariko pushed for colors that pop more clearly, with Hera suggesting something like a sage or lighter tone for the green. The team agreed to revisit the palette but moved on without finalizing specific values.

For the suggested connections axisMichael Shaun noted the "strong alignment / broader exploration" spectrum wasn't immediately readable (11:03). A subtle dividing line — possibly with arrowheads — was proposed to make the continuum legible at a glance without requiring the user to think about it. James confirmed the axis is logarithmic in style, giving more visual space to closer connections.

🔔 Simplified Member Modal

James introduced a new pill-style member modal that collapses to just two lines by default, expanding on hover to reveal icons for messages, Holons, and light/dark mode toggle (13:06). Notifications aggregate into a single indicator on the Holon icon — the number changes rather than spawning multiple dots. The team loved the Holon icon in this context, especially paired with the notification system.

📄 Redesigned Profile Pages

Moenja has completely overhauled the profile page design, introducing a clean bento-style layout with rounded corners, subtle background color differentiation between sections, and a centered tagline with a framed profile image (14:21). The team's reaction was enthusiastic — "very sharp," "very clean."

Key design discussions on profile pages:

  • Assessments could display as a slider across domains, visible as a badge or visual block on the profile
  • Seeking/Offering keywords could be auto-distilled from freeform text using AI summarization, aiding both readability and matching
  • rich text field with an optional image upload was proposed to let users represent their project or organization more expressively — a logo, artwork, or even a slider of images — rather than being limited to plain text boxes (32:10)
  • Testimonials (potentially rebranded as something warmer — "Send Some Love," "Share the Love") would show mutual endorsements, encouraging reciprocal vouching between members (34:54)
  • "Field" (replacing the concept of a "wall") would allow users to post updates and collaborative content, with pinning capability (39:43)
  • Long-term vision includes drag-and-drop section ordering so members can prioritize what appears first based on their own story

Mariko raised a useful tension: the profile centers the person beautifully, but their work or project also deserves some elevation — the platform's members tend to be people whose careers and purpose are integrated, so their project should have a visual presence, not just a text mention (31:42).

[technology="Community Facilitation Tools"]

🤝 Matching System Design

This was one of the most generative discussions of the session. The current suggested connections view on the directory was affirmed as the right home for proximity-based recommendations. But the team converged on a richer on-demand match experience triggered by a "Match Me" button — either on a member card or from the directory view (26:00).

Key ideas for the matching experience:

  • numerical score (1–100, shown on hover rather than always visible) communicates alignment without feeling like a rating system
  • side-by-side match modal, built dynamically on request, would show areas of overlap — with a brief loading/analysis animation to make the generation feel intentional and interesting
  • The modal should show meaningful dimensions like complementary skills, needs/offers alignment, shared alliances, and overlapping domains of interest — not raw data like event attendance
  • Michael Shaun emphasized that the value isn't just "we matched" but why — giving people enough context to decide if a conversation is worth having before committing to it (19:02)
  • The matching score and comparison view were described as a sticky, gamified feature — something that would make people want to complete their profiles and keep exploring

Hera noted that showing a match percentage could even incentivize profile completion: incomplete profiles mean lower or no matchability — "you're unmatchable" becomes a playful motivator (24:35).

[technology="Intelligent Matching Algorithms"]

🗂️ Domain Categories Refinement

The team reviewed the current domain list and made several proposed changes (43:00):

  • "Economics and New Systems" → "Economics and Collaborative Commerce"
  • "Governance and Social Change" → split into "Collaborative Governance" and keep social change separately, or fold new systems into Technology & Innovation
  • "Spiritual Activism and Inner Development" → "Spirituality and Consciousness"
  • Add: Ethics and Philosophy
  • Add: Science (currently absent from the list)
  • Add: Leadership and Facilitation (proposed as the 12th domain to complete the grid)
  • Potential addition of Psychology embedded in the community/relationships category

The conversation also touched on how domains are used: during profile creation they represent what someone is involved in; during browsing they represent interest. Mariko flagged that unfamiliar terms like "collaborative commerce" might cause people to skip domains they actually belong in — so onboarding copy and tooltip language will need to be clear and inviting (48:22). Short hover descriptions (one sentence max) were agreed upon rather than full paragraphs.

[technology="Directory Systems"]

🗓️ Implementation Timeline & Testing Strategy

James proposed a 7–10 day window to fully implement the new design style, the Field feature, and preliminary matching functionality (41:07). The team aligned on a cautious rollout protocol:

  1. Internal team (core four) gets access first
  2. 7–10 days of internal testing — the goal is to surface and fix obvious bugs before any wider exposure
  3. Then bring in the broader core team

Michael Shaun was emphatic that first impressions matter: "I want to move beyond the 'oh, this is great except it didn't work' experience" (40:08). The priority is making sure the first real experience lands flat-out well.

📊 Project Visibility & Reporting

Hera raised the need for a lightweight but consistent weekly status reporting tool — not a full project management overhaul, just something that shows what's in progress, what's blocked, and a summary of active bugs (54:50). She proposed a RAG (Red/Amber/Green) table format — simple enough that Emmanuel, Laura, or any stakeholder could check it at a glance.

James clarified that the existing project map is primarily an architecture reference — tracking pages, Supabase [tag="supabase"] tables, custom scripts, and copy needs — not a sprint tracker. Both tools serve different purposes and both are needed.

[technology="Collaboration Management Tools"]

---

Action Items

James Redenbaugh

  • Implement full UI refresh: vertical card styles, teal/color system, hover enlargement with blur on connection bubbles (05:50)
  • Build simplified pill-style member modal with collapsed/expanded states, Holon notification badge, and light/dark mode toggle (13:06)
  • Implement redesigned profile pages with bento layout, rich text project field, optional image upload, and assessment display framework (14:21)
  • Build on-demand match modal with dynamic score generation, loading animation, and side-by-side alignment comparison (26:00)
  • Add "Field" (wall) feature to profiles: user posts, pinning, optional image attachment (39:43)
  • Add testimonial/endorsement system with mutual-connection logic to avoid spam collection behavior (34:54)
  • Plan and execute 7–10 day dev window for new design + Field feature + preliminary matching, followed by internal test phase (41:07)
  • Prepare simple weekly status reporting format for team visibility (54:50)

Hera Rose

  • Draft RAG table concept (Red/Amber/Green weekly status view) and email to the full team as a reporting template (55:32)
  • Coordinate onboarding of core team once James confirms internal testing window is open (40:00)

Mariko Pitts

  • Review and provide specific feedback on revised color palette once James shares updated options (09:03)
  • Collaborate on testimonial system copy and branding — make it feel warm and mutual rather than formal (34:54)
  • Help refine domain selection prompts so onboarding language is clear for less familiar terms like "collaborative commerce" (48:22)

Michael Shaun Conaway

  • Send Collaborative Commerce paper 📄 to Mariko and James for context on the domain category rename (44:02)
  • Provide input on the five or six core dimensions the match comparison modal should surface (27:24)
Relevant Initiatives

Directory System Enhancement

Priority: 
Very High
Size: 
L
Planning Stage

Membership Authentication System

Priority: 
Very High
Size: 
XL
Creation Stage

3D Globe Visualization System

Priority: 
High
Size: 
M
Creation Stage

Profile Question & Copy Refinement

Priority: 
High
Size: 
S
Planning Stage

Holon Data Architecture and Entity Management

Priority: 
High
Size: 
M
Planning Stage

On-Demand Matching System

Priority: 
Very High
Size: 
M
Planning Stage

Profile Visual Identity System

Priority: 
High
Size: 
S
Planning Stage

Weekly Status Reporting System

Priority: 
Medium
Size: 
XS
Planning Stage
Transcript