i would probably use it just to see it in action, but honestly, i’m not enough of a high-volume identifier that i would download it from the Chrome store and use it routinely.
if nothing else though, i think it would be really helpful from a proof-of-concept perspective to show a possible path where the Identify module could go in the the future, and i think any really good mobile app implementation of an Identify screen would have to include some functionality to define and apply sets of actions / tasks (due to the lack of a keyboard and small screen real estate). (so that’s really why i’m suggesting this – to plant the seed for that.)
if you’re going to put this in the Chrome extension store, you might consider combining this into @sessilefielder’s existing suite of inat tools.
you might want to gauge interest with a simple forum poll, with a single option to vote yes if folks would be interested.