Re: [w3ctag/design-reviews] Review request for IndexedDB Observers (#189)

Thanks for raising this issue; we are super (happy that this has a great explainer and other ancillary documents that flesh out the idea in great detail (so often these important points of background are omitted)!

A bit of initial feedback:
* We noticed in the "Why?" section of the explainer that the points made were all rather clinical and focused on the scenarios the feature enables; however we felt that a few notes about the problem space that motivated the feature would be in order (from the web dev perspective). For example: Many web developers often update a database in a worker (or somewhere separate from the UI) and must write a custom notification system (or polling) in order to know when the database was updated from the UI context. Something like that :-)
* You have a current design illustrated; what alternatives were considered? Would be great to note that in the explainer.
* This feature is strongly tied to IndexedDB, but it seems that the same problem exists for other classes of storage (like local/session storage). We would love to see this expanded and somewhat generalized to handled these additional storage scenarios. E.g. "IndexedDBObserver" => "StorageObserver" :-)

Once again, we were totally blown away with the quality of the examples in your doc. Would that all design reviews were this excellent. We're grateful you reached out to the TAG, and hope we can continue to be of service. Thanks!


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/189#issuecomment-332456203