Skip to main content
In this tutorial we’ll build an example study platform using Trophy for gamification. If you want to just skip to the end then feel free to check out the example repository or the live demo.

Table of Contents

Tech Stack

Pre-requisites

  • A Trophy account (don’t worry we’ll set this up as we go along…)

Setup & Installation

Want to skip the setup? Head straight to the fun part.
First we need to create a new NextJS project:
Feel free to configure this new project however you like but for the purposes of this tutorial we’ll pretty much stick with the defaults:
Next, we’ll initialize a new install of everyone’s favourite UI library, shadcn/ui:
I ran into a warning with React 19, which looks to be a common issue when initializing with npm:
For the purposes of this tutorial I chose --force but you should choose whichever setting you feel suits your requirements.

Building the Flashcards Feature

Setting Up Flashcard Data

For the purposes of this tutorial, we’re going to be using some simple types with an in-memory data store. In a production application you’d probably want to consider storing this information in a database. Here we’ll have a very simple type that stores information about each flashcard where we’ll use the front property to store questions that the student wants to learn the answer to, and the back property to store the answers to each question:
src/types/flashcard.ts
Then to get us started we’ll store a few flashcards in memory centered around learning capital cities:
src/data.ts

Basic Flashcard Layout

With some basic data set up, we need to add a way for users to flick through their flashcards. For this we’ll use the carousel and card components from shadcn/ui so we need to add these to our project:
Then, we’ll create a new <Flashcards /> component that combines these into a working solution, specifying that we can pass along any list of IFlashcard objects as props
src/app/flashcards.tsx
Then we’ll update our page.tsx file to display our <Flashcards /> component, passing in our example flashcard data:
src/app/page.tsx
At the end of this step, you should have a working flashcard UI that allows you to flick through each flashcard in our cities data set.

Flipping Flashcards

Now this is great, but it’s not much use as a study app right now as there’s no way to see if you got the answer right! We need to add a way to flip flashcards over and check our answer… To make this simpler, we’ll first create a <Flashcard /> component that will be responsible for all the logic for each flashcard:
src/app/flashcard.tsx
Then we’ll simplify our <Flashcards /> component to instead just render out a list of the individual <Flashcard /> components:
src/app/flashcards.tsx
Now we’re ready to add interactivity to each flashcard. Here’s what we’ll do:
  • First, we’ll add a side state variable that will hold the current side of the flashcard that’s showing.
  • Next, we’ll add an onClick() callback to the <Card /> component that will update the side state to back when clicked if the front of the card is currently showing.
  • Finally, we’ll conditional render the text in the <Card /> based on the value of the side state variable.
Here’s the finished file:
src/app/flashcard.tsx
Then, we’ll use Motion to add a neat flip animation to the card when we click on it. For this we first need to install the package into our project:
If you think about it, when you flip a flashcard, you tend to do it in the Y-axis. So here we’ll use a <motion.div /> with a light spring animation in the y-axis to create the effect:
src/app/flashcard.tsx
You’ll notice we also added a couple of styles here. These do a couple of things:
  • Ensure that when a <Card /> is flipping, the ‘back face’ isn’t visible during the animation with backface-visibility: hidden;
  • As the <Card /> component is a child of the <motion.div />, usually it would appear flat when it’s parent rotates in 3D. Adding transform-style: preserve-3d; to the <Card /> ensures it keeps it’s 3D effect when it’s parent animates.
src/app/flashcard.module.css

A Flippin’ Bug!

Sweet! Our project is now starting to feel like a real study tool! However the keen eyed (or maybe not so keen…) will notice there’s one major bug here. When we flip a card over, the answer on the back appears in reverse 😢…
I you think about it, when you write a flashcard, you actually write the answer on the back in the opposite direction to the question on the front. And as we’re using motion to literally flip over our card in the Y-axis, we need to make sure we write our answers backwards as well. First, we’ll add a little CSS snippet to handle writing text backwards:
src/app/flascard.module.css
Then we’ll conditionally add this style to our card text based on which side of the card is showing:
src/app/flashcard.tsx
Ok awesome. Now when we flip over a card the answer on the back should read in the right direction:

Tracking Progress

The next step is to add some UI to show the user how many flashcards they’ve looked at, and how many in the set they have left. We’ll use a simple progress bar to achieve this. Before we can start tracking this level of information, we need to set up tracking for a new state variable that holds the index of the flashcard the user is currently looking at. We’ll use the carousel api to hook into the functionality here and keep our state variable up to date:
src/app/flashcards.tsx
Then we need to add the progress component from shadcn/ui to our project:
Finally we can add a progress bar above the carousel:
Sweet! Now things are really starting to come together.
Now the real fun begins…

Adding Basic Gamification

