Web Version Didn’t Make Sense -

I initially explored a web app, but quickly realised loyalty sits in moments - quick checks, redemptions, check-ins at the venue.

Mobile was the natural home.
So I restarted with mobile-first logic.

AI-Augmented Workflow -

AI wasn’t a shortcut. It was a thinking amplifier.

I used:

ChatGPT for initial flow mapping & ideation

Claude + Lovable for UI iteration feedback

HTML-to-Figma plugin to speed screen layout framing

I refined outputs manually, not blindly. The AI served as a fast-draft layer while my judgment shaped the actual product.

This accelerated ideation and gave me more time for behavioural depth.

This is one of the screens generated by ChatGPT in response to my prompt.

This is from Claude using code generated from ChatGPT

More AI prompting to refine the colours and flow

Design Execution

1. Progress that feels alive:

   Added an avatar that moves along the progress bar
   → makes growth feel physical, not numerical.

   
   

   

   
   

2. Gamified earning flow:

   Users manually claim points
   → reinforces reward ownership (like gaming mechanics)

   *This actually animates so that when the button is clicked, confetti pops out. Users can also share their achievements

3. Quests:

   One of Last Card’s biggest reels was prize-driven - people liked rewards.

   So I turned that into behaviour:

   Users earn extra points for completing quests such as sharing a post ABOUT Last Card.

   For this kind of quest I mentioned as an example, visibility becomes a feature, not a hope.

   → boosts organic awareness and real loyalty

4. Future iteration: Diamonds currency:

Points work. Diamonds mean something.

Diamonds tie the brand to “Last Card,” which is a play on words.
They feel earned, limited, and worth keeping.

This feature is planned for the next sprint, but the foundation is ready for an upgrade.

5. Timed retention logic:

In future sprints, inactivity resets progress

No check-ins for 1–3 months → progress resets.

This recreates Duolingo + AliExpress behavioural loops.
→ drives habit through loss aversion

6. UX Details That Matter:

Manual claim → increases ownership.

Unclaimed-tag → visibility of reward opportunity.

Tier perception → designed to create gentle FOMO.

First log-in → automatic starter points for momentum.

Support → WhatsApp • Instagram • Email • Address only.

Push notifications for events - keeps the community alive.

The Flow

User enters venue → Plays / Eats / Orders
↓
Staff logs activity → User opens app
↓
Points update appears + manual claim
↓
User redeems reward → Modal confirmation → Return behaviour reinforced

Taking It Further With an Internal Admin Accounting Tool: The Engine that Makes Rewards Possible

For a loyalty system to work, rewards must be earned, not assumed.

During flow mapping, I identified a risk:

If staff couldn’t log what each customer bought or played,
points would become guesswork, not behaviour tracking.

And do you remember the question I asked on WhatsApp? The screen is above, just under the kickoff section. Customers having to inform the admin themselves of their purchases wasn't a good experience too.

So I designed a lightweight internal accounting app for staff and management.
It links revenue → user identity → reward accuracy.

This tool allows teams to:

✔ Log food & drink orders
✔ Assign purchases to a customer profile
✔ Track gameplay sessions + time spent
✔ Input payments + record spend totals
✔ Generate and export data used to calculate reward points

Instead of manually guessing or marking attendance, the system now has proof, structure, and traceability.

This is where the product truly became a retention ecosystem, not just an app.

Why this mattered

Without an internal logging system:

With the admin tool in place:

Mobile Screens

Desktop Screens