As we're primarily dependent on external data sources, it is hard to keep an eye on the data's quality. A pessimistic review process in which every data change needs to be reviewed is not practical and artificially delays changes that are made to external services.
Even though users are free to change the data sources directly, we expect that it's quite unlikely that this is done in practice - especially considering the circumstances in which this app is typically used. Also, depending on the external service in question, some technical expertise is required to correctly update the entries.
Letting users report faulty/incomplete/imprecise recipes might be a good compromise that keeps the effort required by the end user as low as possible while ensuring that significant data quality issues do not remain unnoticed and frustrate our users.
As we're primarily dependent on external data sources, it is hard to keep an eye on the data's quality. A pessimistic review process in which every data change needs to be reviewed is not practical and artificially delays changes that are made to external services.
Even though users are free to change the data sources directly, we expect that it's quite unlikely that this is done in practice - especially considering the circumstances in which this app is typically used. Also, depending on the external service in question, some technical expertise is required to correctly update the entries.
Letting users report faulty/incomplete/imprecise recipes might be a good compromise that keeps the effort required by the end user as low as possible while ensuring that significant data quality issues do not remain unnoticed and frustrate our users.