I have just created LIP-10 proposing a unified standard for creating and managing Communities which allows using them in an interoperable manner across the Lens ecosystem: github.com/lens-protocol/LIPs/pull/33
While we have already learned that the right place to discuss LIPs is on Github, here's a TLDR for those who will not bother:
Currently, numerous Lens apps (Phaver, Orb, Lenspeer and soon Hey) each offer different implementations of Communities with significant part of their functionalities isolated within the parent app. This results in fragmented user silos and makes navigating the ecosystem confusing, especially for newcomers, as interoperability levels can differ from app to app in various ways.
Overall, it can be detrimental to growth and adoption rates, especially in the current stage of ecosystem development, where network effects and joint efforts to expand the shared graph are crucial.
Interoperability of current implementations is possible and exists on some limited level. However, it is not sufficient, and increasing it would need active coordination between all involved parties, making it ever harder to maintain as the number of apps grows.
To address all that, a unified standard for creating and managing Communities in a way that allows interoperability between apps is needed. It will ensure apps have a straightforward way to offer their users Communities which are accessible from any other app that supports the same standard.
Apps might still choose to have isolated Communities, however, an option to create interoperable ones is crucial for the ecosystem growth. In the longer run, users will decide which model (app gated or interoperable) will prevail.
Finally, ensuring openness and standardization of such a key functionality goes well in line with Lens philosophy and values.