Why Not Something For Content Provider

[sbmalik]

Please Try To Solve The Headache Of content provider

[JakeWharton]

Unless you have a concrete proposal for something that could be added or a specific pain point that could be addressed I don't see much action to take here. There's little reason to use a content provider anyway unless you're providing a cross-app API. There are first-party and third-party solutions for persistence otherwise which do a much better job of abstracting the complexities.

[sbmalik]

Thanks for your help 😁

…

On Feb 6, 2018 7:18 AM, "Jake Wharton" ***@***.***> wrote: Unless you have a concrete proposal for something that could be added or a specific pain point that could be addressed I don't see much action to take here. There's little reason to use a content provider anyway unless you're providing a cross-app API. There are first-party and third-party solutions for persistence otherwise which do a much better job of abstracting the complexities. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#167 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgOs3lhQ2lY7yXeDtoktYEmsCmRp14Giks5tR7ZlgaJpZM4R6ZFn> .