Development Review
Artifact info
Title:

Holomovement App — Feature Development & UX Review

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
March 2, 2026
Next Meeting Date:
February 25, 2026
Hide This
February 16, 2026
Hide This
February 19, 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

🛠️ Prototype Progress & Upcoming Testing

James opened with a solid update on momentum across several fronts (01:13). Membership functionality is now working end-to-end — signing up, paying for things, and a pay-what-you-can system have all been figured out, described as a "fun breakthrough." A smart access system tied to subscription status is functioning on both the back and front end. The Webflow [tag="webflow"] build is actively in progress, with James taking over directly from a team member who fell ill, noting that moving fast himself is actually better at this stage given the number of important architectural decisions involved in building each element for editability and future scalability.

The team is targeting the prototype being ready for a new wave of testers within the next couple of days, with front-end UI included (53:10). Mariko flagged that getting people into the prototype is a priority given that it's now March, and the team agreed to aim for something showcase-ready for the core team meeting on Thursday.

[technology="Custom Membership System"]

💳 Pay-What-You-Can Payment Design

James demonstrated the current Stripe [tag="stripe"] integration, showing a working text-field input for custom payment amounts that routes through a familiar Stripe checkout — supporting Link, Amazon Pay, and other methods (18:35). Michael Shaun shared an earlier design concept featuring a two-screen slider approach: the first screen offering a suggested range (e.g., $15–$20/month) with a secondary option for users who need a lower tier, framed as a "scholarship" rather than a discount. The team responded positively to this framing.

Additional ideas surfaced in the discussion:

  • A wave-based slider visual with increasing amplitude, per Mariko's suggestion
  • Adding an annual gift toggle — "double the impact by making your gift annual"
  • PayPal integration for better international accessibility (James confirmed this is now easier to add)

James also showcased a working wave-amplitude slider prototype he built, where predefined moments shift the wavelength visually — a component that could translate directly into the payment UX (19:47).

[technology="Communication Automations"]

🌍 Globe & Animated Visual Elements

A newer version of the globe interface was shared, featuring animated lines rising over the sky, a wrap/unwrap animation on the globe itself (described as "hologram-like"), and nation borders being added so users can better orient to where community members are located (21:29). The team responded enthusiastically — Michael Shaun called it "a big hit."

Design notes on the globe:

  • Nation borders should be kept close to the background color so continent outlines pop more strongly
  • The transparency/see-through effect on the globe was noted as striking and intentional — "like a hologram"

[technology="Parametric Geometric Interfaces"]

🎨 Icon Design Feedback — Engine for Good

Michael Shaun shared detailed feedback on the redesigned icon set for the Engine for Good framework (02:54). The core concern: icons should be readable without words — a viewer should be able to glance and understand the concept. The prior AI-generated set was acknowledged as generic (money bags, bar graphs), while the newer designs trend abstract but lose communicative clarity.

Specific feedback by icon:

  • Holons Form — strongest of the set; the three-people-in-a-circle reads clearly and represents something important
  • Take Action — not bad, communicates reasonably well
  • Collaborative Commerce — too complex, feels like a Christmas tree with upward energy; needs simplification, fewer lines (3 instead of 5), a slight off-angle rotation, and some kind of container or framing element
  • Ethics & Philosophy — the buckyball/molecule expansion concept is interesting; team was split but leaned toward keeping it
  • Fun to Work — money bag must go; needs a full rethink
  • Feel the Engine — not terrible as a representation of money/fuel, but still needs refinement

The order of icons was also updated following a session with Laura, now sequenced to tell a more logical story: Holons Form → Take Action → Fuel the Engine → Prove Impact → Fun to Work.

Mariko added a useful reframe: an icon that's intriguing enough to make someone stop and read can be a feature rather than a bug — reverse-engineering the psychology of fast media consumption.

👤 Holon Pages & Profile System

The team discussed the design direction for Holon Pages, which don't yet have a dedicated design (30:50). James suggested they can borrow heavily from profile page components but feel more centered — group image in the middle, name on top, with members displayed beneath.

