Thanks for your contribution, you made really great points!
All development these days is done in steps, and they do too. R Business web app started simple and they kept adding features in time.
I think there’s use cases for both mobile and desktop. One is not better than the other, it is simply more adapt to a certain context. And you can get a job done either way, it’s just a matter of being very specific. Take Binance for example. It does a great job of allowing users manage their portfolio both on mobile and web/desktop (which is just an electron wrapper). So you can be successful on both, but none is enough to cover the use cases of the modern user.
I’d like to know more about it. As far as I understand, users just make use of alternative platforms depending on the context. So if you give them a mobile app they will use it when they are off their desks of course. Which doesn’t mean they are moving to mobile. They are simply being smart with the tools they have in context they are. As I said, no single platform can replace another, unless you are able to enclose the full feature set of the other platform with the first one.
That’s correct, but not new at all. Revolut Business already works on the web. Additionally, I’d say that no matter what client you are considering, they all need to communicate to Revout server/cloud anyway. So that wouldn’t lessen the worry about security anyway. A web client is just another client, and there’s an abundance of experts in the field.
Have no experience with Bunq, but I’d be happy to start with the very basics of account management. There’s already an API in place the ability of third parties to build custom Revolut clients with modern stacks based on React or Angular is demonstrated by the projects open sourced on github. Once you have an API in place, yes it’s still a lot of work to provide a performant client, but it’s not A LOT OF WORK. Revolut has been successful so far with the Business branch and porting features to the mobile platform as soon as possible. I don’t see the STRUGGLE (but I’m not saying it’s not challenging either).
It may be. But I don’t get the need for a native desktop client, considering we are talking about a network-heavy application. There would little speed benefit if any. And it would be kind of expensive to maintain a performant app for each platform, unless you go Java, but that’s not native anyway.
Again, I appreciated the contribution, it’s good food for thoughts