RicheMoments Photo Booth Experience

A custom operating system for running event bookings from planning through closeout.

A connected platform spanning a responsive owner dashboard, Hub mobile app, Crew mobile app, and native iOS widget.

RicheMoments needed more than a booking list. The business required one product that could support owner oversight, Crew coordination, event-day execution, financial reconciliation, and quick mobile decision-making without exposing sensitive administrative data.

Identifying details, project information, and user data have been modified to protect client privacy.

ProjectConnected Event Operations Platform

CategoryProduct Design · Mobile Application · Business Operations · Internal Tools

ClientRicheMoments Photo Booth Experience

My roleProduct strategy, UX and workflow design, UX writing, visual design, AI-assisted front-end development, data and workflow architecture, quality assurance, deployment, automation, and ongoing product iteration.

TechnologyReact Native · Expo · JavaScript · HTML/CSS · Supabase · WidgetKit/SwiftUI · Node.js · Vercel · EAS Build · TestFlight

Sanitized RicheMoments owner dashboard showing fictional business health, booking pipeline, next-event readiness, Crew status, payments, expenses, and event activity. — The owner dashboard combines business health, booking readiness, Crew status, balances, expenses, and the next operational decision.

Overview

The platform organizes the full lifecycle of an event rather than separating it into unrelated software categories.

RicheMoments is an event-services business with operational work distributed across bookings, equipment, Crew assignments, client balances, event logistics, expenses, mileage, payment records, and post-event closeout.

The platform brings those workflows into one shared operating system. Owners can move from a high-level business view into a selected event, understand what still needs attention, coordinate with assigned Crew, review proof and incidents, calculate event-related pay, and reconcile the financial activity connected to the work.

The product was intentionally designed for an owner-led business at its current scale. It prioritizes one-event clarity, reliable handoffs, practical controls, and room to grow rather than introducing enterprise dispatch features the operation does not yet need.

The Challenge

The difficulty was not one missing feature. It was fragmentation across the entire event lifecycle.

Important information lived across booking records, payment tools, messages, receipts, reminders, spreadsheets, mobile notes, and personal memory.

That made it difficult to answer time-sensitive questions:

Is the next event truly ready?
Has the assigned Crew member reviewed the final instructions?
What equipment is still missing?
Has setup proof been uploaded?
Are mileage, parking, and event hours ready for review?
Which bank activity belongs to which event?
What requires owner attention right now?

The Solution

Four coordinated surfaces sharing one operational model.

Owner dashboard for administrative, financial, reporting, and reconciliation work.
Hub mobile app as a mobile owner command center for bookings, event operations, and decisions.
Crew mobile app as a focused event-day experience limited to assigned work and submissions.
Next Event iOS widget as an owner-only glanceable view of countdown, readiness, Crew status, balance, equipment progress, and next action.

All four surfaces use the same shared workspace and operational logic so status changes remain consistent across devices.

Product and Workflow Strategy

The product follows the event from commitment through financial closeout.

01Booking
02Readiness
03Crew handoff
04Event execution
05Proof and incidents
06Pay and reimbursements
07Financial reconciliation
08Closeout

Another strategic decision was deliberate restraint. A multi-event dispatch board, continuous Crew location tracking, Crew rankings, shift swaps, and QR inventory scanning were evaluated but not added because they did not match the current operation. The platform stays focused on the work the business actually performs today.

Event Operations Center

Each event becomes a shared operational record rather than a collection of separate messages and checklists.

The selected event includes readiness, smart attention, equipment packing and return, reminders, activity history, saved replies, team communication, and a Crew pay estimate.

The readiness model uses the actual booking, Crew, briefing, equipment, payment, proof, and reminder records. It gives the owner a grounded answer to whether the event is ready rather than relying on a manually maintained percentage.

Sanitized Event Operations Center showing fictional readiness, attention items, equipment, reminders, team communication, activity, and Crew pay estimate. — The Event Operations Center connects readiness, equipment, reminders, communication, proof, activity, and Crew pay around one selected event.

