Product builder · Shanghai

👋 Hi, I’m Mai.

I design and build digital products from the first uncertain idea to a system that people can actually use.

My work moves between product thinking, interface design, AI workflows, and full-stack engineering. I care about tools that feel clear, humane, and dependable after they enter the real world.

Product DesignAI & AutomationFull-stack Engineering

Selected Work

A record of products I have designed, built, and kept running.

HER HAVEN community interface
Community

HER HAVEN

A private digital community shaped around trust, thoughtful expression, and personal boundaries. The system brings together member review, identity verification, posts, private conversations, food, pets, voice, relationships, and community governance.

Product strategy · UX/UI · Privacy systems · Full-stack development
Air personal system interface
Personal software

Air

A personal operating system that connects time, people, projects, and long-term change. It begins with a calendar and grows into a living record of relationships, clients, commitments, and progress.

Product design · Information architecture · Collaboration · PWA
Flower Ops AI operations workspace
AI operations

Flower Ops

An AI operations workspace that connects products, inventory, orders, sales, logistics, and after-sales data. It turns scattered back-office work into workflows that are understandable, reviewable, and traceable.

AI agents · Business workflows · Data systems · Production operations
SUMO music production workspace
Creative tools

SUMO

A production workspace for music creators, designed around large-file transfer, processing queues, format conversion, recovery, and delivery. Every visible state is grounded in what the system can confirm.

Music tools · Async jobs · File processing · Experience design
Automation

Xianyu Assistant

A lightweight business automation system for handling repetitive marketplace conversations while leaving important decisions to a person. It includes message routing, response rules, service monitoring, domain separation, and ongoing deployment.

Messaging systems · Automation · Docker · Nginx

About

I do not begin from a fixed job title. Some days I define why a system should exist; some days I decide how a complicated workflow should feel; and some days I connect the interface, data, infrastructure, and deployment myself.

I keep returning to the same question: can this be clearer, more reliable, and more respectful of the person using it?