IssueTracker

Description: I'd like to use the androidx.preference framework with Compose, but it does not currently offer any support. A few high-level issues:

1. Theming would seem to either require MdcTheme on the entire app, just to support dated androidx.preference, or use duplicate theming for Preferences vs. the rest of the app. Even so, I'd expect actual widget appearance to be different between preferences & rest of the app.
2. PreferenceFragmentCompat as the entry point is a non-composable, fat API.
3. Preference and its subclasses are non-composable, fat APIs.
4. DialogPreference/PreferenceDialogFragmentCompat compounds the issues even further.
5. Not Compose-related, but SharedPreferences for storage should be replaced in favor of androidx.datastore

androidx.preference looks too broken to fix to me, so a complete, modern API replacement may be a better idea.

Interim guidance on how to generally approach Settings in a Compose world would be helpful, and that guidance may just be to abandon androidx.preferences as it will no longer be supported, plus tips on how to roll your own until a Compose-based Settings framework is available.

Use Case: Medium-sized, modularized app with a large number of user preferences from different modules, using a hierarchy of PreferenceScreens and custom screens several levels deep, and many different Preference widgets and custom widgets. Uses androidx.datastore for storage with custom Kotlin data types and Kotlin serialization for storage. Does not use datastore-preferences due to this API's data type & storage approach limitations.