On that basis anything that needed contacts should be in the same
app!

On Nov 15, 2:45 pm, Kristopher Micinski <krismicin...@gmail.com>
wrote:
> The typical answer is that if you have something like this then you
> shouldn't have separate apps in the first place.
>
> kris
>
>
>
>
>
>
>
> On Tue, Nov 15, 2011 at 8:11 AM, swebb99 <sweb...@gmail.com> wrote:
> > Hi,
>
> > Newbie here.
>
> > If I want to create several apps which all allow a user to created,
> > read, update and delete related data so a content provider would seem
> > to be the way to go. However I don't know which app a customer would
> > buy first, second and so on. So how do I make sure that:
>
> > 1) The first app creates and registers the provider.
> > 2) Subsequent apps only make use of the provider and don't recreate.
> > 3) Make sure the provider gets upgraded if a new app is bought, but
> > also is not downgraded if an older app is bought after a new one.
>
> > From reading the docs on content providers I just can see how any of
> > this is possible. The definition of providers doesn't seem flexible
> > enough to allow this kind of thing. If it isn't possible what is the
> > strategy because it looks like content providers are the only
> > mechanism for applications to share data.
>
> > Thanks
>
> > Steve
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" group.
> > To post to this group, send email to android-developers@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-developers+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to