In this section we’ll be adding the following gamification elements to the flashcard project:
  • Achievements for completing:
    • 10 flashcards
    • 50 flashcards
    • 100 flashcards
    • 250 flashcards
  • Daily streak for completing at least one flashcard a day.
  • Automated emails for:
    • Achievement unlocked
    • Weekly progress summaries
This might sound like a lot, but would you be surprised if I told you could build all this in less than 10 lines of code? Yup, you can. Trophy makes it super easy to build these features with a few lines of integration code. So, let’s get started…

How Trophy Works

First off, we need a new Trophy account. Then we can start to piece together the various parts of our gamification experience. In Trophy, Metrics represent different interactions users can make and can drive features like Achievements, Streaks and Emails. In Trophy we track user interactions by sending Events from our code to Trophy against a specific metric. When events are recorded for a specific user, any achievements linked to the specified metric will be unlocked if the requirements are met, daily streaks will be automatically calculated and kept up to date, points are awarded, and leaderboards are updated. This is what makes building gamified experiences with Trophy so easy, is does all the work for you behind the scenes. Recording an event against a metric for a specific user makes use of Trophy’s metric event API, which in practice looks like this:
That’s how in just a few lines of code we can power a whole suite of gamification features. However, before we can start sending events, we need to set up our new Trophy account.

Setting Up Trophy

Here’s how we’ll setup our Trophy account for our study app:
  • First, we’ll set up a Flashcards Flipped metric
  • Next, we’ll setup achievements linked to this metric
  • Then, we’ll configure a daily streak linked to this metric
  • Finally, we’ll configure automated email sequences for this metric
Let’s get into it…
Head into the Trophy metrics page and create a new metric, making sure to specify flashcards-flipped as the metric key. This is what we’ll use to reference the metric in our code when sending events.
Next, create one achievement for each of the following milestones:
  • 10 flashcards (Elementary)
  • 50 flashcards (Novice)
  • 100 flashcards (Scholar)
  • 250 flashcards (Expert)
Feel free to download and use this zip of badges (ready made for this example app): flashcard_badges.zip
Next, head into the streaks page and set up a daily streak.
Head into the emails page and add and activate templates for the two types of emails we want.
  • Achievement unlocked emails
  • Recap emails (weekly)
Each email type has its own section—add a template under each and activate it to start sending.Trophy also gives us a preview of the emails which is nice. Plus, feel free to configure a nice logo and brand colors in the branding page. These settings are automatically used in all emails sent by Trophy.
Before you can start sending emails, you’ll need to configure your sending address with Trophy. But this can be done later on if preferred.

Integrating Trophy SDK

First we need to grab our API key from the Trophy integration page and add this as a server-side only environment variable.
Make sure you don’t expose your API key in client-side code
.env.local
Next, we’ll install the Trophy SDK:
Then whenever a user views a flashcard, we simply send an event to Trophy with details of the user that performed the action (which we’ll mock), and the number of flashcards they viewed (1 in this case). In NextJS we’ll do this with a server action that makes the call to Trophy to send the event, and we’ll call this action when the user moves to the next flashcard in the carousel. First, create the server action:
src/app/actions.ts
Then call it when the user views the next flashcard:
src/app/flashcards.tsx
We can validate this is working by checking the Trophy dashboard which should show our first user tracked in the Top Users table:
Next, we’ll add some UI to show off our gamification features in practice.

Adding Gamification UX

The response to the API call that we make to track events in Trophy helpfully gives us back any changes to the users progress as a result of that event:
Response
This includes:
  • The achievements array which is a list of newly unlocked achievements as a result of the event.
  • The currentStreak object which is the users most up to date streak data after the event has taken place.
This makes it really easy for us to react to changes in the users progress and do whatever we want. In this example, each time Trophy tells us a user has unlocked a new achievement, or extended their streak we’ll:
  • Show a pop-up toast
  • Play a sound effect

Achievement Unlocked Toasts

First, we’ll show a toast when users unlock new achievements. For this we need to add the sonner component from shadcn/ui to our project:
Then we’ll create the <Toast /> UI component we need to display toasts and a toast() utility function to trigger them:
src/lib/toast.tsx
Next, we need to update the page.tsx file with the main <Toaster /> component. This is the component from sonner which is responsible for displaying our toasts on the screen when we trigger them:
src/app/page.tsx
Next, to make sure NextJS shows our badges, we need to configure Trophy’s image host as a trusted domain. If you use custom badge URLs on your own domain or CDN, add those host names here too, or use a plain <img> and skip remote patterns.
next.config.ts
And finally, we update our <Flashcards /> component to read the response from Trophy and display toasts for any unlocked achievements:
src/app/flashcards.tsx
To see this in action, all we need to do is unlock our first achievement by viewing 10 flashcards:

Streak Extended Toasts

