Slide VS androidx

Thank you kind stranger! I opened https://github.com/Haptic-Apps/Slide/issues/3485 with slightly different instructions (shaved off a couple of steps). For example Step 1 can be skipped by doing clone from repo in step 4.

TIL that Slide is also open source: https://github.com/Haptic-Apps/Slide

So long Slide and Infinity, ill see you again in the Fediverse

I didn't actually hear that they were doing API changes? I use Slide, so I guess for me one day in the future Reddit will just stop working.

Slide: intended for everyone, but Its lead developer was immediately open to addressing accessibility concerns, during the beta process, and u/MostlyBlindGamer was able to contribute several fixes for the TalkBack screen reader.

Which would be good open source 3rd party apps to test with? I found a couple of mobile apps, like https://github.com/Docile-Alligator/Infinity-For-Reddit and https://github.com/Haptic-Apps/Slide

FYI, Infinity and Slide are solid reddit apps and both open-source. I still prefer RIF, but in case your wish doesn't come true there are already at least two pretty good options.

I used to use Slide. Switched to Infinity after seeing it promoted on F-Droid. Both are great (with a preference for Infinity) and I will stop using reddit on mobile because I refuse to use their mobile app.

This project will be on indefinite hiatus for the foreseeable future, and may not be maintained. Updates are not guaranteed. See here for details.

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:

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.

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

https://github.com/androidx/androidx The androidx repo might be what you're looking for

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).

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

SafeArgs VM isn't safe?

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