I have received news that once again the service will be down for a very long time period (5 hours) due to your failure to pull this off the last time you tried (which also casued huge damage to our business, and I won’t start listing the way to high number of times these issues happened in the past 2 months alone).
Anyhow, since this time at least you had the decency to provide this information a bit in advance, I am asking for the following (not that I expect it to be of any use, considering that most of the times your service does not work the way you say it does, like when you blocked us completely on January 1st because of a failed payment, despite the fact that you keep denying it and saying that you do not do so for up to 5 days):
- how do you recommend that in the apps we handle the fact that you are offline? Obviously people will want to use the service, and even worse, people will buy the app and will be stuck there for hours. Do you return a specific error that can be handled so that we can provide useful feedback to the user? Please note that the last times this happened we got all sort of different errors, hence it does not seem that you do this properly and consistently.
- please provide code in Objective C and Java showing a simple attempt to login and handling the fact that the server is down, plus a way for us to test this before the 16th, so that we can at least try to make changes in the app to inform the user and avoid another total fuckup, with negative reviews and hundreds of emails from angry customers
Considering that we have been paying for this service for years, and that the damage recently has been difficult to contain due to how unreliable it became, please try at least this time to make sure we can be prepared (and that we can test it). Provide code and instructions and a way to test the whole thing ASAP
This is of course for backendless 3.