Wow - 4 months into the issue and countless ‘the android team will fix it’-replies - and now we’re back at the kafka-esque Microsoft-‘It’s not a bug - it’s a feature!’ nonsense?
And even worse: the feature we want for Android which ALREADY EXISTS in iOS (send money to MANUALLY entered recipients instead of FORCED address book synchronisation) is supposed to be a BUG in iOS?
So either you have not understood the issue or the level of ignorance at revolut concerning customers’ concerns is worse then I thought.
So far my working hypothesis was a rather incapable Android programming team…
The world is not black or white (or use it or leave it) - it’s all about offering and choosing OPTIONS.
Revolut’s iOS app does it - and more importantly your direct competition (N26) does it - that is OFFERING the OPTION to send money to a MANUALLY entered recipient.
So KEEP the ‘feature’ of FORCING users to share address book data in order to send money to other users, WHILE OFFERING the OPTION to enter an eMail or phone number MANUALLY in order to send money.
It’s not that hard.
Right now the ‘head-in-the-clouds-we-don’t-even-understand-why-our-CUSTOMERS-don’t-like-our-FEATURE-address-book-extortion’ attitude is more than somewhat FRIGHTENING.
Applying for a bank license will hopefully shift revolut’s perspective to customers’ privacy concerns.
N26 was forced to do so as well:
- They not only offer sending money to MANUALLY entered recipients (see screenshots above)
- Had to introduce the following OPT-IN:
“In the context of using the services of the N26 App, I agree to be identifiable for other users as N26 customer.”
Yes. This seriousness (somewhat a bank’s core value, don’t you think?) is currently lacking at revolut.
It’s the user who gets to decide if he wants to be identifiable as a bank’s customer - not the bank.
Please get your heads around that fact.