I forgot:

"Niknam: "Change is not always good for everyone. But I think it's good to realize the bigger picture of what Bunq is doing. We know very well what our users want, but it is not one group. Some are more tech savvy and outspoken on our forum and on Twitter. Those are the users that you mainly hear now. Other users are actually the silent majority, and they are reflected in the choices they make, such as the products they use. Some users think we should spend a lot of time on a very narrow set of features around managing money, say the more gadget-like things. But we also pay attention to people who care about the fortunes of the climate, for example. ""

I have waited on such statement: see "sprout.nl/artikel/gebruikers-klagen-na-nieuwe-update-bunq-wat-er-aan-de-hand"
If needed translate as I have done for this section:

"Do not turn back
Despite the mass criticism, the update will not be rolled back, Bunq founder Ali Niknam said in a response. When asked whether the angry reactions surprise him, the entrepreneur continues to return to the history of his bank and to "make the world of banking better". However, he acknowledges that the new version of the app is "really very different" from the previous one, and that it takes time for users to get used to it. There is therefore no question of a crisis situation at his company, he says when asked."

What I read here is: "F**k you users - you're simply too smart, stupid, whatever. We know exactly what we're doing."

Good Bye Bunq!

@Eelco-Stof#173094 I'm afraid, there's no backlog. At least not one for fixing things. It's more than 20 hours ago this whole mess started. No, absolutely NO reaction by bunq, besides closing the original thread, opening a new one and chapeau'ing three +1 in the old thread (besides hundreds of -2).
Meanwhile I assume these guys are sailing only by sight. Now, as it becomes obvious, that the old direction has been lost, there is no Plan B or Plan C. No risk management was obviously done. The Change has not been managed. Everybody, at least the boss, was either hoping only the best or completely ignoring all feedback.
I assume, there's only one thing valid - a goal that has had to be achieved: the app must be released in cw25. That has been achieved. But at what costs? The exciting question is - who has setup and continued the goal as it became clear, that something is going wrong.
Some of the guys in the thread suspect Product-Managers or UX-designers. No, that's far too short.
If it would have been a product-management thing, the company lead would have stand up already, setup a task-force, analyzed the situation, composed a plan and informed public. But nothing of that has come to any ears.
Thus, I assume, that the problem is absolutely top-down. With clear orders how to react - or not react.
Sorry to say, but a moment, for me, everything looks like this fish starts to stink from the head.
And you can nothing do with such situation, besides enduring or leaving.
I'm already organizing transfer of funds and reset of credit-card information for all my subscriptions.
Lucky, there is - for basic banking - not only bunq out there.

You need to communicate! Now!

@Aleksei-Zotov#172429 I also started to move funds. Especially changing account information on all companies referring to my bunq-accounts. My hope that bunq will manage this desaster decreases with every hour without any official statement by bunq.

To guys at bunq:
In this thread we have +/- 100 complaints, but no reaction to any of them by bunq-officials.
But we have 2, now 3, positives, and for the first two, we have immediate "hi-5" by bunq-members.
That means of course you're reading the thread.
However the second worst thing for a company coming into troubled water is: to not communicate, to not react, to not respond.
The most worst thing is of course coming into troubled water in first place.

This thread is meanwhile 4 hours old and perhaps you're feeling like walls are tumbling down. Perhaps you're also simply ignoring the complaining ruckus. Well, for the lattter, the things would be even more worse than I want to imagine. For the first, let's assume that all of your guys are coding. But for what purpose? With what underlying plan? Somewhere above it is mentioned that you want to fix the bug with the invisible online-cards. On-the-fly? Seriously? What about all the other details? Do you already have done an analysis? Where are you? What do you want to do?

I know such situations. The worst thing you can do is to play dead or deaf. You have to react. Or your non-reaction is interpreted as your reaction - and that's never of any good. So, please - start.

I consider that will be a long night at bunq.

Of course I do not have the big picture. The amount of already made upgrades, the complaints, the faults indicated, all extrapolated to a reasonable scenario for tomorrow, end of this week, next week. Then in comparison an estimation about potential attrition of customers. Then an effort-analysis to fix all the problems within certain time.
Or in other words: I hope you make the right decisions for the next hours and days. I do not want to talk about an emergency, but reading only this thread is indicating a big problem, yet without any statement by bunq themselves.

