Open a standard budgeting app for the first time and you will be asked, within the first two screens, to select your currency. The dropdown is long. The selection feels important. Here is the thing about currency selection: if you are tracking narratively rather than calculating, it is completely unnecessary.
The entry "groceries $127" and "groceries ₹8,400" and "groceries €112" are all equally valid money journal entries. The currency symbol is part of the story, embedded in the text where it belongs. No setting required.
What currency settings reveal about app philosophy
The requirement to select a currency reveals the underlying model: the app is designed for calculation. The currency setting exists because the app is going to do math — sum amounts, compare them, chart them in a consistent unit. For a narrative model, currency is just another part of the description. "Dinner ₹2,400, expensive, worth it" doesn't need a currency setting to be valid.
No currency setting. No configuration. Just type what you spent. Free forever.
The digital nomad case and simplicity as feature
For anyone earning or spending across multiple currencies — freelancers with international clients, expats, frequent travelers — the single-currency requirement of standard budget apps is a genuine problem. The narrative entry handles this naturally: "coffee €4, about $4.40, grabbed at the airport." Every setting removed is a decision the user doesn't have to make. Every decision not made is friction eliminated. moneytyping has no currency setting not because we forgot — because the narrative model doesn't need one.