{"slug": "i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type", "title": "I Built an AI Expense Tracker That Understands the Way People Actually Type", "summary": "A developer built Vitmora, an AI expense tracker that understands natural, multilingual input instead of requiring fixed formats. The app can interpret mixed-language sentences like \"Petrol ke liye 300 pay kiya\" or \"500 रुपये का पेट्रोल भराया\" to automatically categorize expenses. Vitmora aims to eliminate the friction of traditional expense tracking by adapting to how people actually type.", "body_md": "I Built an AI Expense Tracker That Understands the Way People Actually Type\n\nMost expense tracking apps expect users to type in a fixed format.\n\nBut real people don’t track expenses like that.\n\nSome people type:\n\n“Paid 100 for petrol”\n\nSome type:\n\n“500 रुपये का पेट्रोल भराया”\n\nOthers naturally mix languages:\n\n“Petrol ke liye 300 pay kiya”\n\nAnd sometimes people combine everything together in a single sentence.\n\nMost expense trackers completely fail at understanding this.\n\nThat’s the problem I wanted to solve while building Vitmora.\n\nThe Problem With Traditional Expense Tracking\n\nI’ve tried many expense tracking apps over the years.\n\nMost of them were good at charts, dashboards, and reports.\n\nBut almost all of them had the same problem:\n\nThey expected users to adapt to the app.\n\nYou usually have to:\n\nAfter a few days, it starts feeling like work.\n\nAnd honestly, most people stop tracking because of that friction.\n\nBut there was another problem I kept noticing.\n\nLanguage.\n\nPeople Don’t Think About Money in One Language\n\nIn countries like India especially, people naturally switch between languages while typing.\n\nSometimes it’s English.\n\nSometimes Hindi.\n\nSometimes Hinglish.\n\nSometimes regional languages.\n\nAnd most of the time, it’s mixed naturally.\n\nThat’s how people actually communicate.\n\nFor example:\n\nThese all mean something very clear to humans.\n\nBut most apps struggle to understand them.\n\nThat’s where the idea behind Vitmora started.\n\nThe Goal Was Simple\n\nI didn’t want users to learn how to use the app.\n\nI wanted the app to understand users naturally.\n\nInstead of structured forms, the experience should feel more like chatting.\n\nJust type normally.\n\nVitmora should figure out:\n\nautomatically.\n\nBuilding Multilingual Expense Understanding\n\nThis turned out to be much harder than it sounds.\n\nBecause users don’t type consistently.\n\nFor example:\n\n“Petrol ke liye 300 diye”\n\n“Petrol bharaya 500”\n\n“500 ka fuel”\n\n“Bike me petrol 200”\n\nAll of these technically describe the same kind of expense.\n\nThen there’s mixed language input.\n\nA single sentence might contain:\n\nAnd users still expect the app to understand them instantly.\n\nThat became one of the biggest product and engineering challenges while building Vitmora.\n\nUnderstanding Intent Instead of Perfect Grammar\n\nOne thing I realized very quickly:\n\nPeople don’t type for machines.\n\nThey type for convenience.\n\nNobody wants to stop and think:\n\n“Am I formatting this correctly?”\n\nThe app should understand intent even if the sentence isn’t perfect.\n\nFor example:\n\n| User Input | What Vitmora Understands |\n|---|---|\n| Paid 100 for petrol | Fuel expense |\n| 500 रुपये का पेट्रोल भराया | Fuel expense |\n| Uber ke liye 300 pay kiya | Travel expense |\n| Swiggy order 450 paid by UPI | Food delivery + UPI |\n| Coffee 120 with card | Food & card payment |\n\nThat flexibility completely changes the feeling of expense tracking.\n\nIt starts feeling natural instead of robotic.\n\nThe Bigger UX Lesson\n\nWhile building this, I realized something important:\n\nMost software still expects humans to behave like software.\n\nBut real communication is messy.\n\nPeople switch languages.\n\nUse shortcuts.\n\nMix sentences.\n\nMisspell words.\n\nType casually.\n\nAnd honestly, that’s normal.\n\nTechnology should adapt to people — not the other way around.\n\nQuick Demo\n\nI recently recorded a small demo showing how Vitmora understands different styles of expense entries in real time.\n\nDemo Video - [https://www.youtube.com/shorts/p06VeqzKGNA](https://www.youtube.com/shorts/p06VeqzKGNA)\n\nExamples used in the demo:\n\nThe goal wasn’t just multilingual support.\n\nThe goal was making expense tracking feel effortless.\n\nWhat’s Next\n\nVitmora is still evolving, and there’s a lot more I want to improve around:\n\nBut this idea of “track expenses the way people naturally speak” has become one of the core philosophies behind the product.\n\nBecause managing money shouldn’t require perfect formatting or perfect English.\n\nIt should feel natural.\n\nThanks for reading.\n\nWould genuinely love feedback from developers, builders, and anyone interested in AI, multilingual UX, or personal finance tools.\n\nYou can check out Vitmora here: [https://vitmora.com](https://vitmora.com)", "url": "https://wpnews.pro/news/i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type", "canonical_source": "https://dev.to/diveshjain25/i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type-3oma", "published_at": "2026-05-27 06:16:47+00:00", "updated_at": "2026-05-27 06:22:33.581583+00:00", "lang": "en", "topics": ["ai-products", "natural-language-processing", "ai-startups", "ai-tools", "generative-ai"], "entities": ["Vitmora"], "alternates": {"html": "https://wpnews.pro/news/i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type", "markdown": "https://wpnews.pro/news/i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type.md", "text": "https://wpnews.pro/news/i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type.txt", "jsonld": "https://wpnews.pro/news/i-built-an-ai-expense-tracker-that-understands-the-way-people-actually-type.jsonld"}}