alexs
25 October 2016 20:40
62
I appreciate the fact that you’re trying to find a compromise here so please excuse my persistence, I’m not being deliberately awkward here either but…
I wanted to present a third way: if you keep the Monzo-generated segregations as they are and allow users to tag transactions once only as a separate attribute on the data, then these custom categories are effectively distinct from Monzo’s, so they can still generate insights based on their categories while allowing the user to track their spend on whatever different metric they see fit in a first order way.
Users can already tag transactions via notes, for example -
In the meantime, my suggestion would be to tag these transactions. I’d recommend using emoji, rather than text to avoid typos & lower / upper character variations which will cause issues when you search for the ‘tag’, plus emoji are easier to spot when you’re scrolling through your transaction feed.#PP might be an idea (hashtags being the most likely prefix for custom tags if Mondo ever supports them).
I use emoji to group my transactions for spend on taxis
So while -
Not allowing multiple tags on a transaction nullifies the concerns about double-counting.
I adopt that approach too, the challenge here is that your transactions are often a mix of different categories so in most cases, this will only enable you to count purchases of certain things, rather than aggregate them.
I could be missing something there though…
On your second point, re-reading what I put it does come across a little harshly. I simply meant to add a note of caution that closing the book on something (in my view prematurely) would be a mistake given that I don’t fee the solution space has been fully explored.
I often struggle with that too!