Key Capabilities

A complete operational system across owners, Crew, events, collaboration, and finance.

Owner oversight

Booking pipeline, business health, readiness, Crew status, balances, equipment, expenses, and reporting in a consistent navigation system.

Event operations

Readiness scoring, smart attention, equipment checklists, reminders, activity history, saved replies, team messages, proof, incidents, and pay estimates.

Crew command center

Briefing acknowledgment, event timeline, parking, dress code, communication, proof upload, time, mileage, and reimbursement submission.

Collaboration

Private owner threads, Crew-to-owner messages, event group chat, attachments, bulletins, notifications, unread tracking, and saved replies.

Financial operations

Payments, expenses, receipts, bank activity, owner activity, event allocations, capital assets, tax-exempt documentation, and tax-oriented categories.

Decision support

Smart attention and the owner-only Riche Assistant convert authenticated records into grounded summaries, next actions, and draft communication.

Native widget

A private next-event view showing countdown, readiness, key statuses, and one next action without exposing broader workspace details.

Sanitized owner-only Riche Assistant showing fictional event operations questions, grounded answers, suggested actions, and privacy boundaries. — The owner-only Riche Assistant answers grounded operational questions, summarizes activity, and drafts communication without silently changing records.

Decision Support with Guardrails

The assistant was designed to help owners decide, not to act without them.

The assistant uses a bounded operational context rather than the complete workspace. It can explain what remains before closeout, summarize current activity, draft a message, and open the relevant workspace.

It remains owner-only and read-only by design. It cannot silently change operational or financial records, move money, expose private attachments, or act outside the authenticated workspace.

Operational Journey

The same product supports different decisions before, during, and after the event.

Before

Prepare the event

Confirm package and tax treatment, record payment status, assign Crew, add logistics, review event economics, and resolve readiness gaps.

Handoff

Brief the Crew

Share timeline, parking, loading, dress code, booth placement, equipment, and owner notes. Acknowledgment flows back to the owner.

Event day

Coordinate execution

Use messaging, setup proof, time, mileage, parking, incident reporting, and status updates within one chronological event record.

Closeout

Resolve what remains

Confirm returned equipment, review Crew pay and reimbursements, keep incidents visible, and identify missing records.

Finance

Connect the money movement

Link payments and expenses to bookings and bank activity while preserving owner contributions and draws as non-revenue activity.

Financial Operations

Event profitability depends on connecting booking, expense, Crew, and bank activity rather than reviewing each in isolation.

The financial workspace supports payments, expenses, receipts, bank transactions, owner activity, event cost allocations, capital assets, tax-exempt documentation, and tax-oriented categories.

Multi-link reconciliation allows a deposit or expense to connect to more than one operational record while preserving matched, partially matched, and unmatched states.

Sanitized financial operations and bank reconciliation workspace using fictional bookings, expenses, transactions, receipts, and matching states. — Financial operations connect fictional booking payments, expenses, receipts, bank activity, and event allocations within one reconciliation workspace.

Privacy, Security, and Role Boundaries

Each surface receives only the operational context its user and environment require.

Supabase authentication and row-level security enforce Production, Demo, owner, and Crew boundaries. Demo Mode uses fictional records and disables live external side effects. Crew access is limited to assigned events and the records necessary to complete that work.

Private attachments use protected storage and signed access. API secrets remain server-side. The assistant is owner-only and uses bounded context. The native widget receives only a sanitized operational payload.

Client contact information, message bodies, incident details, attachment links, and broader financial records are excluded from widget storage. Event name and venue can use iOS privacy redaction.

Supabase authentication and row-level security
Workspace-isolated Production and Demo data
Event-scoped Crew access
Protected attachments and signed access
Owner-only read-only assistant
Sanitized widget payload

Responsive and Cross-Platform Design

Each surface is designed for its use context rather than squeezed from one desktop interface.

