The ₹120 Maggi That Built Expenseek’s Smartest Feature
While trekking during our production phase, Expenseek failed to add a simple Maggi bill because there was no network. That moment pushed me to build Offline-First Online Groups one of the strongest features of our app today.
The ₹120 Moment That Hit Hard
We were on a trek — tired, hungry, and like every great trip story, it involved Maggi.
One plate. ₹120.
Naturally, I said: “Add it in Expenseek.”
We opened the app. Created the expense. Selected group members. Tapped Save.
Nothing happened.
No network.
And suddenly, our “online group” wasn’t so powerful anymore.
This wasn’t just any moment:
A production app
A real user scenario
And the founder standing right there
I looked at Samyak. He looked at me.
No dramatic music. Just silence.
And in that silence, one thought hit hard:
“Ritesh… this is personal now.” The Real Problem: Apps That Don’t Work Without Internet
That ₹120 Maggi exposed a much bigger issue.
Most expense tracking apps are built online-first.
Which means:
No internet = No functionality
No connectivity = Broken experience
But real life doesn’t work like that.
Treks don’t come with WiFi
Trips don’t guarantee 5G
Rural areas don’t care about your backend
Users won’t wait for network to split ₹120
Money gets spent everywhere. Internet doesn’t exist everywhere.
That mismatch became impossible to ignore.
Why Expenseek Needed an Offline-First System
If Expenseek is built for real people in real situations, it must:
Work in low-network zones
Handle expenses instantly
Sync data without user effort
Never lose transactions
That’s when I decided:
“Expenseek shouldn’t depend on the internet. It should adapt to it.”
Building Offline-First Group Expense Tracking
The idea sounded simple:
“Let online groups work offline.”
But technically? It required a complete rethink.
Here’s how we built it:
Users can add expenses without internet
Data is stored locally using Async Storage
Each entry is tagged as Pending Sync
A background system detects network availability
Once online, a sync engine pushes data to the server
Smart conflict handling prevents duplication
Group members automatically receive updates
The Result:
No failed entries
No data loss
No user frustration
No “who paid for Maggi?” arguments
An online group that behaves intelligently offline.
Testing in Real Conditions: The Coorg Trip
Later, during our trip to Coorg — including Mandalpatti — we tested other expense apps in low-network areas.
They failed.
No offline support
No smart syncing
No fallback system
That’s when I realized:
We didn’t just build a feature. We solved a real-world problem.
What This ₹120 Failure Taught Me
Some features come from:
Market research
Product strategy
User feedback
But this one?
It came from a failed Maggi entry.
And it changed everything.
Key Lessons:
Real-world testing beats perfect lab conditions
Offline-first is not optional — it’s essential
Small failures can lead to big product breakthroughs
User experience matters more than technical assumptions
Expenseek Today: Built for Real Life
Today, Expenseek is not just another expense-splitting app.
It is:
Built for travel
Designed for low connectivity
Reliable in unpredictable environments
Created from real user pain
It doesn’t just work online. It works in real life.
Final Thought
Looking back, I’m grateful that ₹120 entry failed.
Because sometimes, your product breaking in front of you is the best thing that can happen to a founder.
About the Author
Ritesh Sakhare Co-Founder, Expenseek, Connect on LinkedIn