As people have said before, there were lots of complaints that Monzo was walking too slowly and that they should speed up. Now there are complaints that they are going too fast. I don’t have any particular issues with Monzo’s approach at the moment as I’ve always seen using Monzo as an ongoing development.
However, these issues - lack of progress or now too much progress - could easily be solved by Monzo better using the beta processes. I feel that Monzo should use Testflight / Androids Testflight equivalent and Labs more often than they actually do. Having a fast track app and a slow track app. Then take feedback of new features from this channel to improve the app. Since I joined Testflight, there has only been a handful of betas and I couldn’t say they were particularly innovative betas pushing new build after new build. How long was labs actually testing Spending? The same could be said about the original Current Account beta. Not much was changed with the current account over the first 6 months of testing it.
Could there also be a better public bug logging system showing current and resolved issues? The iPhone X graphics bug, for example, appears about every 2 weeks on the forums.
Monzo should use the vast amount of users who would test their app to death for free before they release it to the masses who don’t like things like spelling mistakes. I have said many times they should get volunteers to help them sort out updating transaction information which are not a priority for Monzo right now.
In the end though, I think Monzo are doing a very good job and I’m happy for things to continue as they are.
Also, where do I find those people? I’d like to recommend to my boss we hire some of them, as every business needs someone to make sure there’s no security issues!
This is tough and I definitely see both sides of the debate. I havent noticed any bugs myself but when other users highlight them I can see how it looks bad for a bank relying exclusively on its app. That said I genuinely feel this is temporarily acceptable and to be expected when we demand so many updates and improvements from the service. I am definitely guilty of joining in with ideas for how we can improve the service but really these quick changes are bound to come at a price and I think that the occassional bug and spelling mistake is a fair price to pay. I would agree that if the bugs impacted security then we might have a bigger issue but I have never seen any evidence of this. I also feel like these complaints have definitely been taken onboard very strongly from @simonb 's comments above.
I would like to say that I feel like they’re starting to drop the ball as far as the app is concerned.
On the design side, I feel like they’re starting to outgrow the original design made during the prepaid beta days and are running out of room to put new features in, resulting in a bit of a mess. Not to mention, I still can’t get over the awful Android-style transaction detail view on iOS. WTF seriously? You used to set the bar on what a banking app should look like, what happened now?
On the technical side, the iOS app is getting slower and slower. Network requests are made upon opening each tab and seem to run on the main thread, as I feel quite a lot of lag when switching tabs (just try spam-click the bottom tabs on Monzo and compare to another app like the Phone app). Now this was fine back in the prepaid days when there was (presumably) one or two endpoints to request, but now with the current account and everything, this approach no longer works and the resulting experience is quite sad.
Maybe it’s time for a v2.0 with a design that treats current account features as first-class citizens instead of tacking them on here and there with duct tape, and a rewrite of the internal API service to actually use some caching and no longer load everything on the main thread (instead display a loading spinner if no previous data is available).
Sorry to be harsh, but I love :mondo: and I would like the “polish” of the prepaid days back.
Thought this was a little ironic, or was this deliberate?
Monzo inspires a lot of dedication and loyalty in people because of how they communicate with users. Since we can easily provide feedback and point out errors we tend to see them more like our friends and forgive bugs/ little errors- or conversely, expect our feedback to be taken on board ASAP because of how close we feel to the whole process. I like the pace at the moment compared to the long wait late last year from the move, but I understand there will be growing pains as they work on delivering stuff on that Big List™
Monzo has always paid attention to the little details (instead of churning out multiple services) to make the user experience truly special, so these errors probably seem jarring. If we’ve grown to expect a certain level of service and attention to detail as well as expecting more updates I hope the team isn’t stretched too thin.
Yeap I agree with a lot of what’s been said here. What’s the point in labs if the features are going to get pushed half finished? The new summary tab was just very rushed, should never have been released without committed spending working correctly.
There seems to be constant posts about iPhone X issues which seem to never be addressed?
Just seems that maybe Monzo is trying to rush too much out too quickly. I get though people did complain about lack of features before (me included). I think maybe as has been suggested, Monzo could use the Beta/Testflight system better than they currently do.
If a lot of people are having these issues then it’s not just power users complaining. We really wouldn’t have got a thread like this if there wasn’t a sizeable amount of people with issues that they feel aren’t being addressed
Nope there’s not, everybody keeps reporting it and shouting about it. I did it as late as yesterday, and COps just responded ‘thanks for the feedback’. Little bit frustrating, if the Monzo dev team are aware then say they are aware. Save everyone’s time.
TestFlight bugs would be fine but when those bugs aren’t fixed in the next “Live” release that’s frustrating. It does feel it only goes through TestFlight for a short amount of time when it could have been there for longer and had most bugs fixed
Yes, TestFlight being the keyword here, this is the whole point of testing. When bugs are flagged in beta releases, they should be fixed before the live release is deployed. The iPhone X UI bug is not isolated to beta software.
This is such a lazy response (not by you personally! but by Monzo corporately): I come across this all the time in my field (web development): “This is a Safari bug - nothing we can do about that.” Well, Safari stinks, but if you can’t do anything about that then you are working in the wrong field.
That’s why you employ iOS developers rather than script kiddies, I hope: A developer should now the bugs of their platform, and how to work around them.
I will check it anything has changed with iOS12 however 
Why is it not an issue in any other iOS app? I’m on iOS 12 and the issue is still present.
