MSGreg
13 years agoVisitor
Converting to paid app, migrating vanity codes
I have an existing free private channel with a vanity code and I want to convert to a paid upgrade with dual channels paid/demo.
I want the new paid version to acquire the vanity code that is now associated with the free private channel, and the new demo version to have a vanity code with a "demo" suffix. All without upsetting or confusing existing users.
I know that the paid version will be a public channel. Should the demo version be a public channel too? I have been getting a good number of users/testers by being listed on the "private channel" lists. Going forward, the demo version is really intended for users to verify basic functionality on their Roku device(s) before purchase.
The new demo version has screens for upgrading, so I'll need to first get the paid version's access code so I can include that in the demo version for the upgrade process. Does that paid access code become available to me when I click "submit" or do I have to wait until the paid version is accepted?
From the same code base, I have two different packages, one with the "Demo" enabled, and one with "Demo" disabled (i.e. the latter is the paid version).
Can anyone walk me through the process of doing this conversion, especially with regard to migrating the vanity code?
I think I might end up with three channels: paid, demo, legacy private channel. This would be fine but at some point, I would like to remove the legacy channel.
I want the new paid version to acquire the vanity code that is now associated with the free private channel, and the new demo version to have a vanity code with a "demo" suffix. All without upsetting or confusing existing users.
I know that the paid version will be a public channel. Should the demo version be a public channel too? I have been getting a good number of users/testers by being listed on the "private channel" lists. Going forward, the demo version is really intended for users to verify basic functionality on their Roku device(s) before purchase.
The new demo version has screens for upgrading, so I'll need to first get the paid version's access code so I can include that in the demo version for the upgrade process. Does that paid access code become available to me when I click "submit" or do I have to wait until the paid version is accepted?
From the same code base, I have two different packages, one with the "Demo" enabled, and one with "Demo" disabled (i.e. the latter is the paid version).
Can anyone walk me through the process of doing this conversion, especially with regard to migrating the vanity code?
I think I might end up with three channels: paid, demo, legacy private channel. This would be fine but at some point, I would like to remove the legacy channel.