Where is the official response from the Company outlining the path to resolving all of the issues listed? What is your plan to build in quality control, beta testing, and feedback before launching or removing features in your production pipeline? What is your plan to never make these mistakes going forward, specifically, breaking key functionality which your Customer directly depend on. Your service is broke, are you treating this as a high-severity event? If you don't communicate, admit your mistake, and identify the path forward, you will lose the trust of your Customers. You are now on the clock and your users will abandon your services going forward if this is not addressed. I, like many others are the primary voice of recommendation for our family and friends. You will lose us and all of those we influence if you don't provide a strategy to fix this service.
Treat this like an outage, because from a functionality standpoint and Customer impact level, it is. I expect an email from your company to all users outlining the changes, issues, and remediation in progress. I expect a stickied tracking post in this forum where you will communicate the status to resolution. I expect going forward, you establish the correct Development and Operations Support models for managing your products.
You have a chance to earn back trust, but it is a short window.