Skip to main content
Back to projects
Spillr icon

Spillr

Spillr is a mobile conversation card game. You pick a deck, play a timed round, and see your result, all in one smooth flow.

Role
Product design + mobile development
Outcome
A smooth path from picking a deck to seeing your result, with progress saved on the phone.
Stack
TypeScriptReact NativeExpo
Spillr banner

What it is

Spillr is a mobile conversation card game. This story covers the full path from picking a deck to playing a timed round, seeing the result, and checking your progress.

The finished game includes picking a deck, a short intro, playing cards, results, daily streaks, saved stats, play history, sound, and phone reminders. Everything is saved on the phone, so a round never needs a server or an online account.

The goal is a casual group game that is quick to start, fun while playing, and rewarding after each round.

The problem and the fix

The problem

  • More than a list of cards

    Players need a clear topic, a ready moment, simple card choices, and a result that means something

  • Each round should count

    Streaks, stats, and history should carry the game forward

  • Playing should work offline

    No server or online account should be needed to play

The fix

  • One path from deck to result

    Pick a deck, watch the intro, play cards, and get your own ending

  • Simple card choices

    Answer, pass, or end the round on every card

  • Two-minute pace

    Unanswered cards count as passed when time runs out

  • Progress after each game

    Finished rounds update streaks, stats, and history

  • Sound and reminders

    Sound, animation, and optional reminders bring players back

What I did

  • Turning the provided screen designs into one connected game flow.
  • Building every in-game moment: the intro, flipping cards, answering, passing, running out of time, ending a round, and leaving safely.
  • Linking game results to streaks, stats, and play history saved on the phone.
  • Managing background music, sound effects, animations, and phone reminders across screens.
  • Handling unfinished cases like an empty deck, a lost streak, reminders being turned off, or a player leaving early.

How I designed it

  1. 01

    Start with the whole player journey

    The provided designs and a full walk-through kept every screen looking and feeling the same

    Consistency
  2. 02

    Save every finished round the same way

    The last card, ending early, and running out of time all end the same way

    Flow
  3. 03

    Keep results consistent

    The result screen and history list use the same rule and tell the same story

    Clarity
  4. 04

    Match sound to the open screen

    Music follows the current screen, and result sounds play only once

    Sound
  5. 05

    Protect unfinished rounds

    Confirm steps and an empty-deck message give a safe way out

    Safety
  6. 06

    Choose a predictable, satisfying game

    The round stays focused instead of adding modes or settings it does not need

    Experience

Main features

Picking a deck

A swipeable row shows the available decks and keeps the chosen one front and center.

Animated intro

The chosen deck is introduced with text that appears step by step, a themed animation, and a clear start button.

Timed card play

Players flip one card at a time, then answer it, pass it, or end the round. A two-minute timer counts down, and a card left unanswered when time runs out counts as passed.

Safe back button

The back button is handled with care. Leaving a round in progress asks you to confirm, and the home screen asks before closing the app.

Result screens

Results tell apart a round where everything was passed, a round with no answers, a partly answered round, and a fully answered round. Each has its own message and animation.

Daily streaks

A finished round updates your streak, spots your first game of the day, and shows a streak celebration when it fits.

Saved progress

Cards played, answered, and passed, plus your game history, stay available on the profile and history screens.

Sound and animation

Menu music, in-game music, result sounds, button sounds, Lottie animations, and confetti mark the big moments.

Phone reminders

Optional reminders are set up on the phone, including warnings before your streak is about to run out.

Tech Stack

  • TypeScript

    defines how the app behaves and the rules for its data.

  • React and React Native

    build the mobile screens from reusable pieces.

  • Expo SDK 54

    runs the app on phones and connects to phone features.

  • Expo Router

    moves the player from screen to screen.

  • React Native Reanimated

    powers smooth motion and screen changes.

  • Lottie and React Native Confetti Cannon

    play the intro, result, streak, and celebration animations.

  • Expo AV

    loads and controls music and sound effects.

  • Expo Notifications

    schedules and cancels phone reminders.

  • AsyncStorage and Expo SecureStore

    save game data and the player's name on the phone.

  • React Native SVG and HugeIcons

    draw custom graphics and icons.

  • Figma references

    guide how the mobile screens look.

  • Android and Expo build tooling

    package the app for Android.

  • Groq API

    writes new questions in another part of the app; it is not part of playing a round or seeing results.

Playing a round and seeing results needs no game server, online database, cloud backup, account, or multiplayer service. Writing new questions is a separate online feature and is not needed to play the existing decks.

Hard parts and how I solved them

Keeping results consistent
The result screen and the history list need to describe the same round the same way. One shared rule keeps the title, message, animation, and history marker in step.
Saving progress without a server
The app saves profile data, stats, history, sound settings, and streaks on the phone, and keeps the player's name in the phone's secure storage. If saved data is missing or broken, the app falls back to safe starting values.
Managing sound across screens
Music starts or fades depending on the open screen, and in-game music stops before the result sound plays. Sound effects follow the saved volume and are guarded so they do not repeat by accident.
Handling real-life interruptions
The game handles running out of time, empty decks, the phone's back button, leaving early, reminders being turned off, and lost streaks, instead of assuming every round goes perfectly.

How it works

  1. 1

    The finished game lets a player open Spillr, pick a deck, watch a short intro, play cards at a steady pace, and get a result that matches what happened.

  2. 2

    That same round then counts toward the player’s streak, stats, and history, with optional sound and reminders to bring them back.

  3. 3

    Playing needs no game server, online database, cloud backup, account, or multiplayer service.

    Writing new questions is a separate online feature and is not needed to play the existing decks.

  4. 4

    Testing note: the available Android test build only runs on ARM phones and would not start on the connected x86_64 emulator.

    So the full flow was not tried on a device here. iOS, real Android phones, reminder timing, and every possible result have not been tested yet.

Results

  • Confirmed: the game offers a complete play loop that runs on the phone, with clear player choices, a fixed round time, different result screens, streaks, saved progress, history, sound, and optional reminders.
  • The project has no numbers on downloads, ease of use, speed, or business results, so none are claimed.
  • Our reading: linking each round to streaks and history should make rounds feel complete and give players a reason to come back, but this still needs testing with real players.
  • Testing note: the available Android test build only runs on ARM phones and would not start on the connected x86_64 emulator.
  • Known issue: the history screen’s “Passed” and “No Spilled” filters use the same unfinished-round group, so they do not show different results yet.

What I learned

What I learned

  • A short game works better as one clear path than as many separate screens.
  • One shared result rule stops the result screen and saved history from telling different stories.
  • Saving everything on the phone gives a personal experience without an account, but it makes recovery and sharing harder.
  • Sound and animation need the same careful planning as screens and data.
  • The test build has to match the test device; an app that builds is not proof it runs on every phone.
Next projectCosmicXA space experience in your browser that makes the size of the universe something you can explore, shape, and understand.Read the story
CosmicX banner