Wherever it is placed, it needs a consistent, detailed, but iNat-novice-friendly explanation that should point out what the current community taxon is.
Regarding placement, what is the problem you’re trying to solve by moving it? If you’re concerned its current placement is so obvious that people are using it when they don’t understand what it does, do can you cite some examples? IMO, the three-dot contextual menu is a fairly obscure place to put it. Regarding the proposal to remove it, this is functionality I personally want in the app (and everywhere else) so I can opt-out of the community ID for those rare occasions where I am completely confident the community is incorrect, so I’m not in favor or removing it. I am in favor of making the language more consistent.
The number of observations added via the Android app that are opted out of the community taxon is vanishingly small
The proportion of observations added via the Android app that are opted out of the community taxon is considerably less than the same proportion on the web
IMO, this seems to imply that people aren’t using it that much. Can’t say whether or not Android users are confused by it, but I don’t think it’s doing much damage.
That’s great to see, and a lot better than me attempting to find past examples - not even sure how I would have - thank you!
Aside from me accidentally tapping it all the time, maybe it’s confusing (to me) because it is the only thing in the menu? Needs a “Duplicate observation” friend.