Page Comparison

...

Once a BK App guest’s phone battery gets down to a low %, we trigger them an offer for a free of Monster Drink. When the guest charges their phone the offer will disappear from the Offers Page.

We don’t need to store battery level information, we need to create a capability to read this info during user navigation and when our app is running in the background.

...

• Create a new ruleset User Attribute > Battery Level to be applied on SystemWide Offer.

• The new ruleset will check the battery level according to the parameter inputted;

• If the user’s battery level hits the parameter, an offer will be available on their Offers page, only App;

• No latency between when the guest triggers the offer and when it appears in the App;

• Display this offer on Kiosk, we need a development on our side and Acrelec also needs to have a development. So, the recommendation is go live only on App because the users receive a In-App notification and they can redeem the offer right-way in the App;

• The offer will be available until the user battery becomes above the parameter;User atribute, after many conversations with Data Team, they decided to not save battery level as user attribute on mParticle/Braze and the event Offer Unlock will be triggered instead when user hits the parameter set on Sanity. So, we should use this event to send In App message via Braze

• Create a new User Attributes property called Battery Level that will be checked when the user starts the app and then, every 2 minutes. This property will only be checked if at least one of the Systemwide Offers available has the Battery Level rule within its UserAttributes rules.

• To run the be able to run the battery level rule evaluation when the app is in background we're introducing @capacitor/background-runner package. This enables us to run JS scripts in the background for both Android and iOS:

  • We will schedule the background job successfully user first have to start the app.

  • When the app starts in the foreground, we persist all battery level rules from offers to be able to access this data later in the background. For user data we're accessing existing user data stored under RBI_USER key.

  • When the App enters the background, we schedule the background job. Currently, it's configured to run every 5 minutes, however due to platform level battery optimizations, it's not guaranteed that the script will always run (see the docs for more details). In the script we initially check if:

    • User is signed in

    • Battery level rules are stored

  • When these two conditions are met, we then evaluate the battery level rule with the current device battery level, in case when the battery level has changed enough to enter/leave the configured battery threshold, we will send a local notification when the conditions are met. When the guest taps the notification it opens the Offers Page in the App and the mParticle event will be sent from foreground. This would be safer in terms of duplicating events from foreground/background.

    • Risks:

      1. Platform level battery optimizations:

         1. There are no guarantees the background job will ever run, especially when the battery level is low;

         2. Need to take into consideration iOS and Android battery optimizations feature which they might be kill our background job.

            1. We should use threshold above 20%. For instance 30%, based on iOS platform usually starts their battery optimizations function in 20%.

...