Acorn as We applet

collaborate on diagrams: https://drive.google.com/file/d/1uELuB8yGMp1Xvmu_HttxmUK-au7xq-YM/view?usp=sharing

main considerations

• how will the "lobby" DNA structure change?
• how will membrane access change?
• how will the desktop app change?
• do we want to make the desktop app interoperable with the We applet? How will this affect the current registration flow and architecture?

architecture considerations

conductors <-> UIs

The desktop Acorn app prepackages a holochain binary with electron-holochain. If acorn becomes a We applet, it would need to use the conductor managed by the launcher. Would the electron UI be able to connect to the launcher and display any projects from there?

I think there is value in keeping the option of using Acorn as a standalone desktop app, without needing the launcher or We. However, if users want to connect their apps, that can be done.

team-based organization

Miro organizes boards in "teams" which show up in the left sidebar. If Acorn organized its trees like this, perhaps invitations are managed at the team level rather than the tree level. Would we still want to allow for per tree invitations?

happ architecture

If Acorn uses a team-based approach, each hApp is per group, with 2 DNAs:

1. profiles
2. project (clonable template, each project is its own DNA)

This approach makes interoperability with We much easier, as shown below.

UI interop

electron UI

The electron UI could fetch teams and projects from both Holochain conductor instances (electron-holochain and launcher - as shown in blue and green). Projects from the launcher include directly from the Acorn webhapp as well as the Acorn We Applet.

We applet UI

The We applet UI would only fetch We specific hApps from the launchers conductor instance. If viewing the applet from a group context, the team sidebar is not shown, and only the list of trees specific to that group are shown. If viewing the applet outside of a group context, then a list of all groups can be seen.

Launcher App UI

Acorn could also be packaged as a standalone .webhapp that can be installed to the launcher outside of We. If so, it manages its own team happs, but could also connect to any team happs created inside We.