Let devs provide a suggested price about houston HOT 11 CLOSED

Let's use the .apphub file, then we can have a warning/reminder during the publish process if they don't have a price that it'll be published as free.

from houston.

we need some discussion about this — what format should the .apphub file be? JSON? YAML? The latter is quite popular in the continuous integration-y world, but JSON is probably the most universal.

Perhaps:

{
    "suggestedPriceUSD": "2.99"
}

Some things worth discussing:

1. should we store the currency in the key-name or the value?
2. should we store the currency as a float or a string? (JSON has no arbitrary-precision datatype, so we might run into float-y issues)

from houston.

1. I think we should store the currency in another key/value pair ("suggestedPriceCurrency" : "USD")
2. String. I think going string -> float would be easier than dealing with a float in JSON

from houston.

We can't have a minimum price so specifying "suggested" is probably unnecessary. Also I think we decided that we only wanted int pricing right?

from houston.

@danrabbit well, do we want proper int pricing ("1 dollar, 2 dollars") or $0.99/$1.99 etc?

and @zackfern, what would be the advantage of having the app developer choose the currency? it's all going to be converted on the store anyway, right? So i thought it would make the most sense to just force everyone to specify in USD.

from houston.

I thought we wanted to do proper int. We have to set USD minimums because of fees anyways. I don't think we can really process something less than $1 USD.

As far as conversions, I think it makes sense to just do USD and convert for MVP. We can always add more native currencies.

from houston.

so you're in favor this?

{
    "suggestedPriceUSD": 2
}

from houston.

I think we can drop the suggested and just have priceUSD

from houston.

i see. i guess i was just trying to make it clear that it's not a hard price, but I suppose the .apphub file is not the place for that clarification

from houston.

Yeah, I think we should probably consider implementing a small TOS sooner than later to clarify these things

from houston.

Implemented as part of PR #46

from houston.