Nice! The approach, then, is to create two separate channels: a "lite" or "free" one and a fully paid version? Is that right?
Is it correct that there are otherwise no "upgrades" available to boxes before 4.3 aside from installing another channel?
I guess I could have two apps, a "lite" one that offers an in-channel upgrade to boxes 4.3 and after, and then a separate channel that has the features enabled for those boxes prior to 4.3.
How do I prevent users from installing the "full featured" channel without paying? Is it a public channel or a private channel? How do I enable a fee for that channel?
I feel like there's a key document I failed to read. Which one is it
🙂What design approach works best for developers/users? Are there any other design approaches to consider?
Seems like it's easiest at this point to in-channel purchasing, then add it later when there are worthwhile features.
If I do that, can I convert people on post-4.3 boxes from the "fully-enabled" version to the "in-channel" purchase version so I can maintain only one version eventually? Related question: is it possible to give away the fully-enabled version for free?
In the
Channel and Publishing Guide, it says:
Channel packages are initially uploaded to the Channel Store as unpublished channel versions. Developers can do beta-testing by accessing these unpublished packages via Roku assigned channel codes.
How does this interact with a paid channel? (i.e. do beta testers pay? can the beta test period be eliminated by the developer?)
Thanks!