ATM use abroad fee decision was solely a community decision.
Other things reprioritised or changed due to community input - pots, fingerprint privacy for Android (brought ahead of payment only due to forum input), CASS, Coin Jar, profile photos.
ATM use abroad fee decision was solely a community decision.
Other things reprioritised or changed due to community input - pots, fingerprint privacy for Android (brought ahead of payment only due to forum input), CASS, Coin Jar, profile photos.
“…NOTHING has changed”…“apart from keeping up with industry”
But that’s every high street bank, and also HSBC were an Apple Pay launch partner. Their new App is also getting regular updates. Monzo had the first three because the technology was already ubiquitous and easy to implement. Ironic considering Apple Pay and Paym are too. You can’t compare the two considering HSBC also offer student accounts, credit cards and actually reasonable interest rates for overdrafts. Sounds like cognitive dissonance?
Guys I wasn’t saying Monzo hasn’t changed. Obviously it has. I was saying forum hasn’t had a big effect on what that change was. It probably would have been pretty similar without the forum.
I think it had an impact - but we are still a minority, representing around 1% of customers.
So they can’t just take everything we say and implement it, while other (non-members) might not like it.
But they can take an idea, perform user research, and if it is well received, implement it.
Well you can’t exactly engage with legacy banks on the same level can you?
Let’s face it, every suggestion has 20 counter suggestions and variations, ranging from ‘I love it’, ‘I hate it’, ‘i want a toggle switch’ to ‘leave it as it is’. Democracy can only go far, a benevolent dictator is needed in the end
The original name of the thread was along the lines of “The Monzo team is too slow” and it’s newly moderated name is really lame I have a different opinion to the OP (and have shared it) but he should be allowed to say it without having his words adjusted. Please change it back to what it was.
When I joined the Monzo prepaid beta in April 2016 I was really impressed with the functionality that was offered for a beta and the rate of change. I think Monzo’s size (both in product and customer base) allowed them to be very nimble.
I find it frustrating sometimes now when the Monzo community simultaneously defends the pace of the product changes because Monzo is small/new and yet also thinks the fintech/startup approach will allow for “innovation” over “legacy” banks.
If the prepaid/current account crossover was a big distraction what will it be like when Monzo is offering other functionality? Won’t joint accounts, overdrafts, marketplace technology, integrations with other services or offers/discounts be just as intensive? Legacy banks provide so many more services than Monzo and some of them are starting to compete with some of what Monzo offers…
I’m a developer myself, I understand that not all of the above functionality requires the attention of all of the workforce but there are shared bottlenecks: developers, designers, business relations, finance experts and customer operations to support it. I think it will be a long while before some of the stuff we want is delivered.
Sometimes I think the prepaid beta went too big too early. But the value of the marketing boost is probably worth a few annoyed early adopters
Let’s find out why?
Ok well the only way that would happen is for Monzo to actually tell us but they won’t so if it was monzo that added that bit to the title then it was a bit pointless and as @rarther has just said OP should be allowed to say it without having their words adjusted.
Poor show changing the title imo.
I think the difference between supporting more functionality and combined support of the current account and prepaid offering is that you have to implement everything twice - once for the prepaid, and once for the current account. Only time will tell, but the April updates looks more in-depth compared to previous months, so it seems like a plausible explanation.
But it was explained by @cookywook that he didn’t think it was. Everyone else had been explaining why they thinking is it isn’t So it’s accurate.
Ps why are we randomly choosing the male pronoun for the OP?
What is “he” a she? If not then there’s no problem.
I don’t know, do you?
They may not be a he or she, but something else so refering to them by their username (Siri) is the best option
I’m looking into the changing of the topic title.
No staff or leaders adjusted the title of this post. It was changed by a regular member.
In all honesty I kind of agree with the op. Perhaps without the insulting rethoric. But genuinely I would be interested in an explanation as to why features that sound easy to implement to a lay person like me are clearly way more complicated.
For the record I know nothing about computer programming, I bet it’s mega complex, far more than I gather. But nevertheless I’d like an explanation.
Best example I have is the missing feature of saving payee’s. I mean surely monzos database must save the payee’s details as they appear in my “recent payee’s” section. Then after some time they disappear.
I would love an explanation from the monzo staff as to why it’s takes months to change this to make the payee’s permanently saved?
I think it’s important to go back and to talk about the idea of moving fast and breaking things. Starling (don’t turn this into a Starling v Monzo thread we have plenty of those already) have just released their business current account, and I love it. It was a huge engineering challenge that involved entirely changing how their systems operate and they only really began work in January, I was very impressed when I saw the glossy release page and was excited to give it a go.
But then I signed up.
I transferred in a few pounds for testing and then hit a snag transferring them back out, went to chat to support in-app and had to type out all of my details because the chat was broken and they couldn’t see them automatically. I went to my account settings and was repeatedly told of a network error, I tried on iOS and was told my verification status was unknown. Other people have had plenty of other issues and some have had the business account causing (minor) problems with their personal account.
Now, I would like to say that, while dealing with these problems, Starling have made me feel more valued as a consumer than I ever have been before (and as a dev, I’m used to seeing other people’s bugs so I don’t really mind them & I’m happy to sidestep them) but, if I was a new customer this would 100% switch me off to Starling and fintech’s in general as I’d just class them as unprofessional and uncoordinated.
In fairness, they were pressured into an early deadline of the end of the financial year which… technically they made but, they moved quickly and broke a lot of things. Thinking about that example, I don’t know about everyone here but personally, even though it’s not my project, I’m thinking about everyone’s experience and, I know I’d prefer a slower development pace with lots of testing to make sure that the big fun releases weren’t marked with the majority of users having blocking issues (and for those of us who don’t mind mixing with bugs, early betas with lots of feedback opportunities are greatly appreciated #MonzoLabs)
Just a quick example to demonstrate a different development pace and the issues with it.
Edit. I wasn’t expecting that to be quite as long as it turned out…
I don’t know and I don’t really care and right now I’m wondering why you do.
This may be of interest to you: https://monzo.com/blog/2018/04/05/how-monzo-to-monzo-payments-work/