Storing user settings on device or via API with Storage plugin

[sts-ryan-holton]

👋 Hi everyone!

I'm currently working on a Nuxt JS application that'll be turned into a native mobile app for iOS & Android. Along side the app I'm building a Laravel 8 API that the app will communicate to in order to store data and provide authentication as well as holding larger sets of data.

One area that I'm a little stuck on is with providing user settings and app settings and where these should be stored.

For example, assume that there's a settings page and some radio button groups for each setting, let's take a setting called Theme as an example which provides 3 possible values that a user can tap on:

• System
• Dark
• Light

Currently my proposed direction would be to, on each tap of a setting send an API request to my Laravel 8 API to update a table called user_settings with a column called theme, however from what I anticipate, if the API request took any longer than a second it could provide some UI issues, but at least the settings would be stored off-device.

In my other proposed solution, I'm planning on using the Storage plugin for these since it is just key/value pairs anyway, but I kind of also need them to be stored in the database.

What are some of you doing with these types of decisions, are you using the storage plugin to store settings and a database for larger sets of data, both or one or the other?