The full story
A mobile wellness companion, with a platform its team publishes from.
MUSE brings five spaces into one mobile app: Muse for conversation, Explore for practices, Learn for guides, Connect for community and Reflect for private history. Meditations, breathing, recorded audio and guided practices sit alongside a text and voice AI companion.
The visible half is the app. The half that decides whether a content product survives is the platform behind it, and that is the larger build. Every session, sound file, breathing pattern and guided practice has to be created, reviewed, scheduled and sometimes pulled, by the people who own the content rather than by an engineer.
So the console covers the whole surface. Meditations and soundscapes with their audio. Breathing patterns on their own schema, because they did not fit the shared content model and forcing them into it would have been the wrong kind of tidy. Practices across movement, ritual, creativity and learning. Pathways and tasks, altar visuals, daily prompts, and the greetings on the home screen.
It also carries the parts people forget to plan for: the community space with its feed, profiles, reports and moderation queue; review of AI companion conversations; notifications; analytics; and role-gated access so the right people reach the right areas.
The mobile app uses React Native, Expo and Expo Router; Next.js powers the separate web console. Supabase provides authentication, PostgreSQL, media storage and Deno Edge Functions. Local storage and a retry queue help user activity sync after a connection failure, while server-side role checks protect administrative actions.
It is the same depth of build we bring to a business platform, aimed at a consumer product instead, which is why it sits alongside our operating platform work rather than in the list of smaller engagements.