Hello and thanks for the quick reply, I will look more closely at the feature list before asking next time. 
It looks like the thread you referenced on IAP was over a year old with much noise, anecdotal information, or referencing older or outdated ADC dev agreements.
Wondering if your team could create a “live” document that could outline some workarounds for IAP and perhaps how that problem was solved? The goal is something that would serve as a “guide” for monetizing a freebie game without multiple versions on the app store (or even marketplace although I don’t really care about android atm).
Side Note:
One of the technical problems that was pointed out was supporting all the platforms for a given function. Why not take the php approach and just use a naming convention for platform specific functions? (i.e. ios_iap_approve…) For something that is IOS platform specific I would expect to fail when invoked on the android platform. As usual it would be the onus of the developer to disable the feature if they were testing on another platform. Maybe we can all agree to some extent that the further we abstract the device the more we degrade (or at least divest) the user experience. [import]uid: 6769 topic_id: 2281 reply_id: 6903[/import]
