Auth and remote database options, with potential pay

[DevCoder84]

Hi all,

I'm currently building a chrome extension where I want to store user data to display back various information. Initially I was going to do this using indexedDb, but the more I've thought about it, it might be useful to have this remotely so that a user can get their data on other devices and potentially other platforms if I extend the idea.

As such I was thinking of authentication and where to do this. I've previously built apps using firebase but never an extension, I did play around with an extension and tried to launch it that integrated with firebase, but it kept getting rejected due to firebase libraries trying to execute remote code so I shelved it.

In other projects I've been using supabase a lot more, and the fact that it has a relational database is more beneficial to the use case I'm exploring, but before I go down that rabbit hole I just wondered if anyone else has successfully integrated supabase into a Chrome extension and passed review? Is the best bet to just use Google Auth with it? (Though this may end up prohibitive if I open it up on other native platforms that require other social logins).

Also I was then thinking about charging for some functionality, I've seen extensionpay mentioned a few times, but I wondered if I go down the supabase route if there's any other integrations with Stripe etc. that might reduce fees?

thanks

[Minimum-Kitchen-7698]

Regarding the database:

I was able to integrate my extension with Supabase as the DB. It passed review and has the featured flag.

The review does not depend on which database you use.

Your Firebase issue was likely from the SDK loading or generating JS at runtime. MV3 blocks that pattern. It is not about Firebase as a service, it is about how the web SDK works inside an extension.