Skip to content
All work
Mobile

GlimpseGems

A mood-based city discovery app, designed end to end — from first sign-in to a saved, shareable list.

Role
Product design and full-stack development
Timeline
2025
Stack
  • React Native
  • TypeScript
  • Supabase
  • Tailwind CSS
  • Geospatial filtering
Links
Not publicly available

In short

Problem
Discovery apps rank what is popular; few help you find a place that fits how you want to feel.
My contribution
Product design and full-stack development, from onboarding to a saved, shareable list.
Key decision
Saved places carry explicit state — Favorites, To Visit, Visited — because those are three different intentions.
Outcome
A React Native app with mood categories, filtering, map and list views, stateful saves and achievements.

The problem

What was broken, for whom

Recommendation apps are good at showing you what's popular; they're worse at matching a place to a mood. Wanting somewhere quiet to focus, somewhere romantic, or somewhere to celebrate is a different search than 'restaurants near me' — most apps don't have a category for it.

Context & constraints

GlimpseGems is a location-based discovery app built around mood rather than cuisine or price. The product bet is that people already know how they want to feel on an outing before they know where they want to go.

My role

What I actually did

Product design and full-stack development — the entire flow from onboarding through to a saved, shareable collection.

Product design

What I designed, flow by flow

Onboarding
Social sign-in first with email as a fallback, then a short coach-mark tour on first use of Explore instead of a tutorial up front.
Search & discovery
Seven mood categories — Savor, Focus, Unwind, Energize, Celebrate, Romance, Nightlife — plus a general Explore, with hidden picks surfaced separately from trending places.
Map / list
Explore has both views: a map for what is nearby, a list for what looks interesting. The coach marks explain the map's less obvious affordances — glowing pins for hidden picks, the recenter button.
Filtering
Each category deep-dive filters by cuisine type, budget, live music, parking and more.
Saved states
Favorites, To Visit and Visited are separate states, and one place can hold more than one at once.
Gamification
Achievement badges on the profile, with unearned badges shown in a locked state rather than hidden.

Key decisions

Trade-offs made on purpose

  1. Decision 01

    Saved places have explicit state — Favorites, To Visit, Visited — not one flat list

    Why: Wanting to remember a place, planning to go and having already been are different intentions, and shouldn't share one bucket.

  2. Decision 02

    Explore has both a list and a map view

    Why: Deciding what is nearby and deciding what looks interesting are different tasks — a map answers the first, a ranked list the second.

  3. Decision 03

    A short coach-mark tour on first use of Explore, not a long tutorial up front

    Why: The map's less obvious affordances — glowing pins for hidden picks, the recenter button — get explained exactly when a user would otherwise be confused by them.

  4. Decision 04

    Unearned achievement badges show in a locked state instead of being hidden

    Why: Showing what is still achievable makes a gamification layer feel like progress rather than a hidden scoreboard.

The product flow

From first sign-in to a saved list, screen by screen

GlimpseGems sign-in screen with social auth options
01 · Sign inSocial sign-in first, email as a fallback — the shortest path to the first screen
GlimpseGems home screen with mood-based category chips
02 · Choose a moodSearch sits on top, but the seven mood categories are the main way in
GlimpseGems Savor category with filters
03 · FilterInside a category: filters for cuisine, budget, live music, parking and more
GlimpseGems Explore screen with list and map toggle
04 · ExploreTrending, Nearby, New and Hidden Picks tabs, with a List / Map toggle — two tasks, two views
GlimpseGems map view onboarding guide
05 · Learn the mapFirst visit to the map: a coach mark explains glowing pins and the recenter button in place
GlimpseGems saved collection with Favorites, To Visit and Visited states
06 · SaveSaved places filter by Favorites, To Visit and Visited — one place can be in more than one
GlimpseGems gamified profile screen with achievement badges
07 · Track progressAchievements on the profile, with locked badges visible so there is something to work towards

For the technical reader

Technical implementation

The solution

How it works

A React Native app on Supabase: social or email sign-in, a home screen organised around seven mood categories (Savor, Focus, Unwind, Energize, Celebrate, Romance, Nightlife) plus a general Explore, and a category deep-dive with real filtering — cuisine type, budget, live music, parking, and more. Explore supports both a list and a map view, with 'hidden picks' surfaced separately from trending places. A Saved section tracks each place's state — Favorites, To Visit, Visited — so a list isn't just a bookmark pile, it reflects where a user actually is in deciding to go somewhere.

Stack

What, and why

React Native
one codebase for the whole app, native performance for map interaction and gestures
Supabase
Postgres, auth and geospatial queries without standing up a separate backend service
Tailwind CSS
kept the mood-based category system visually consistent — seven categories with seven colour identities, defined once as tokens rather than hand-picked per screen

Challenges

What broke, and what I'd change

  • Seven mood categories is a lot of surface area to keep visually distinct without the app looking chaotic — the category colour system had to carry meaning (Energize reads differently from Unwind) while staying inside one coherent palette. That balance took more design iteration than any single screen
  • Save-state modelling (Favorites / To Visit / Visited) is simple to describe and easy to get wrong in the data model — a place needs to be able to hold more than one state at once (favorited and visited), which shaped the schema more than I expected going in

What I learned

Onboarding that explains a feature at the moment it's needed, instead of up front, is more work to build — you need state to know what the user hasn't seen yet — but it's the difference between a tutorial people skip and one that actually lands.

More work

Fintech

CIB Digital Banking

Payment features that clear compliance and ship to a national bank's customers.

  • Node.js
  • NestJS
  • REST API design
  • React
  • +3

Read case study

Hardware & IoTHonorable Mention — ETH Zurich

RescueTap

One tap — or a detected fall — sends a caregiver your exact location.

  • Python
  • Raspberry Pi 4
  • MPU-6050 / I2C
  • Twilio WhatsApp API
  • +2

Read case study

Contact

Have a problem worth solving?

I'm open to Software Engineer and Product Engineer roles — remote, or relocating. Based in Cairo, EET (UTC+2).