Case Study

SigNusk

Signusk is a bilingual UX experience designed to help Hajj &
Umrah pilgrims stay connected and navigate large crowds safely.

ROLE
UI Designer & Product Contributor
PLATFORM
iOS · Android
STATUS
In Development
YEAR
2025
The Problem

Lost in a crowd of millions

Every year, more than 2 million pilgrims gathe in Makkah. They travel in groups — sometimes 200 people. But there was no reliable way to know if someone was drifting away — until it was too late

Quote

A group of 100 pilgrims.  A crowd of 2 million people. One leader. No tool.

The Solution

Real-time visibility. For every member

Every year, more than 2 million pilgrims gathe in Makkah. They travel in groups — sometimes 200 people. But there was no reliable way to know if someone was drifting away — until it was too late

SigNusk app hero mockup
Bluetooth tag on every member's wrist
Live GPS map of Makkah — AR/EN
3 status levels : Nearby · Distant · Unreachable
The process
01

User Flow & Architecture

Before opening Figma, I mapped the complete app architectureto align the entire team on scope and navigation.
The user flow focuses on three key actions:
Join group → Track members → Navigate together

SigNusk user flow and app architecture
02

MoSCoW Prioritization

To define a clear MVP and avoid scope creep, I ran a MoSCoWsession with the team — separating what the app must do fromwhat can wait for V2.

SigNusk MoSCoW prioritization session

Must Have

Team overview · Hub state Login · Member list · Map

Should Have

Team overview · Hub state Login · Member list · Map

Could Have

Wealth information  Fetwa per step of Hajj

Will Not Have

Out of scope for V1

03

UI Design with Gluestack

The interface was built using the Gluestack design system
to ensure scalability and efficient developer handoff.

SigNusk mobile app UI screens
The process
01

Color coding for universal understanding

Green = safe · Orange = warning · Red = danger. No text needed to understand the status. Works across all languages and literacy levels.

02

Bilingual AR/EN from screen one

The language switcher is visible on screen 1 — not buried in settings. For pilgrims from 180+ countries, language access is a safety feature

03

Timestamp on every member

"6m Ago" vs "Now" — a small detail that makes the difference between calm and panic.

04

Battery indicator on each tag

A dead tag = an invisible member. Showing battery level proactively prevents the worst case scenario.

05

Gluestack UI for dev handoff

Every screen was designed to be buildable — no design-dev gap. Faster handoff. Fewer surprises in production.

Learnings

Designing for safety means every pixel matters. One missing alert = one lost person.

Simplicity is a safety feature
Color is a universal language
Real-time data needs trust indicators
Multinational design starts from screen one
MoSCoW saved the team weeks of work