The Day Our Own App Failed… and I Took It Personally: Ritesh Sakhare

The ₹120 Moment That Hit Hard We were on a trek, tired and hungry, and like every good trip story it involved Maggi. One plate. ₹120. Naturally, I said: “Add it in Expenseek.” We opened the app. Created the entry. Selected members. Tapped save. Nothing happened. No network. And suddenly our “online group” wasn’t so powerful anymore. Production app. Founder standing there. Feature failed. I looked at Samyak. He looked at me. There was no dramatic music. Just silence. And in that silence, one thought: “Ritesh… this is personal now.” The Problem Was Bigger Than Maggi At that moment, I realized something important. Most apps are built online-first. Which means: No internet = No functionality. 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 architecture. Users won’t wait for network just to split ₹120. Money gets spent everywhere. Internet doesn’t exist everywhere. That mismatch bothered me deeply. If Expenseek is meant for real people in real situations, it must work even when the internet doesn’t. Rethinking the Architecture The solution sounded simple: “Let online groups work offline.” But technically? That’s not small. I redesigned the flow: Users can add expenses without internet. Data is stored locally using Async Storage. Each entry is marked as “Pending Sync.” A background listener constantly checks for network availability. The moment connectivity returns, a sync engine pushes the data securely to the server. Conflict handling ensures no duplication. All group members automatically see the updated expense. No errors. No lost entries. No Maggi politics. An online group that behaves intelligently offline. That contradiction became our strength. The Coorg Confirmation Later, when Samyak and I went to Coorg including Mandalpatti we tried other apps in low-network zones. They simply didn’t work. No offline group support. No smart syncing. No fallback logic. That’s when I felt proud. Not because we added a feature. But because we built something real. Something practical. Something tested in chaos not just in perfect WiFi conditions. What I Learned Some features are built from strategy. Some are built from research. Ours was built from a failed ₹120 Maggi entry. But that small failure reshaped how I think about systems. Today, Expenseek doesn’t just work online. It works in real life. And honestly? I’m grateful it failed that day. Because sometimes, your product breaking in front of you is the best thing that can happen to a founder. Ritesh Sakhare Co-Founder, Expenseek Builder in chaos Architect of Offline Online Groups