Thinking through user-private documents

[a-type]

I have a couple routes for supporting documents which are private to one user, which would be helpful for certain upcoming apps, like...

• Mood tracking... the whole app, really.
• Wish list - shared shopping lists, but private wish lists
• Guitar stuff - WIP songwriting shouldn't be visible to other members

All of these are either a whole library or some subset of documents being private to one particular user's replicas. They should still sync to that user's devices.

The two ways I have for doing this would be...

1. Support it in Verdant.
2. Have multiple libraries for these apps: one public, one private

So I just want a space to (publicly) think out which one to choose.

[a-type]

Verdant implementation

Pros: Possibly opens the door to more flexible authorization in the future.

Cons: Complicates Verdant as a system, even if only a little. Also, I've thought about possible future authorization steps and none of them seem feasible with the way Verdant works (like sharing to N users, or read/write permission granularity).

[a-type]

Multi-library implementation

Pros: Keeps Verdant simple and isolates this concern to higher abstraction. Private libraries would be relatively lightweight as they would be limited to pull-based sync anyways.
Cons: Might complicate client code. Might require ensuring multiple Verdant stores work well on the same page.

[a-type]

Upon reflection, I think what I'll try is prototyping a simple app with private data using the multi-library approach and see how it feels.