Work

LET ME GO · CATEGORY · TYPE

LetMeGo: telling a stranger their car is in the way, without a confrontation.

LetMeGo lets someone notify a vehicle owner that their car is blocking a path — without exchanging phone numbers or having an awkward face-to-face. Built for Richinnovations, a two-week sprint covering both the mobile app and the website.

Engagement
Design sprint
Duration
2 weeks
Scope
Mobile app + website design.
Year
2025
HERO — PRODUCT OVERVIEW
01SECTION

LetMeGo solves a small, universal annoyance: someone's car is blocking your path, and you have no way to reach them without becoming the person banging on windows in a parking lot. Richinnovations brought Edwin in to design the mobile app and website — a two-week sprint, straight to UI, with the product concept and functionality already decided going in.

The core idea was already set: let a stranger notify a vehicle owner without exchanging phone numbers, without confrontation, without either side having to feel exposed. That's a genuinely different design problem from most consumer apps — the entire product has to work for two people who don't know each other and may never meet.

No research phase — same shape as the Infinium engagement: two weeks, brief to screens. Mobile app and website both in scope, delivered in 2025.

02WHAT WE FOUND

The direction here didn't come from formal user research — it came from the founder's own experience with the problem. Anyone who's stood next to a blocked car in a parking lot knows the moment: it's hot, you're in a hurry, and the last thing you need is a clunky app standing between you and getting moving again.

Based on the founder's own lived experience with the problem, not formal user interviews or competitive research. A real source of insight, but a narrower one — worth naming honestly rather than presenting as broader research than it was.

01

The user is already frustrated before they open the app

Nobody opens LetMeGo in a good mood. They're blocked, often in the heat, often already late for wherever they were going. That emotional starting point became the design brief's real constraint: the app had to get out of its own way.

02

Friction reads as failure in this specific moment

A flow that would feel merely "a bit clunky" in a normal app reads as actively broken here, because the user has zero patience reserve left. Every extra tap, every unclear step, compounds a frustration that's already peaking — which made flow speed and clarity the design's real success metric, not feature completeness.

IMAGE
04WHAT CHANGED

LetMeGo shipped and is live — covered by Mathrubhumi as a "Made in Kerala" product solving a problem every driver recognizes.

The app is published and available now, built by Richinnovations out of the K-SUM Technopark incubator in Thiruvananthapuram. Independent coverage from Mathrubhumi picked it up as a homegrown Kerala product tackling obstructive parking directly.

No usage numbers to report yet, but real, checkable proof of the thing existing and doing what it was designed to do — a working product covered by a Kerala news outlet, not a screen deck that never shipped.

05WHAT’S NEXT

The engagement ended when the two weeks did — screens delivered, no retainer with Richinnovations afterward. LetMeGo shipped and continues on as their product, built and maintained on their own from here.

Small app, one honest job — get out of your way.

A bruised banana is still a banana.

If you're mid-build and something feels off, that's usually the right time to look, not the wrong one. Twenty minutes. No deck. No proposal to sit through.

Broken doesn't mean beaten.

Book 20 minutes
Let Me GO — uxbubble case study