For member display scalability, James described dynamic circular layout scripts already built:

  • Up to 13 members: arranged symmetrically in a single circle
  • 13+ members: two concentric layers, packing like a molecule

Mariko suggested a gold/yellow border on profile circles to distinguish admins within a Holon — not a size hierarchy, just a color signal. The team aligned on this approach.

On scope: Alliances are being deferred for now. Focus remains on individuals and groups as the core experience before adding that third layer.

[technology="Directory Systems"]

📊 Assessment Engine Planning

A significant portion of the meeting was spent planning the assessment engine (37:24). James demonstrated a recently built client assessment as a reference point — a multi-screen multiple choice flow that outputs 1–10 scores across five metrics, generates a spider graph, and classifies users into types. Simple, logic-based, no agentic analysis required.

The team aligned on building something similar with 5–6 domains (5 makes a pentagram shape; 6 makes a star). Michael Shaun committed to starting a shared document immediately with candidate domain names and questions.

Key design principles the team wants to apply:

  • Spectrum-based framing rather than qualitative scoring — "does this sound like you or not?" rather than "how good are you at this?"
  • Questions should feel neutral and interesting, avoiding test-taking bias (the MMPI/Myers-Briggs problem of people answering how they want to appear)
  • Should be completable in 10 minutes or less
  • Each domain should have more candidate questions than needed so the team can cull weak ones

Mariko advocated for including at least one fun, gift-like assessment (e.g., the numerology mandala tool) — something people would do just for the experience, that enriches their profile organically without feeling like data extraction.

James floated a longer-term vision: a garden of assessments users can choose from, with the power to decide which assessments inform their matching — so astrological or numerological inputs are opt-in rather than default.

James also shared a new version of the numerology mandala tool that builds the visual in real time as you type — the team expressed interest in integrating this into the platform (43:44).

[technology="Assessment Systems"]

[technology="Intelligent Matching Algorithms"]

🧹 Profile & User Cleanup

Before the next wave of testers comes in, James will do a pass on existing test profiles — deleting obvious test entries while preserving any profiles where real effort was put in (53:23).

---

Action Items

James Redenbaugh

  • Complete Webflow [tag="webflow"] front-end UI build and have prototype ready for tester access within the next couple of days (13:05)
  • Add PayPal to the payment flow for international accessibility (19:30)
  • Implement the two-screen pay-what-you-can slider design with wave animation and annual gift toggle option (16:43)
  • Refine icon set per feedback: simplify Collaborative Commerce icon (fewer lines, slight rotation, add container/framing), revisit Fun to Work icon, apply gold border logic to Holon admin indicators (24:50)
  • Build scalable dynamic circular layouts for Holon Pages with molecule-style packing beyond 13 members (34:41)
  • Fix numerology assessment (model/API update needed) and explore integrating the real-time mandala builder into the platform (38:07)
  • Clean up test user profiles, preserving those with real input (53:23)
  • Have front-end prototype ready to showcase to core team by Thursday (54:22)

Michael Shaun Conaway

  • Start and share the assessment domains document — list 5–6 candidate domains and draft multiple questions per domain for team review (40:52)
  • Frame questions as spectrum/identity-based rather than evaluative to minimize bias (48:29)
  • Hold internal review with Hera before socializing the document more broadly (52:43)

Mariko Pitts

  • Review and provide copy for onboarding flow document Hera started (35:37)
  • Contribute to assessment brainstorm — especially fun, gift-like assessment concepts for profile enrichment (41:56)
  • Coordinate Thursday core team update and prepare to showcase prototype progress (53:50)
Relevant Initiatives

Membership Authentication System

Priority: 
Very High
Size: 
XL
Creation Stage

Directory System Enhancement

Priority: 
Very High
Size: 
L
Planning Stage

Assessment Development

Priority: 
Very High
Size: 
Planning Stage

3D Globe Visualization System

Priority: 
High
Size: 
M
Planning Stage

Engine for Good Icon Redesign

Priority: 
High
Size: 
S
Creation Stage

Holon Page Design & Implementation

Priority: 
High
Size: 
M
Planning Stage
Transcript