I don’t have a concrete Feature Request yet. Rather, I want to collect ideas for one, ideas that have been vetted as good practice elsewhere in the software development industry.
Hence, the “how to think” title. I mean it literally. Once we’re sure how to think about it, then we can establish requirements, think about practical mechanisms, and thereby arrive at a good Feature Request.
Maybe it won’t ever get to the level of quality I’d want to put into a Feature Request. But it should help me understand what I’m doing better, when I get to the stage where I and my app are one of those “exceptions”. I expect to get to that point fairly soon…