Sanitized Hub mobile app showing fictional next-event readiness, Crew status, balance, equipment progress, and owner actions. — Hub emphasizes the next decision an owner needs to make while away from the dashboard.

Sanitized Crew mobile command center showing fictional assignment details, briefing, proof, time, mileage, and submission actions. — Crew receives a focused event-day workspace limited to the assigned event and required submissions.

Visual and Interaction Design

The premium brand identity was extended into a dense internal product without becoming ornamental.

Executive operational frame

Black establishes the operating environment, gold marks active navigation and key signals, and cream and white surfaces preserve readability.

Explicit status language

Clear status pills, smart attention language, and visible Saving, Syncing, Synced, Offline, and Sync Issue states reduce ambiguity.

Progressive detail

Compact summaries lead into timelines, instructions, checklists, proof, incidents, and financial records only when the owner or Crew member needs them.

Technical Approach

A shared repository and reusable domain logic support four distinct product surfaces.

The dashboard uses dependency-light HTML, CSS, and JavaScript. Hub and Crew are React Native applications built with Expo. The native widget uses WidgetKit and SwiftUI through a private Expo native module and App Group.

Supabase provides authentication, workspace storage, row-level security, protected attachments, supporting tables and RPCs, and Edge Functions for notifications and optional server-side assistant responses.

Reusable packages contain calculations, Event Operations rules, widget payload generation, and brand assets so the dashboard and mobile apps do not independently reinterpret the same status.

HTMLCSSJavaScriptReact NativeExpoSupabasePostgreSQLRow Level SecurityWidgetKitSwiftUINode.jsVercelEAS BuildTestFlight

Iteration and Product Judgment

The product improved by narrowing the work before expanding the feature set.

One-event clarity over enterprise dispatch

A large dispatch board, continuous location tracking, rankings, shift swaps, and QR inventory were evaluated but deferred because they did not match current operations.

Canonical financial relationships

Payments, expenses, bank activity, owner activity, and event allocations were modeled as connected but distinct records so reconciliation remains trustworthy.

Role-based mobile reduction

Hub and Crew share the operational model but expose different decisions, information, and actions based on responsibility.

Decision support without silent control

Smart attention and the assistant prepare owners to act while preserving explicit review of operational and financial changes.

Demo as a real product environment

Fictional seeded data, disabled side effects, persistent Demo Mode signaling, and workspace isolation support safe review and demonstration.

Quality and Release Discipline

Testing, packaging, deployment, and release validation were treated as part of the product.

116 automated tests

The verified release validation included 116 automated checks supporting the current product state.

Multi-surface testing

Releases were reviewed across desktop, mobile, Expo, TestFlight, and the native widget rather than assuming one surface validated the others.

Controlled release workflow

Backups, migrations, build steps, deployment, and submission remained explicit checkpoints within the release process.

Outcome

A fragmented set of operational records became one connected event operating system.

The completed platform connects owner oversight, mobile booking operations, Crew event-day workflows, collaboration, financial reconciliation, readiness, closeout, and a native widget through one shared model.

The verified outcome is functional rather than promotional: the business now has a production platform, an isolated Demo workspace, role-specific mobile applications, a native widget, financial and event-operations workflows, protected collaboration, and a tested release process.

No conversion, revenue-growth, attendance, engagement, satisfaction, or time-saving claims are made.

Key Takeaways

What the platform reinforced.

Event operations are easier to manage when booking, Crew, proof, pay, expenses, and bank activity remain connected to the event that produced them.
Owner and Crew experiences should share operational truth without sharing the same level of access.
Readiness is most useful when it is derived from real records rather than manually maintained.
Decision support earns trust when it explains and prepares without silently acting.
A native widget should reduce the product to one safe, private glance rather than reproduce the application.
Deliberate restraint can be as important as feature development.

Does your business need more than disconnected tools?

I design connected digital products that bring operational clarity to complex service workflows.

Email Ashley