This issue describes a proposed enhancement to the Consumer Pay-to-play Livestreaming App Template.
Current Situation
When first launching the Consumer app, a user is shown the "Paywall" view:
Unexpected Behaviour
If a user scans the QR code, perhaps with another device, and sends sufficient currency to cover the cost of 1 minute + fees, the paywall page remains, blocking the user from proceeding.
In order to proceed, the user must first close down the app, and then relaunch it, which represent a sub-optimal user-experience.
Proposed Enhancement
This issue proposes that the app should poll at regular intervals, to verify whether the app's wallet has been topped-up.
If there is sufficient balance to pay for 1 minute + fees, then the app should proceed to the next step after the paywall page.
The polling interval should be configurable in the template, e.g. every 10s
This issue describes a proposed enhancement to the Consumer Pay-to-play Livestreaming App Template.
Current Situation
When first launching the Consumer app, a user is shown the "Paywall" view:
Unexpected Behaviour
If a user scans the QR code, perhaps with another device, and sends sufficient currency to cover the cost of 1 minute + fees, the paywall page remains, blocking the user from proceeding.
In order to proceed, the user must first close down the app, and then relaunch it, which represent a sub-optimal user-experience.
Proposed Enhancement
This issue proposes that the app should poll at regular intervals, to verify whether the app's wallet has been topped-up.
If there is sufficient balance to pay for 1 minute + fees, then the app should proceed to the next step after the paywall page.
The polling interval should be configurable in the template, e.g. every 10s