Robert,
For example with us at the planning commission, the first thing they thought of when I first trained them on our viewer with eDraw, was to pass drawings back and forth, just for quick collaboration on random things. But, you are right, that's a very secondary use. 90% of the time it's just to view.
The two-way thing, of modifying a feature collection, is not nearly as important as if only we could load your exported Feature Collection back in to eSearch with symbology and attributes. And even at that, the geometry is probably the biggest thing. For example:::: 1) An assessor selects a parcel with your eSearch 2) She exports this one parcel as a Feature Collection 3) She then sends to a second user. This is already possible, exporting from your eSearch then loading in eDraw, to load it back in to eDraw. But it loses symbology and attributes hence why eSearch could use a Load button.
If the two-way thing is major work than it's not nearly as important as of just first implementing such a "load" button to re-load the exported Feature Collection from your eSearch. What do you think? And, maybe even for a future update, keeping symbology and attributes? (Kind of like how eDraw keeps its text and sybmology in its json file) But at first perhaps just supporting geometry? If it would help to break up this task in to multiple updates. Your new features always give us new ideas on what is even possible, like new workflows like this concept here!!! I realize I may have opened a Pandora's Box here because this vastly increases the scope of this one widget. And if any other widget re-loaded your eSearch's output that'd be fine but the current ones that I have seen don't, eDraw is the one that comes closest it seems.
example of eDraw upload/download functionality:
(note, I reversed the upload/download icons on Jeremie's eDraw)
Ah, and I guess I should have put this in eDraw. I can move my posts there if you'd prefer.