contactstore
Compressor
| contactstore | Compressor | |
|---|---|---|
| 11 | 1 | |
| 431 | 6,994 | |
| - | - | |
| 1.7 | 0.0 | |
| about 1 year ago | 5 months ago | |
| Kotlin | Kotlin | |
| 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.
contactstore
-
🍾 Contact Store 1.0 is now available! – a modern, simpler way of accessing contacts in Android
If you find this API useful, 🌟 give a star on Github and 🐦 [follow (@alexstyl)](twitter.com/alexstyl) on Twitter for updates.
- GitHub - alexstyl/contactstore: A modern contacts Android API.
- Show HN: I wrote an new API to replace Android's ContactProvider
-
I have created an API to get rid of ContentProviders when using the Contacts API
Out of curiosity, would you be willing to elaborate why you used interfaces for the Data Models as opposed to something like a data class? e.g. Contact.kt
-
ContactStore 0.9.0 now supports every ContactContract columns 🎉
You can find the source code at: https://github.com/alexstyl/contactstore
-
ContactStore 0.6.0 is out – Featuring new DSL, Linked Account support, testing without Robelectric
There have been a few new features in ContactStore released recently. If you are working with Contacts in your app and you prefer an alternative to working with ContentProviders, this one is for you.
- I wrote an API in Kotlin to make Contacts straightforward to use (no ContentProviders)
-
I wrote an API in Kotlin +Flow to make Contacts straightforward to use (no ContentProviders)
It looks like that on a first look but you will get multiple emitions. All queries in ContactQueries use extensions in ContentResolver.Kt in order to make the Flow emit again once a change in the ContentObserver is detected.
Compressor
-
setResult and finish don't work inside any Coroutine Scope. Possible reasons?
We use the Compressor library in our app. I upgraded it to V3 today, and that requires that the compression code be run inside a Coroutine Scope.
What are some alternatives?
ez-vcard-android - Maps the Android vCard API to the ez-vcard API.
Coil - Image loading for Android and Compose Multiplatform.
Corbind - ⚡ Kotlin Coroutines binding APIs for Android UI widgets from the platform and support libraries
glide - An image loading and caching library for Android focused on smooth scrolling
ez-vcard - A vCard parser library for Java
Fresco - An Android library for managing images and the memory they use.
android-gif-search - Gif LazyVerticalGrid MVVM using Dagger 2 + Hilt with Retrofit 2, Moshi, Kotlin Coroutines, JUnit, Espresso and Robolectric tests!
ImageLoader
contacts-android - Android Contacts API Library written in Kotlin with Java interoperability. No more ContentProviders and cursors. Say goodbye to ContactsContract. Build your own contacts app!
SoBitmap - Bitmap decoder, handle resize & quality & compress stuff following user's configurations.
vcard4android - Allows usage of vCard resources with the Android contacts provider
Android-Universal-Image-Loader - Powerful and flexible library for loading, caching and displaying images on Android.