Vanilla usage

[1j01]

What is the story for apps either not using a framework, or using a framework other than React or Angular, going forward?

Native components for these frameworks sounds great for those using these frameworks, but will an API be provided for vanilla usage?
Web Components, perhaps?

Looking at the code, I see there are separate implementations of components for each framework, so I'm guessing the answer will be to use one of the framework implementations, If so, which would be most lightweight, or easiest to integrate?

[jamesdaniels]

We're planning to provide both a headless API containing the common logic between the framework implementations and a Web Component solution in a future release.

[johanrd]

Hi @jamesdaniels. Following up on this discussion.

Looking at the v7 beta release, I notice:

1. Only React and Angular packages are available (@firebase-oss/ui-react, @firebase-oss/ui-angular)
2. No Web Component implementation
3. No vanilla/headless example in the /examples folder
4. The @firebase-oss/ui-core package exports functions, but there's no clear pattern for vanilla/framework-agnostic usage

For context, we previously used the v6 ui.start() widget approach which worked great for any framework.

Questions:

1. Is Web Component / vanilla support planned for the v7.0 stable release, or is this targeting a later version?
2. For frameworks other than React/Angular, what's the recommended approach in v7? Is @firebase-oss/ui-core intended for headless usage, and if so, is there documentation or an example planned?

Thanks for the work on v7 - the modular architecture looks promising! Just trying to understand the path forward for non-React/Angular users.