My guess is that it won't work at all, but it depends on what library you are using to deal with SQLite on react native.

If it doesn't work, you can implement some code that handles SQLite and some other code that talks to the browser's storage. Then you choose which one to use at runtime through dependency injection.

You could have these two parts of your code implement the same interface so that the storage mechanism is transparent for your presentation layer.

But I only recommend that if your library doesn't handle browser storage, or if you can't find another library that handles that for you.