Error Flagging Feature for Android App
Love the android app currently in beta. My only gripe is I don't have a tablet to read with, using my phone is annoying.
However, I have often wished it was possible to hi-light a sentence when I notice a possible error (typically a missing "to be" word). That way I could contribute to the translation without interrupting my reading to log onto the forums, try to explain the location of the error, and then describe the error itself. Just being able to flag the sentence would possibly help when making future edits, especially if multiple people notice the issue.
The main problem with this kind of feature is that it's incredibly burdensome on JNC staff. How do we handle people abusing the report feature? How much time does it take to check whether an error is legitimate or not? We currently get a lot of suggestions that aren't error reports but contesting editorial choices, and those take additional time to check with the translation team. We are still a very small company, so creating a new job responsibility to monitor the app error report feature means taking away resources from a different part of the company. Or the error reports just get ignored because of how time consuming it is, in which case why spend the time and resources developing it in the first place?
We know this feature has been widely requested, but some of us staff also believe that leaving the process more burdensome naturally filters out a lot of the problems I cited above. It's an entirely voluntary process, so if someone is taking the time to do it, then we can naturally place a certain amount of trust in the reports.
@myskaros a highlight feature would be useful without the automatic reporting system, readers could just highlight any potential errors they see as they read through and then easily go back to review and report them later, which would also let them more easily consolidate error reports. It also just lets the kind of people who like highlighting their books do that if they want to.