Kuya Carlos
Back to projects
Personal project

Monito Monita

The Filipino exchange gift, run from one link: draw names, share wishlists, play the theme weeks and do the reveal at the party. No app, no sign-up.

The demo is one click, no sign-up.

Play the 51-second Monito Monita demo video
See it in 51 seconds.
No accounts
a name and a 4-digit PIN to join
233
unit tests, 33 of them for the draw
98
PageSpeed mobile score on the live landing

What it is

Monito Monita is a web app for running a Filipino Christmas gift exchange from a single link shared in the group chat. Everyone joins with a name and a 4-digit PIN, the organizer draws all the names in one tap, and each person opens their own slip, which unfolds on screen with the name written in ink. At the party, a projector shows the reveal one slip at a time, with the organizer's phone as the remote.

The problem

Every December, Filipino families, barkadas and offices run Monito Monita: a secret gift exchange. Names are drawn as a bunutan (folded paper slips pulled from a bowl), the weeks before the party have themes like “something soft” or “something red”, and at the party each person reveals who they had.

Today it runs on a Messenger group chat, a spreadsheet and someone's memory. Someone has to draw the names and keep them secret, people forget the week's theme, wishlists get lost in the chat, and anyone who joins late or misses the draw makes it harder.

My role

Solo project, built with AI tools: Claude Design for the design directions and screens, and Claude Code for writing the code.

I owned the product decisions, wrote the specs and rules the AI worked from (they're in the repo's CLAUDE.md and docs/), reviewed every change, and tested the live app, including on my own iPhone.

Design process

  1. 01

    A generic first look

    The first build used a “Puto Bumbong” look. It worked, but it looked like every other AI-made app.

  2. 02

    Three directions, one pick: Handmade Pasko

    I explored three new directions in Claude Design and picked the third: the evening before Simbang Gabi, a paper parol as the only strong colour, and everything else made of paper someone prepared: a listahan notebook page, gift tags, a capiz card, papel de japon.

    Three rules

    1. Colour is light.
    2. Different jobs use different materials.
    3. Nothing is blurred.

    Four signature moments

    1. A small bowl on the landing page that draws a sample slip.
    2. The join drop: your name lifts off the notebook as a slip and falls into the bowl.
    3. The slip unfold, with the name written letter by letter like wet ink.
    4. The party reveal: the slips flip around a ring of lights and the parol lights up at the end.

    Everything else moves only when you touch it.

  3. 03

    The landing, redesigned twice

    First, the 51-second demo video moved into the first screen, behind a click-to-load poster, so a visitor sees the whole idea in a minute. Then the page was cut down to one picture and one row: the headline and buttons beside the video poster on laptops, one centred column on phones, and the bowl made small and set on the corner of the “Paano 'to?” notebook list.

Where it ended up

The landing: one link for the whole bunutan, the video in the first screen.
On a phone, everything that matters is above the fold.
After the draw, your slip waits, folded.

Built for budget phones

Most people open the link from Messenger on a phone, so every screen was designed mobile-first, with 16px inputs (no zoom on iPhone), 44px tap targets and respect for reduced motion.

Engineering highlights

Numbers as of 21 November 2026.

A draw that makes one loop

  • The draw is a pure function that builds a single gift loop (A → B → C → … → A), so the reveal can go from person to person. It respects exclusions both ways.
  • It tries the most-constrained person first, and says which exclusions to relax when no loop exists.
  • 33 tests, including 400 random groups checked against a brute-force search over every possible loop.

Pairs never leak

  • Before the reveal, no page, JSON or network response shows who gives to whom, except your own receiver.
  • End-to-end tests check the HTML and every response at each stage, for groups of 3 and 30.
  • Personal-link tokens are kept out of the Referer header.

Identity without accounts

  • Tokens are 32 random bytes, stored only as SHA-256 hashes. PINs use salted scrypt.
  • 5 wrong PINs lock a member out for 15 minutes; 10 lock them out until the organizer unlocks them.
  • Per-IP rate limits on creating, joining and failed come-backs.

