First of all, I’d like to personally thank you all for spending the time to provide us with valuable feedback. I can’t stress enough how impressed I am with this community. This might be my first post, but I’ve been reading this forum for some time now…
On to the questions now
Why have we got it, what is it for?
The second part of the question is easy. It’s a graph, providing you with information about past and projected usage of the Monzo account. The definition is vague on purpose, since this (just like any other feature of our app) will evolve and change over over time.
The first part is trickier, but is absolutely a fair question, and of course we’ve asked it internally several times as well. I guess to answer this, you need to think about what Monzo aims to provide. Among other things, we aim to provide people with accurate and timely information so that they can make the best possible financial decisions. A graph of your balance history seems like an obvious place to start, does it not? Sure, by itself, that doesn’t mean much, and is probably only useful to very few people. I can even get why you’d not want to spare precious screen space for that. But remember that this is just a starting point. Other information has already been added to that graph (like a projection of your future balance and a line describing when you’re in negative balance), and we will be adding even more to it over time.
This brings me nicely into the next very common question:
can we get rid of it by way of toggle switch in a settings menu perhaps?
I think @hugo’s response to this is spot-on, and I couldn’t agree with it more. Quite frankly, that’s not a sustainable way of building apps. First of all, if we provided toggles for different features, supporting the app (and all possible combinations of those toggles) would become a nightmare from a design, implementation and testing perspective. And this is not us thinking of ourselves, but also about users. We’d much rather spend time building new, exciting features to delight them, rather than spend time maintaining all the different combinations of toggles. Secondly, even if it is true that most people would prefer to have Pulse hidden in the form that it is now (which is debatable I think), there’s no way to know that about future iterations of it. But once a toggle is off, there’s no way for that user to ever see the new iterations. Of course, that just means that the onus is on us to make this something that everybody (or at least most users) are excited to have. And of course, we think we’re up to the task