As someone who’s does work that get app reviews, luckily I haven’t had to deal with joke reviews, but it really sucks when there’s some very temporary problem for a day or two, and suddenly you start getting a bunch of ‘it used to be good but xyz is broken’ reviews that never go away because when its fixed, they never come back to update it.
Please be a responsible reviewer and if its something temporary, update your review! Ive even replied and let them know its fixed and it stays forever.
I think it can be a life lesson about fixing issues ahead of time. Users may just want to go about their needs, and aren’t volunteering to keep checking back after periodic updates to see if things are better.
I’ve had times where I report an issue, a developer (or release note) claims it’s fixed, I try it out, and the issue is still there. That can be very different from a direct communication asking me to try out a beta release that might’ve fixed it. In one of those scenarios I’m asked to QA test, in the other I’m implicitly forced to be one.
Take a closer look at the review. “It used to be good but XYZ is broken” - means at one point things worked relatively well. The demand for progress might have been the thing that broke it.
Quite often, I think the balance goes a bit too much in the wrong way towards making things newfangled at the expense of breaking standard functionality. Sometimes being lazy about a project is the better approach.
Or you know, google and apple are constantly changing rules and things break on one OS on specific phones because the OEM breaks the API google provides.
It was just an example, im not getting review bombed because I slaughtered something horribly like the send button doesnt work anymore!
Sometimes things just happen.
Edit: also, if youre not working on your app adding features that people ask for, upgrading dependencies over time, the language etc you’re going to lose users and might not even be able to publish anymore, and will even get your app removed after a period of time. Software is ever flowing even if you dont see the changes. I can’t even count the amount of times ive had to change alarms and background tasks because of rule changes by google, and you’d never know as a user.
As someone who’s does work that get app reviews, luckily I haven’t had to deal with joke reviews, but it really sucks when there’s some very temporary problem for a day or two, and suddenly you start getting a bunch of ‘it used to be good but xyz is broken’ reviews that never go away because when its fixed, they never come back to update it.
Please be a responsible reviewer and if its something temporary, update your review! Ive even replied and let them know its fixed and it stays forever.
I think it can be a life lesson about fixing issues ahead of time. Users may just want to go about their needs, and aren’t volunteering to keep checking back after periodic updates to see if things are better.
I’ve had times where I report an issue, a developer (or release note) claims it’s fixed, I try it out, and the issue is still there. That can be very different from a direct communication asking me to try out a beta release that might’ve fixed it. In one of those scenarios I’m asked to QA test, in the other I’m implicitly forced to be one.
Are you seriously saying write flawless software year after year after year? It doesn’t exist.
Take a closer look at the review. “It used to be good but XYZ is broken” - means at one point things worked relatively well. The demand for progress might have been the thing that broke it.
Quite often, I think the balance goes a bit too much in the wrong way towards making things newfangled at the expense of breaking standard functionality. Sometimes being lazy about a project is the better approach.
Or you know, google and apple are constantly changing rules and things break on one OS on specific phones because the OEM breaks the API google provides.
It was just an example, im not getting review bombed because I slaughtered something horribly like the send button doesnt work anymore!
Sometimes things just happen.
Edit: also, if youre not working on your app adding features that people ask for, upgrading dependencies over time, the language etc you’re going to lose users and might not even be able to publish anymore, and will even get your app removed after a period of time. Software is ever flowing even if you dont see the changes. I can’t even count the amount of times ive had to change alarms and background tasks because of rule changes by google, and you’d never know as a user.