Warehouse
contactstore
| Warehouse | contactstore | |
|---|---|---|
| 1 | 11 | |
| 18 | 431 | |
| - | - | |
| 0.0 | 1.7 | |
| over 1 year ago | about 1 year ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | 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.
Warehouse
-
Warehouse
Warehouse is a lightweight Kotlin DSL dependency injection library; this library has an extremely faster learning curve and more human-friendly logs, and more explicit, it has graph nesting and multi-module support.
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.
What are some alternatives?
ez-vcard-android - Maps the Android vCard API to the ez-vcard API.
Corbind - ⚡ Kotlin Coroutines binding APIs for Android UI widgets from the platform and support libraries
ez-vcard - A vCard parser library for Java
android-gif-search - Gif LazyVerticalGrid MVVM using Dagger 2 + Hilt with Retrofit 2, Moshi, Kotlin Coroutines, JUnit, Espresso and Robolectric tests!
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!
Compressor - An android image compression library.
vcard4android - Allows usage of vCard resources with the Android contacts provider
Splitties - A collection of hand-crafted extensions for your Kotlin projects.
KotlinState - Kotlin library designed to create an Ui state management structure.
sigbla-app - Sigbla is a framework for working with data in tables, using the Kotlin programming language. It supports various data types, reactive programming and events, user input, charts, and more.