We’ll use the same methods to show similar toasts when a user extends their streak. As we’ve set up a daily streak in Trophy, this will trigger the first time a user views a flashcard each day.
If we wanted to experiment with a different streak cadence, like a weekly streak, then none of this code changes - the great thing about Trophy is everything can be configured from within the dashboard and doesn’t require any code changes.
All we need to do is read the currentStreak.extended property from Trophy and handle showing another toast with a new if statement:
src/app/flashcards.tsx
Now the first time a user views a flashcard each day, they’ll see one of our streak extended toasts:

Sound Effects

Gamification is first and foremost about increasing user retention. The best way to do this is to make the features we build as engaging as possible. A great way to do this that’s often overlooked is with sound effects. Here we’ll add two distinct sound effects for each case where we show a toast to further engage the user. This helps distinguish the different toasts and helps users build up an expectation of what each sound means. For this we’ll make use of the HTML5 Audio API and use sounds from freesounds.org.
The sounds used in this example are in the repository in the public/sounds directory. Feel free to use them or pick others you like!
To load the sound files into our application, we’ll create a ref for each one, then we simply call the play() method on each when we want to actually play the sound:
src/app/flashcards.tsx

Displaying Study Journey

The last piece of UI we’ll add will be a dialog to display the user’s study progress, including their streak and any achievements they’ve unlocked so far. First, we’ll add a couple of new server actions to fetch the users streak and achievements from Trophy. As we’re using a daily streak here, we’ll fetch the last 14 days of streak data from Trophy to give us enough to work with in our UI:
src/app/actions.ts
Then we’ll call these actions on the server when the page is requested:
src/app/page.tsx
Then we’ll create a new <StudyJourney /> component that takes in the achievements and streak data as props and renders it nicely in a dialog. Before adding this we need to add the shadcn/ui dialog component to our project, and while we’re at it, we’ll add the seperator component too:
We’ll also need dayjs to help us with displaying dates nicely as well:
Now we have everything we need to build our study journey component:
src/app/study-journey.tsx
Finally, we simply add this component to our page and we should be good to go:
src/app/page.tsx

Adding an XP System

Now let’s take our study platform to the next level by adding an XP (points) system. This will give users a sense of progression and reward them for their study activity.

Setting Up Points in Trophy

First, head to the Trophy points page and create a new points system. We’ll call ours “XP” with the key points.
Configure your points system to award XP for viewing flashcards. You can also set up bonus XP for streak milestones.

Integrating Points API

Add new server actions to fetch points data:
src/app/actions.ts

Creating a Points Context

To manage points state across the app, create a React context:
src/contexts/UserPointsContext.tsx

Building the Points Center UI

Create a points display component that shows the user’s XP with a satisfying number animation:
src/app/user-center/points-center/points-center.tsx

Updating Points on Flashcard View

Finally, re-fetch points whenever a user views a flashcard to show real-time XP updates:
src/app/flashcards.tsx
Now when users view flashcards, they’ll see their XP update in real-time with a satisfying animation!

Adding Leaderboards

Nothing drives engagement like friendly competition. Let’s add a leaderboard to show how users stack up against each other.

Setting Up Leaderboards in Trophy

Head to the Trophy leaderboards page and create a new leaderboard. We’ll create a daily leaderboard with the key daily-champions that ranks users by flashcards viewed.

Leaderboard API Integration

Add server actions for fetching leaderboard data:
src/app/actions.ts

Building the Leaderboard UI

Create a leaderboard component that displays rankings with pagination:
src/app/leaderboard-center/leaderboard-center.tsx
The leaderboard automatically updates as users study, creating a dynamic competitive environment that encourages daily engagement.

Adding an Energy System

Energy (or “lives”) systems are a proven retention mechanic that encourages users to return throughout the day. Let’s add one to our study platform.

Setting Up Energy in Trophy

Trophy’s points system is flexible enough to handle energy mechanics. Create a new points system with the key energy and configure it with:
  • A maximum cap (e.g., 5 energy)
  • Automatic regeneration rules
  • Costs per action (e.g., -1 energy per flashcard session)

Energy API Integration

Add server actions for energy management:
src/app/actions.ts

Creating an Energy Context

Similar to points, create a context for managing energy state:
src/contexts/UserEnergyContext.tsx

Building the Energy UI

Create an energy display that shows remaining energy with visual indicators:
src/app/energy-center/energy-center.tsx
With energy in place, users have a reason to return multiple times throughout the day as their energy regenerates, boosting your daily active users.

The Result

Congrats! If you’re reading this you made it to the end of the tutorial and built yourself a fully-functioning study platform. Of course there’s loads more we could do to this, so here’s a few ideas:
  • Persist flashcards to a database
  • Create multiple flashcard sets for other topics
  • Add authentication
  • Allow users to create their own flashcard sets
If you had fun or think you learned something along the way then give the repo a star on GitHub!

Get Support

Want to get in touch with the Trophy team? Reach out to us via email. We’re here to help!