top of page
Logo with MArgins.png
A commuter wearing the UrbiePack (experience design)

URBIEPACK: A 2015 → 2025 Retrospective

URBIEPACK was my attempt to solve a real commuter tension: people need their belongings to be both secure and quick to reach. The project taught me how physical design, behaviour, and constraints shape user experience long before I began working in tech.

What City Commuters Need

Urban commuters face a paradox: they must protect their belongings from theft in crowded spaces, but they also need effortless access to essentials like transit cards, headphones, or wallets. Most bags optimize for one or the other, rarely both.
URBIEPACK aimed to bridge that gap.

Research phase 1:
Cultural Probes

Category 1: things that need to be accessed easily during commute. like water bottles, ipods, phone, wallet or kes.
Category 2: things that need extra security when commuting
Nothing
Cultural Probe sample of what's in a user's backpack.

I asked my Instagram followers to share photos of what they carry. 75 people responded.

I categorized their items into two groups: what they access frequently and what they protect the most.

The pattern was clear: the things commuters reach for constantly are often stored in the same pockets as their most valuable items.

That tension became the core design problem URBIEPACK needed to solve.

Cultural probe sample of what's in a user's backpack, thermos, wallet, keys, and things that need to be reached easily

Ethnographic Observations

I spent time observing commuters on public transit. I noticed:

ethno.jpeg
People hold backpacks on their chest when a train gets crowded
ethno2.jpeg
Commuters develop rituals based on level of crowd
ethno 3.jpeg
Bags swing behind, making zippers extremely vulnerable

Design Explorations

Early Sketches / Rejected Ideas
I explored several directions:

  • Built-in hard-lock systems: too heavy and visually aggressive

  • Fully front-loading backpack: great accessibility, poor security

  • Side zipper concepts: fast access but easy to pickpocket

  • Hidden swivel pockets: strong security but overly complex

Each concept failed by leaning too far in one direction.

Trade-off Analysis
Ultimately, I realized the most viable design would require a combined mechanism: security features integrated with on-body accessibility, instead of separating the two.

Sketches of various backpack designs
Exploratory Sketches for an anti-theft, but accessible for the user backpack

Final Concept: Stopper System + Vest Integration

The final design paired a mechanical stopper (to lock the top flap and restrict opening) with a wearable vest that stabilizes the bag against the body.

This delivered:

  • Hands-free stability

  • Restriction of unauthorized access behind the user

  • The ability to access items without fully removing the bag

Layouts & Features

  • Laptop sleeve close to the back for security + weight distribution

  • Quick-access pockets on the front panel for items used frequently

  • Vest straps that shift weight and bring pockets closer to the body

Prototype
Final pictures of the UrbiePack prototype
Hero image of a user wearing the UrbiePack prototype in transit
Explanation of the stopper system

What I Learned & What I’d Do Differently Now

Looking back with my UX + product design mindset today I would make a few changes:

Design & Materials

  • I would push materials research further (cut-proof textiles, waterproofing, hidden seams).

  • I’d explore modularity so users can customize accessibility vs security levels.

User Testing

  • I’d conduct real-time commuter testing: getting on/off buses, navigating crowds, adjusting straps.

  • I’d gather feedback on the stopper mechanism’s usability under pressure.

Manufacturing Feasibility

  • I’d simplify the vest system for cost-effective production.

  • I’d revise the pattern to reduce sewing complexity and material waste.

Experience Design

  • I now see URBIEPACK not just as a bag, but as an experience ecosystem — security rituals, micro-interactions, and emotional comfort all matter.

  • I’d focus more on the journey than the hardware.

bottom of page