Those are some nice stats!
Like the others have already posted, the main problem is in the communication. Yes also from customers to bunq; we can be harsh in voicing our opinion. However, that tone is caused by sudden unexpected changes to crucial areas of our workflows. More of a defensive wtf cry rather than a direct attack towards the people at bunq.
Personally I have to live with tight budgets and the routing of recurring payments has become crucial in keeping the money flow in line, without becoming a Scrooge watching every cent. With the automatic routing to my budget accounts I simply cannot spend more than I actually have. When a budget is dry at the recurring tx I become aware that I quickly need to make adjustments. A nice way to prevent debt 💰. Dedicated budgeting apps and the like are too slow for this, because they either require me to keep checking them and the connected ones only process transactions after they happened. Only the bank itself can decline transactions before they happen, and bunq did.
Being a tech company bunq should be familiar with the practice of announcing breaking changes. Either by deprecation notices in the release notes or with semantic versioning, bumping the major version when the interface breaks. That way there is time to make adjustments before going along with the new release. The release notes of the app updates did not announce any feature deprecations in advance, neither did any of bunq‘s posts on Together. It was just forced upon us without a notice, disguised as a big improvement, but seriously breaking money management flows. Even when the stats show it is not as commonly used, there are people using it. A friendly heads up would be extremely appreciated and limit the amount of negative feedback after the release.
(edit: typos)