← Back to portfolio

Party Game · 2026

Cups and Giggles

Cups and Giggles is a mobile-first social guessing game built around party rooms, themed trivia decks, and live multiplayer rounds. I shaped both the player experience and the backend plan for realtime lobbies, scoring, and content delivery.

Role

Product Designer & Full-Stack Game Engineer

Timeline

2026

Stack

Flutter, Fastify, Go, PostgreSQL, Redis

Impact

Live room flows · Category pipeline · Multiplayer architecture

Cups and Giggles home screen showing party actions, featured players, and game categories.
The product opens directly into party actions, featured mixes, and the quick-play modes that drive reuse.

Player experience

Cups and Giggles is designed as a party-first guessing game. Players can host or join a room in seconds, choose a theme, and move through short competitive rounds that work equally well for solo play, remote friends, or in-person groups sharing the same session.

Modes and categories

  • Supports themed decks spanning pop culture, film, games, and public figures.
  • Extends beyond standard trivia into charades, pictionary, multiple choice, and image-based guessing.
  • Uses obscured imagery and clue-driven prompts so the same content can power multiple game modes.

Realtime multiplayer

  • Players create or join rooms with short shareable codes and clear ready-state feedback.
  • Scores, countdowns, and round transitions are synchronized through a dedicated realtime gateway.
  • Global, weekly, and friends leaderboards keep the competition alive beyond a single party session.

System design

A custom content pipeline turns source data into playable decks, so new categories can be imported, processed, and served without hand-authoring every question and image asset.

Architecture snapshot

Mobile client

Flutter frontend with animated navigation, cached images, and hooks for sign-in, ads, and purchases.

Core services

Fastify handles auth, content, and profile APIs while Go manages low-latency room events and gameplay state.

Data layer

PostgreSQL stores users, scores, and question data, while Redis holds room state and live leaderboard updates.

Selected screens