jfarringdon has posted an answer to the question "In-App Purchasing for
Applications":

No you should not currently offer in app features that you charge for. It is
against the distribution agreement.

You could offer separate paid apps, and have your main app share these
resources (if you take good care to share, normally apps do not share).
Post back with your solution, it is an interesting question for a number of
people. Good luck, J.

http://www.android.com/us/developer-distribution-agreement.html


View this question at the Google Help Forum
Unsubscribe from answers to this question

jfarringdon

Thank you for the response and exactly what I am designing.

My main app uses Characters where the information about each character are
stored via the sqlite database and the images that make up the character are
stored on phone which my main app uses to load a character when needed.

I will create an "installer" app for EACH character. The installer app will
contain the information for each new character and the images (which are
under /assets in the apk) and when the user buys an installer app for a
character it will download, run, read in the images from /assets, write them
to the phone and populate the sqlite database with the the character
information.  The installer for each character will also uninstall a
character by reversing the process.

So when an installer for character is purchased (though marketplace) and run
to install the character, then my main app can read the database, read the
images and run the character.

I downside is a user can then have accumulate "installer" apps for each
character on their phone. So I am applying an option to remove the installer
app for each character once the character is installed or they can either
remove it or leave it on their phone.

The characters can be uninstalled from the installer OR from the main
program.
So they don't need the installer app to remove a character.

That is the ONLY way I can think to abide by the Market rules as they stand.

-Chris

On Wed, Mar 24, 2010 at 11:34 AM, chris harper <[email protected]> wrote:

> I see your point. I can be read either way. The android tech guys on here
> won't comment because it is a legal matter but it would be really really
> great if they could at least point us in the direction of WHERE to ask this
> question???
>
> There is not a legal discussion forum to ask these things.
> *
> Please.  To the Google engineers reading this. *
>
> You guys really might want to bring up at your next weekly working meeting
> (if you have those) that with all these developers creating everything from
> X to Z for applications there WILL be many legal questions like this one
> that will need to be answered.
> So the developers will know what direction to go in on different issues.
>
> We don't want to skirt around anything legal, we just need a place to go
> for direction.
>
> So you guys REALLY might want to set up a place where we can go to get
> these legal questions answered.
>
> Instead of waiting until they do all the work of developing their app and
> getting it out there and THEN telling them "oh you can't do this for legal
> reason ..whatever".
>
> Just trying to help. I guess I will just send search around to see if I can
> find a general android support email and I will send the question there.
>
> For anyone wondering what the question is go up to my last email on this
> post about how to do in-app purchasing and the Market Agreement.
>
> -Chris
>
>
> On Wed, Mar 24, 2010 at 10:44 AM, Yahel <[email protected]> wrote:
>
>> > 3.3 *All fees received* by Developers for Products *distributed* via the
>> > Market must be processed by the Market’s Payment Processor.
>> >
>> > To me that means any additional money that you make from any product
>> (i.e.
>> > app) that you distribute from the Market must go though the Market's
>> Payment
>> > Processor.
>>
>> Say I sell gold point, or tickets through my app, then it doesn't fit
>> into " *distributed* via the Market ", since it is not distributed
>> through the Market at all, but through my app.
>> Intrepretation is in the eye of the beholder...Whatever that means :D
>>
>> Anyway, there is no need to argue. We need Google's take on it.
>> Because only them know what they want and don't want.
>>
>> Yahel
>>
>> --
>> 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]<android-developers%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>>
>> To unsubscribe from this group, send email to android-developers+
>> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
>> ME" as the subject.
>>
>
>

-- 
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

To unsubscribe from this group, send email to 
android-developers+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Reply via email to