ComposePrefs
androidx
| ComposePrefs | androidx | |
|---|---|---|
| 5 | 14 | |
| 67 | 5,076 | |
| - | 1.5% | |
| 0.0 | 10.0 | |
| over 1 year ago | 5 days ago | |
| Kotlin | Kotlin | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ComposePrefs
-
Does anyone actually use DataStore?
I use it as part of my own apps as well as in my Compose preferences library https://github.com/JamalMulla/ComposePrefs.
-
ComposePrefs3 is the Material3 version of ComposePrefs, a library for creating Preferences in Jetpack Compose. Available now!
I posted about ComposePrefs a few months ago and said that I went with M2 because M3 was just lacking. That's no longer the case, so here's the updated library for M3. Hope it's useful.
- ComposePrefs - Fully featured preferences library for Jetpack Compose
- Fully featured preferences library for Jetpack Compose
- I open-sourced an intuitive and easy to use Preferences library for Jetpack Compose. Currently has support for 8 of the most common Preference items including Text, CheckBox, List, and EditText.
androidx
-
Building Reddit Recap with Jetpack Compose on Android
To diagnose whether our composables and models meet these criteria, we leveraged Compose Compiler Metrics. These gave us stability information about the composable parameters and allowed us to update our UiModels and composables to make sure that they could be skipped. We ran into a few snags. At first, we were not using immutable collections, which meant that our list parameters were mutable and hence composables using these params could not be skipped. This was an easy fix. Another unexpected issue we ran into was that while our composables were skippable, we found that when lambdas were recreated, they weren't considered equal to previous instances, so we wrapped the event handler in a remember call, like this:
-
Is there anywhere on github which has the latest Android Open Source Project (AOSP) files?
I am trying to manually copy and paste out the pieces of code I need from the glance source code and put into my Android Studio project but as you can imagine there are hundreds of errors to address. I also tried a git clone of a specific chunk of the source code from here without any luck.
-
Simple RSS Feed Reader - Jetpack Compose
One mistake I made is naming conversion of a composable function, that I didn't start with a noun. This is quoted from Compose API guidelines
- Does anyone actually use DataStore?
-
Where is the GitHub repo for kotlin multi platform mobile. I can't find it?
https://github.com/androidx/androidx The androidx repo might be what you're looking for
-
Introducing Focus, a new open source Gradle plugin
Haven't looked too closely yet, but so far this seems similar to AndroidX Playground (albeit Playground isn't exactly meant for public consumption, of course).
- Just because Jetpack Compose is out, it does not mean we have to bury the old XML
-
LiveData is superior to StateFlow for UI and ViewModel layer.
This is the implementation of CoroutineLiveData: https://github.com/androidx/androidx/blob/androidx-main/lifecycle/lifecycle-livedata-ktx/src/main/java/androidx/lifecycle/CoroutineLiveData.kt
-
What is current best tech stack for modern apps?
SafeArgs VM isn't safe?
-
Do you use SharedPreferences?
preferences datastore is similar to SharedPreferences. Proto datastore is the one you should be using, and is based on protocol buffers to give you type safety among other advantages. Even in the case of preferences datastore though, it doesn't appear to even mention SharedPreferences. You can see the source for all datastore components here: https://github.com/androidx/androidx/tree/androidx-main/datastore
What are some alternatives?
Showkase - 🔦 Showkase is an annotation-processor based Android library that helps you organize, discover, search and visualize Jetpack Compose UI elements
Kotlin_Flow_To_The_View - PoC using Flow completely on an Android Projet with MVVM architecture. No LiveData. The advantage over simply using the viewModelScope is the fact that 5 seconds after leaving the application (not killing it !), the coroutine is cancelled, avoid possibly unnecessary work.
KotlinBloc - A predictable state management library for Kotlin and Jetpack Compose, using the BLoC design pattern.
jetpack-autoloader - [READ ONLY] Autoloader for Jetpack. This repository is a mirror, for issue tracking and development head to: https://github.com/automattic/jetpack
compose-remember-preference - Jetpack Compose library for remembering state persistently (based on DataStore preferences)
Dispatch - Automatic CoroutineDispatcher injection and extensions for kotlinx.coroutines
preference-store - DataStore Preferences wrapper
event-emitter - [ACTIVE] The event emitter allows you to register multiple observers, but enqueue events while there are no observers.
ComposePrefs3 - ComposePrefs3 is a fully featured library of preference composables for Jetpack Compose.
PiCompose
android-starter-v4 - An Android template project (in Kotlin) with boilerplate and current patterns.
Anko