Methods, systems, and computer readable media for locally storing cloud application user preferences

1 . A method for locally storing cloud application user preferences, the method comprising:

at a user device comprising at least one processor:

obtaining, using a first representational state transfer (REST) application programming interface (API) endpoint and a local data store for storing user preference data associated with a first user of a user preferences service, user preference data for a first cloud application, wherein obtaining the user preference data includes obtaining, from a remote server, a default value for a first user preference of the user preference data when the local data store lacks a value for the first user preference;

utilizing the user preference data to configure or present the first cloud application on the user device;

detecting an updated value for the first user preference; and

storing, in the local data store, the updated value for the first user preference.

2 . The method of claim 1 comprising:

at the user device or a local data store controller:

sending, using a second REST API endpoint and to the remote server, a POST API message including the updated value for the first user preference; and

receiving, from the remote server, a POST API response indicating a successful update of the value of the first user preference.

3 . The method of claim 2 wherein the POST API message includes a user identifier, an application identifier, or another identifier for uniquely identifying data associated with the first user stored at or by the remote server.

4 . The method of claim 1 comprising:

in response to a second cloud application associated with the user preferences service starting up or being logged into by the first user, obtaining, from the local data store, values for compatible user preferences including the first user preference in lieu of requesting the values for the compatible user preferences from the remote server.

5 . The method of claim 1 wherein obtaining the user preference data occurs concurrently with or after starting or logging into the first cloud application.

6 . The method of claim 1 wherein obtaining the user preference data includes sending, using the first REST API endpoint, a GET API message for requesting at least some of the user preference data and receiving a GET API response message providing at least some of the user preference data in a data format discernible by the user device.

7 . The method of claim 6 wherein the data format includes a Javascript Object Notation (JSON) format, an extensible markup language (XML) format, an object notation format, a data interchange format, or a binary format.

8 . The method of claim 1 wherein the remote server includes a user preferences service platform or a remote data store for storing user preference data for a plurality of cloud applications including the first cloud application.

9 . The method of claim 1 wherein the first user preference includes a theme preference, a page size preference, or a view type preference.

10 . A system for locally storing cloud application user preferences, the system comprising:

a memory;

at least one processor; and

a user device implemented using the memory and the at least one processor, the user device configured for:

obtaining, using a first representational state transfer (REST) application programming interface (API) endpoint and a local data store for storing user preference data associated with a first user of a user preferences service, user preference data for a first cloud application, wherein obtaining the user preference data includes obtaining, from a remote server, a default value for a first user preference of the user preference data when the local data store lacks a value for the first user preference;

utilizing the user preference data to configure or present the first cloud application on the user device;

detecting an updated value for the first user preference; and

storing, in the local data store, the updated value for the first user preference.

11 . The system of claim 10 wherein the user device or a local data store controller is configured for:

sending, using a second REST API endpoint and to the remote server, a POST API message the updated value for the first user preference; and

receiving, from the remote server, a POST API response indicating a successful update.

12 . The system of claim 11 wherein the POST API message includes a user identifier, an application identifier, or another identifier for uniquely identifying data associated with the first user that is stored at or by the remote server.

13 . The system of claim 10 wherein the user device is configured for:

in response to a second cloud application associated with the user preferences service starting up or being logged into by the first user, obtaining, from the local data store, values for compatible user preferences including the first user preference in lieu of requesting the values for the compatible user preferences from the remote server.

14 . The system of claim 10 wherein the user device is configured for obtaining the user preference data concurrently with or after starting or logging into the first cloud application.

15 . The system of claim 10 wherein the user device is configured for sending, using the first REST API endpoint, a GET API message for requesting at least some of the user preference data and receiving a GET API response message providing at least some of the user preference data in a data format discernible by the user device.

16 . The system of claim 15 wherein the data format includes a Javascript Object Notation (JSON) format, an extensible markup language (XML) format, an object notation format, a data interchange format, or a binary format.

17 . The system of claim 10 wherein the remote server includes a user preferences service platform or a remote data store for storing user preference data for a plurality of cloud applications including the first cloud application.

18 . The system of claim 17 wherein the user preferences service platform utilizes a microservice architecture or the user preferences service platform is distinct from a cloud application server providing data or service to the first cloud application.

19 . The system of claim 10 wherein the first user preference includes a theme preference, a page size preference, or a view type preference.

20 . A non-transitory computer readable medium comprising computer executable instructions embodied in the non-transitory computer readable medium that when executed by a processor of a computer perform steps comprising:

at a user device comprising at least one processor:

obtaining, using a first representational state transfer (REST) application programming interface (API) endpoint and a local data store for storing user preference data associated with a first user of a user preferences service, user preference data for a first cloud application, wherein obtaining the user preference data includes obtaining, from a remote server, a default value for a first user preference of the user preference data when the local data store lacks a value for the first user preference;

utilizing the user preference data to configure or present the first cloud application on the user device;

detecting an updated value for the first user preference; and

storing, in the local data store, the updated value for the first user preference.