user preference API

An API for accessing User preferences such as

• preferred font/fonts

• light or dark mode

• layout preference (mobile/desktop/tiling etc)

• font size

these specific examples don't make sense without a rendering API

I believe an API like this can provide a compromise between developers wanting/needing
to control their own render pipeline and users who value configuration.

In addition, apps wouldn't bundle their own configuration menu that could be entirely provided by the host
even if the app has unique settings, it just informs the host of the names and types of options it takes.

And, the host could generate a configuration menu that contains the settings for every app on the host.

Now that I think about it, what I'm asking for is optional parameters with metadata, E.g., option name, APIs needed to comply a with setting, ETC.
(so the user/host can tell what an option is)

The issue does not identify any files, tests, or existing entry points. Start by reviewing current WASI API proposals and conventions, then define the scope and metadata model for host-provided user preferences; done would require an agreed API design and clear behavior for applications and hosts.