MOMO

How I solved a complex problem of managing inventory, reservations, and statuses of a local ceramics club.

Role: Designer and Developer

Momo case study hero image

/about momo

Momo is a community where people gather to learn about ceramics by painting pieces or modeling them. The founders were doing everything manually with spreadsheets and notebooks to keep track of the pieces, payments, inventory, reservations.

I partnered with them to build an end-to-end platform for them to manage reservations, register pieces, define prices and accept/activate members. Also, for the visitors to use a mobile app where they would be able to select classes, upload their pieces, check reservations and generate QR codes to accumulate visits for gifts.

Momo platform overview

/why building momo

I challenged myself to not only design an experience, but also build the entire product from the admin portal to the mobile app.

Connecting everything via a database, handling policies, defining schemas, and defining behaviors was a great experience, but also very challenging.

It allowed me to expand my knowledge on how to build reliable and scalable products, and also how to conduct exhaustive testing on my development.

Momo admin portal
Momo mobile app
Momo feature showcase
Momo additional screens

Closing thoughts

/learnings

I enjoyed and learned a lot while designing and building momo. It feels great to take the driver's seat of not only designing every pixel and flow of an experience, but also immediately thinking on the downstream effects and consequences of the design decisions in the systems architecture.

/key outcomes

✦ Basics of proper back-end development
✦ Developing mobile apps with Expo
✦ Quick iteration by getting almost instant feedback