How is it okay to make fundamentally broken software and then release/sell it as if it's functional? It shouldn't be, just like it isn't for architects, engineers(real ones) to design and build buildings that fall down and cars that explode.
Or a hundred people who have their intellectual curiosity satisfied. I recently used Google Lens to ID (with like 75% confidence) a mushroom I had zero intention of eating either way.
Mushroom identifying books have all of the same issues. I guess one could make an argument that it's unconscionable to publish those, too.
Every responsible resource will be full of this kind of caution and neglecting it should be criminal. It isn’t covering your ass or putting an obligatory warning label on everything, a primary point of interest in mushroom identification is toxicity. If you don’t do it you kill people, not like maybe but certainly.
You also don't know that the app doesn't warn users that it shouldn't be used in life and death situations, but I'll maintain that it shouldn't have to. To avoid "criminal negligence" accusations.
If I have a rock identification app does it need to say not to eat rocks to avoid liability for dental damages? If I sell bicycles do I have to tell you that rolling downhill fast can cause death or injury?
It is more comparable if you built an app to identify cancerous moles, except it produced false negatives significantly more often than an actual doctor, leading to people dying. This isn’t a “roll the dice” thing.
> he used the plant identification app
Which I think is a different category of app altogether from a fungus/plant edibility app.
What about an app that tells you how to pump gas while smoking a cigarette? That seems like pretty obvious negligent design. In California at least that opens you up to a lawsuit. [0]
[0] https://www.shouselaw.com/ca/personal-injury/product-liabili...