I have seen a lot - also withdrawing an app-version, going back to the previous version. Followed by a verbose root-cause-analysis, together with a strong plan about priorities, content and schedule. Then communication to the customer to get back trust and confidence.

However, such plan must be started immediately. Announcement of actions (even only highlighting when the plan will be available) must be available within hours. The clock is ticking and counting against you guys. At moment you have to deal with several hundred of upgrades (perhaps). Tomorrow it might be already ten-thousands.

Bunq, when will you start to communicate?

@Jakob-Y#170967 Danke für den Link. Dann nehmen wir das mal als gesichert, auch für dieses Update an.

Gerade ein rewrite muss besonders intensiv durch eine Regression. Ansonsten baut man sich ja zwei Baustellen rein: die alten features funktionieren nicht mehr, die neuen noch nicht.

Wenn es dann zum release-date kommt und klar wird, dass etliche Dinge nicht funktionieren, dann müssen Prioritäten gesetzt werden. Entweder ein MVP das funktioniert, das muss entsprechend kommuniziert werden, oder aber man bleibt länger im Beta-Stadium und macht weiter, bis das Zeug funktioniert.

Keine dieser Möglichkeiten scheint gewählt worden zu sein.
Möglicherweise hat sich der/die zuständige Projekt-Manager/in gnadenlos übernommen und ist schon Vergangenheit bei buq. Aber auch das kann kommuniziert werden. Wurde es aber nicht.

Also bleibt, dass alles von "oben" abgesegnet ist.
Und das wäre bei Leibe kein Ruhmesblatt.

@Jakob-Y#170918 Danke für Deine Antwort. Ich kann jetzt natürlich nicht evaluieren, inwiefern Deine Aussage mit der Wirklichkeit übereinstimmt. Aber nehmen wir für einen Augenblick an, dass es so ist, wie Du schreibst.
Dann gibt es zwei mögliche Szenarien:

1) Bunq hat über alle existierenden Features ihrer App, vor allem die bisherigen Features, die vielleicht nur ein bißchen geändert oder verschoben wurde, eine extensive Regression laufen lassen. Und ich würde hier mal eine richtig gute test-coverage voraussetzen wollen. Dann haben sie von den Fehlern gewußt und haben die App trotz dieser Fehler freigegeben => NO-GO

2) Bunq hat eine nur marginale oder gar keine Regression für ihre (vorhandenen) Features. Und hat dementsprechend das ganze nur mit von mir aus module-tests freigegeben. Ohne irgendwie zu wissen, wie das ganze als System funktioniert. Oder bisherige Features weiter funktionieren. => NO-GO

Egal, wie ich es drehe und wende - wir sprechen hier nicht von einer Wetter-App, die von einem Hobbyisten an seinen freien Wochenenden zusammen geklöppelt wird. Wir sprechen hier über das Front-End von Geld-Verwaltung. Da erwarte ich mehr Konsistenz und Gründlichkeit.

@Jakob-Y#170907 Hi, worauf genau gründet sich Deine Zuversicht? Ich vermute, ich hoffe, dass Banking-System und UI getrennt voneinander sind. Dass, auch wenn Mist angezeigt wird, in den darunter liegenden Basisdaten nichts geändert wurde, bzw. diese immer noch existieren. Aber weiß ich's? Weißt Du mehr?

What the hell? What's going on?

Guys at bunq, you have done a beta-phase. Found a lot of problems. And did you fix them?
How on earth can you dare to issue such app for banking activities in this pre-alpha-state.
Inconsistent data, instable results, random numbers - are you sure you wanted to have that?

You're a bank, aren't you?
And what do you think is the most important attitude your customers will request from you?
News? Gadgets? Progress? NO!
It's only one thing: reliability!
And reading such comments, together with the comments in other channels (reddit, Telegram, etc.) makes me nervous.
And nervous in money affairs means nothing good - for you.
I mean, why shall I wait until you guys start to consider to provide a stable and mature product, which passes at least basic consistency regression?