- To
- Product teams, and engineering teams that care about product
- From
- Uvesh Menpurwala
- Re
- How I decide what to build
- Updated
- Oct 2025
Product judgement, with the engineering to ship it.
Taking products from proof of concept to release.
TL;DR 1
5 case studies
Products I worked on: the problem, the calls I made, and what changed.
01Start from the journey
From SyncIT. Scrub through it.
- Connect
- Download
- Review
- Report
- Configure
They
Pairs the instrument over BLE, Wi-Fi/LAN or serial
It hurts
A different app per instrument family
The fix
One app for every supported instrument
02The calls that mattered
What was on the table, what I chose, and why.
- Maintain each app
- One cross-platform product(chosen)
Why: One product is simpler for customers and gives one roadmap instead of several.
from SyncIT →
03Before and after
From SpeakUp. Drag to compare.
before
Typical language app
- Needs a connection
- Account before the first lesson
- Often a subscription
after
SpeakUp
- Works fully offline
- No account
- Record and play back on the device
04All the work
Case studies, teardowns and proposals, newest first.
- Case studyOct 2025SyncITA cross-platform Flutter platform for Sensit’s gas-detection instruments that consolidates several legacy apps into one product, in two tiers: Lite for offline field use and Plus with cloud sync, reporting and integrations.journeydecisionsbefore/after
- Case studyOdigoAn advertising robot with two mirrored displays and central control, with its app built in Flutter on ROS SDK, platform channels and Socket.IO.
- Case studyDasherA delivery robot with nine integrated display panels. I built the advertisement panel, with dynamic content scheduling and remote file transfer to the robot.decisions
- Case studySpeakUpAn offline-first Flutter app for practising spoken English in timed card-draw sessions. No account and no internet needed.decisionsbefore/after
- Case studyQuickServeA two-sided home-services marketplace: a Flutter app where customers book and pay for a service, and a Spring Boot backend that dispatches each order to service partners.journeydecisions
Want to talk it through?
I’m happy to walk through any of these in more depth, including the parts that didn’t work.
uveshmenpur.03@gmail.com— Uvesh Menpurwala