I might be missing something. I was proposing content provider as an app of it's own, much like say how some of the file managers provide security modules. So when A is installed the content provider is not. Of course the user can go and just install the content provider but that's no different than if the user deleted the file I guess.
On Sep 19, 2010 9:28 AM, "Mark Murphy" <[email protected]> wrote: On Sun, Sep 19, 2010 at 9:23 AM, Prakash Iyer <[email protected]> wrote: > You could write a content... Except it won't support the "data survives uninstall" requirement: -- User installs App A -- App A realizes the provider isn't there and enables its own copy of the provider -- Life is good -- User installs App B -- App B sees that App A's provider is there, uses it -- Life is still good -- User uninstalls App A, wiping out the data -- App B sees that App A's provider isn't there and enables its own copy of the provider -- User sees the data is gone -- User is unhappy -- Life is not so good -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware... Groups "Android Developers" group. To post to this group, send email to android-develop...@googlegro... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
