AI Product Strategy · Responsible Intelligence · Android
DHRUVA
Your constant in motion.
A journey-aware travel companion designed around arrival, assistance and consent-first safety.
Developed for Android · Submitted for Play Store review
I wasn't trying to build a travel product.
I was trying not to miss my stop.
Long journeys are rare moments to disconnect. One thought stays quietly in the background.
Traditional alarms understand when. Travel problems often depend on where.
Different travellers.
Same underlying need.
Confidence during the journey.
Students travel overnight. Professionals commute exhausted. Parents travel alone. Families worry in silence.
"Can I sleep until my station?"
Overnight routes
I saw the whitespace between navigation and arrival.
Travellers already know where they are going. The opportunity is helping them remain confident while getting there.
Tap Travel below to see where the gap exists.
ARRIVE
Wake me when the journey matters again.
Choose a destination. Decide how far before arrival. Start. Put the phone away. Not replacing Maps — reducing the need to continuously look at Maps.
Destination selected
Then I stopped thinking only about myself.
What if this was my parent travelling alone?
Could I prepare the journey for them?
And if I can help them...
does that mean I should be allowed to track them?
Tap to see what tracking would have meant.
Family is a relationship.
Permission is a product decision.
Relationship is separated from permission. Permission is separated from temporary context. The traveller stays in control.
Relationship is separated from permission. The traveller stays in control.
Three pillars. One human principle.
Travel assistance when you need it. Privacy when you don't.
Wake me when the journey matters again.
Choose where, how, and how early. The rest disappears into the background — designed for tunnels, weak signals and imperfect connectivity.
Destination set
Alert 1.2 km before arrival
A system should communicate what actually happened.
Not what we hope happened.
Now you know it is actually ready on the traveller's device.
Arrival wasn't the only uncertainty.
What if the journey moves away?
What if it stops unexpectedly?
What if connectivity disappears?
The obvious solution was continuous tracking.
I chose a different approach.
PROTECT
Additional awareness only when the traveller chooses it.
Journey Safety begins with the traveller's decision. It ends when the journey completes.
Origin
Mumbai CST
Destination
Pune Junction
Travel Mode
Train
Expected Arrival
11:45 PM
Trusted Guardian
Priya (Sister)
Journey Safety
Tap to start
Intelligence should reduce noise — not create fear.
One inaccurate GPS point jumps away. No alert. Normal points follow. Nothing happens. Only when several points consistently suggest a different story — the interface reacts.
Journey proceeding normally
Safety check · Interactive demo
Are you safe?
Your journey appears to be moving away from the expected route.
The system contributes context. The person keeps agency.
Observations are not conclusions.
Location intelligence can identify unusual movement. It cannot automatically explain why it happened.
Tap either card to see its effect on the traveller.
I didn't ask where can I add AI.
I asked where can intelligence improve a human decision.
Intelligence should reduce noise — not create fear.
Product direction
These represent product direction — not all necessarily current functionality.
AI accelerated execution.
It didn't replace product judgment.
Advanced technology matters only when ordinary people can use it.
Complexity belongs inside the product — not with the traveller.
DHRUVA
Four decisions.
Everything else stays out of the way.
Real products live outside the happy path.
The journey continues through tunnels, low battery, GPS noise, app restarts and patchy connectivity.
Good signal
Journey state clear and current.
Principles
Put responsibility where it creates the best product outcome.
Signal → Context → Understanding
Intelligence helps DHRUVA understand when to help. The traveller still decides how.
Consent drives architecture
The trust model is not a UI decision — it is built into how data flows through the system.
Accessibility also has an economic side.
I deliberately questioned whether functionality required cloud infrastructure or could happen reliably on-device. Affordability is part of accessibility.
Product
Tap each principle to explore the trade-off behind it.
Start with one real problem.
Understand how far that behaviour can travel.
One Traveller
Current Product
Family
Adjacent Opportunity
Assisted Travel
Longer Horizon
Mobility Ecosystem
Long-term Possibility
Downloads would not be my North Star.
Confident journeys — not installs — would tell me whether Dhruva was working.
Confident Journeys
North Star
Tap any metric to see what it measures.
Features should earn their place.
Not every idea becomes a feature. Try the decision gate.
Question 1 of 7
Real problem?
NO.
Limits can make a product more trustworthy.
AI Product Leadership is connecting decisions — not owning only one of them.
Select each node to explore how these connect in practice.
Select a node to explore
DHRUVA
Your constant in motion.
Dhruva represents the idea of a constant reference while everything around it moves. That felt right for a product designed to quietly help travellers remain aware through changing journeys.
A quiet point of confidence through the journey.
Developed for Android · Submitted for Play Store review
I don't want Dhruva to become another app travellers constantly manage.
I want it to become something they trust enough to stop thinking about.
Technology should support the journey — not become the journey.
JOURNEY COMPLETE
DHRUVA
Arrive with confidence. Stay connected by choice. Use intelligence with purpose.