Nothing heavy until it's needed

  • The landing's first load is a 16–39 KB poster image: no video, no player, no animation code.
  • The bowl's animation code loads when someone touches it. The slip's animation library (GSAP) arrives once the page is idle.
  • A tap that comes before the code is queued and still plays.

Forms that survive a slow phone

  • People start typing before the page's JavaScript loads. The create-group form keeps whatever was typed.
  • An error coming back never overwrites what was typed after submitting.
  • Tested at 6× CPU throttling on a 400 ms / 1.6 Mbps network.

Budgets, measured

  • At most 150 KB of compressed JavaScript on the first load of the pages members open: the join page is 147.0 KB, a member's page 146.4 KB.
  • The slip unfold runs at about 60 fps at 4× CPU throttling, and a tap starts it moving in about 25 ms.
  • PageSpeed Insights on the live landing: 98 mobile and 100 desktop for performance, 100 for accessibility, best practices and SEO.
The organizer sees who has opened, never who drew whom.

Testing

  • 233 unit tests (Vitest), including 33 for the draw.
  • 77 database constraint tests, run against a Neon branch and rolled back.
  • 62 Playwright test runs on a Pixel 7 (Chromium), an iPhone 14 (WebKit), a 1366×768 laptop and a 1920×1080 projector: the whole flow from creating a group to the reveal with each person in their own browser, offline and recovery, slow phones, reduced motion and the one-click demo.
  • A layout sweep of every page at 11 screen sizes, from 360×740 to 1920×1080, that fails on overlapping controls or text. Join, create-group and the organizer page are also checked at 200% text size.
  • A usability test with AI personas, such as a kuya tapping Join on a slow phone and an organizer running a 20-person group. Each fix is tested the way the persona ran into it.

The real-iPhone audit

I tested the live site on my own iPhone in Safari. The audit, and the permanent overlap check it led to, caught:

  • The date field on the create-group form spilling into the Budget field, taller than the others, with no placeholder.
  • On a phone turned sideways, the reveal's controls covering the ring of slips. In portrait, Next below the fold on an iPhone SE.
  • A wishlist field's tap area covering the field below it.
  • The logo, Edit and wishlist links smaller than a 44px tap target.
  • Text cut off with an ellipsis, now wrapping onto the next notebook line.
  • Buttons, PIN boxes and labels breaking at 200% text size.
  • A submit race behind a flaky test: an error coming back could undo what was typed after submitting.
Create a group: a name, a date, a budget and the theme weeks.

Screenshots

Joining takes a name and a 4-digit PIN. No accounts.
Open it, and the name is written in ink, with their wishlist below.
At the party, the organizer's phone is the remote.
Handa na? Twelve slips, twelve secrets.
Each Next flips a slip and lights the way to the next person.
The finale: the parol lights up. Maligayang Pasko!

Tech stack

Next.js 16React 19TypeScriptTailwind CSS v4Neon PostgresDrizzle ORMZodGSAPUpstashPostHogVitestPlaywrightRemotionVercel

Next.js 16 with the App Router and React 19, TypeScript in strict mode, Neon Postgres through Drizzle ORM, and Zod. Upstash handles rate limiting, and PostHog records server-side events only, with no personal data. It runs on Vercel in the Singapore region, with a daily cron that deletes expired demo groups.

The demo video is code too: a Remotion project that records the app's real screens frame by frame and cuts them with React components that reuse the app's slip, parol and sky.

First commit 9 Nov 2026public and tested on 21 Nov138 commits

What I'd do next

  • AI gift ideas: suggestions from the receiver's wishlist, the budget and the week's theme, with limits per group.
  • Office plans: big groups, CSV import, custom branding and several groups per company.
  • Optional organizer accounts, for people who run more than one group a year.

Want to build something like this?

If you have an idea for an app people would open from a group chat, or want to talk through how this one was built, reach out.