I can confirm, at the Glasgow Meet they inspected our phones upon entry. iOS users were taken into a lovely room, where they had drinks and food and got to see some talks from Monzo staff. Us Android users were herded into a freezing room where we were jeered and spat at for the duration of the event.
I did get to pay for my Uber home using Android Pay, so that was nice.
I totally see where youāre coming from, and I agree - itās frustrating that features are not released on both platforms at the same time. Ideally, thereād absolute feature parity and everything would be released at the same time.
The team currently working on Pots is made of 1 iOS dev and 1 Android dev (+ backend). Unfortunately, itās not a case of focusing efforts on one platform instead of another as the two developers are not interchangeable and, in most cases, features are not necessarily comparable across platforms in terms of effort required. For instance, there might be components that have been built differently and therefore require a different approach (and potentially more time to deploy).
In the case of pots, the implementation required both platforms to upgrade the current āAccountsā tab from what used to be the āCardsā tab. Luckily for us, this had already been done by another team on iOS but it wasnāt necessary for Android at the time. This resulted in our team taking on additional work to make Pots function as designed which slowed us down significantly compared to iOS. This was highlighted in our Pots retrospective and the team took an action to carefully scope projects and decouple them from any dependencies going forward!
Here is a screenshot of our retrospective tool.
We are working very hard to bring new features on both platforms at the same time, but at the moment we are a very small team and we are sadly constrained on several fronts. We have already made significant progress in our efforts to achieve this goal, and weāre confident that in the future weāll be able to continue to close that gap until it no longer exists.
On a personal note, Iām an Android user myself (and so are @tristan and @JordanFish) and I can promise you that none of us favour iOS in any way. Weāll definitely reach feature parity one day!
Thanks for your reply @valerio, that makes things a lot clearer for me!
Itās fair enough that the Android developer is constrained by some other activities to be completed like the āAccountsā tab and that both are getting the same amount of developer attention.
Sometimes it feels like thereās loads of people developing iOS and no-one developing Android or at least heavily weighted towards iOS but itās refreshing to hear that in this instance that isnāt the case but just held up by Androids general behind-ness.
From memory of what was stated at one of the recent Open Office events, I think there are now more āAndroid bodiesā floating around Monzo than iOS ones. They just have more to do to catch up
Ahahaha, and now imagine how awful that would be down the line in regards to maintainability, scaleability and performance
That also excludes the security issues that systems like React bring to the table (as it is essentially writing lower level Swift/Java for you, you have very little control and oversight so malicious code injection is a real possibility unless you manually inspect every line generated at which point the engineering time to develop in React > native)