Today I re-stumbled on some good stuff from last year. We recently started modeling things like "pages the user has screenshotted" (or saved for later, or…).
I pushed Michael and Sebastian to try to model this as something like an *event*, not as a *bookmark — *that is, to record the user's action/intent/signal, not to store and mutate some kind of structured state. And I further suggested putting *several* of these actions in a table of the same place: a table of things the user has done to a particular URL. Here are a couple of long pieces from Martin Kleppman that give some context about the strengths of this kind of approach. This might bend your mind; I hope you start to see overlaps here between UI telemetry, syncing, activity streams, onboarding and feature discovery, and more besides. http://www.confluent.io/blog/making-sense-of-stream-processing/ http://www.confluent.io/blog/turning-the-database-inside-out-with-apache-samza/
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
