Nice update, looking forward to the budgeting improvements but no ETA for pot hiding on iOS is pretty naff 
4 Likes
Happy to see everything moving forward however a lack of ETA for iOS is a little more than disappointing but maybe I’m just impatient
1 Like
Not impatient, it is definitely disappointing. it’s a feature that’s been talked about quite a bit on here and never once has it it been mentioned that a platform might lag behind.
4 Likes
I too am disappointed with lack of parity for iOS. I’m not a techy type but out of curiosity is iOS more complex in some way? I see all sorts of restrictions being placed by Apple on apps via the store. R-
1 Like
Not really, but they are two different platforms so just have two different methods of implementing stuff.
It has been mentioned before that the Android and iOS teams don’t synchronise as one could hold up the other due to staff holidays, bug fixing and such. So they just plough through their own agendas and release as and when it’s ready.
At least that’s how I remember it without searching the forums for the exact comment 
9 Likes
As a long time Android user, makes a change for once to not be the poor relation to iOS
That’s how I remember it explained, and also that there are not always the same number of Android and iOS devs on each team
4 Likes
Last few things I can think of have all been predominantly android first… could this mean monzo need to hire more ios devs to keep capacity similar? 
Yeah that’s what I remember them saying.
Which makes it slightly more concerning that the apps will start to diverge more and more? And who oversees all of this? Hopefully this is just one example that has been done to luck, but from my experience, it’s pretty basic planning to know this stuff so makes me worry at the ‘manager’ level that this is still all ‘team driven’ with little to no cohesion across platforms.
And yeah, if something new is being developed and worked on first by a specific platform team, just tell us that up front? Transparency, remember? And Monzo must’ve known about this for a while already. Not great.
2 Likes
To be devils advocate for a moment and whilst saying Monzo does all I need I would be concerned about functionality drift. It is almost as if there are two different products being developed. R-
2 Likes
I remember when custom pot images were released on iOS - this was before Android had the same functionality - so it’s nice Android is getting a look-in first for this one.
There’s loads of little (and big) differences on the wiki (my bugbear is the piss-poor search on Android) which would be nice for a dedicated team to go through to try get OS parity.
7 Likes
so monzo have been developing in this way since their inception but now you’ve been personally disadvantaged suddenly it’s going to get worse and worse and the team management is terrible.
It makes complete sense from a management point of view to do one platform first, work out the kinks and issues and then implement faster on the other platform as you know how best to do it etc already. That you are annoyed and think it should be held off whilst it’s built for both platforms is rediculous. User feedback on one platform will help both and speed everything up.
It’s really just not a big deal and they’ve said they’re working on the iOS version already.
14 Likes
@bruno is back 
Best tell that to thousands of companies, both larger and smaller, who think they know better than you then.
1 Like
No chance you just don’t scout the updates on both platforms for other apps so arnt actually aware what features are different between the two platforms?
Monzo haven’t publically released a feature here (no press release etc just a forum post on progress), they’ve specifically said they’re putting it in labs until they’ve got it ready for both…
2 Likes
Apparently putting something in Labs is now the same as releasing it. So there we are.
4 Likes
Don’t recall much iOS user solidarity down the years when whole apps were not on Android
BBC Sport was a notable - and license payer funded - example for months
6 Likes
Oh I totally agree, and it is not a feature I would use anyhow. But just because a process is X, doesn’t mean that it is either the correct way of doing things or that the process can’t be improved on.
1 Like
Nothing to do with me personally at all, I’m not that petty, nor am I annoyed. I just think it speaks to a wider issue that, whilst small at present, could lead to problems in the future.
I disagree with the approach of building for either platform first.
But then I don’t manage any of this, and I’m going on the little information we have, just like everyone else here.
2 Likes
Ohh for goodness sake.
I want feature parity. Let’s not let the past taint this.
5 Likes
It is, you are right.
1 Like