WL App Configuration and Releases
WL App separates operational loyalty configuration from native app releases. Most loyalty content, campaigns, and customer-facing messages can be updated from the platform without publishing a new app version.
Branding Configuration
Branding is configured during onboarding and applied across the WL App or embedded module.
| Area | What can be configured |
|---|---|
| Brand colors | Primary, secondary, accent, background, surface, text, and error colors. |
| Typography | Font family, sizes, and weights where supported by the deployment. |
| Logo and splash | App logo, splash screen, loading states, and header assets. |
| Customer card | Background, logo placement, QR/barcode/numeric format, and card copy. |
| Navigation | Labels, icons, order, and feature visibility depending on the deployment. |
| Empty states | Illustration and copy for screens with no content. |
| Languages | Enabled languages and user-facing copy. |
No-Release Configuration
These updates are normally managed from the Loyal Guru platform or CMS and do not require an app store release.
| Area | Examples |
|---|---|
| Games | Backgrounds, card/wheel visuals, prize names, prize images, win/lose messages, probabilities, stock caps, play limits. |
| Coupons and vouchers | Image, title, description, terms, benefit copy, product/store scope, validity dates, redemption instructions. |
| Challenges | Name, description, image, progress copy, reward preview, completion message, timeline, layout selection. |
| Rewards catalog | Reward content, points cost, stock, eligibility, expiry, and code batch upload. |
| Home and CMS | Banners, articles, news, external promotions, brochures, club benefits, FAQ. |
| Points and tiers | Points currency name, tier names, tier benefit descriptions, cashback labels. |
| Push and in-app content | Message title, body, deep link, trigger event, and campaign content. |
Changes that Require a Release
An app store release is only required when the change affects the native layer or the host application behavior.
| Change Type | Why a release is needed |
|---|---|
| Native device capability | New camera, biometric, push, storage, or OS-level permissions. |
| Authentication bridge change | Host app or native SDK authentication flow changes. |
| Navigation restructuring | Native app shell, tabs, or deep-link routing changes outside the embedded module. |
| Native performance or security fix | Binary-level fixes that cannot be deployed server-side or through WebView/module updates. |
For full WL App deployments, Loyal Guru manages app store submission and review coordination. For embedded SDK deployments, the retailer owns releases of the host app, while Loyal Guru manages the embedded loyalty module.
Offline and Error Behavior
WL App is designed for retail use cases where Customers may open the app in store or during high-traffic periods.
| Capability | Behavior |
|---|---|
| Offline detection | Shows a fallback or warning when connectivity is lost. |
| Cached essentials | Core information such as card and recent loyalty state may remain visible depending on deployment. |
| Retry logic | Requests can retry when connectivity is restored. |
| 4xx handling | Validation and authorization errors are surfaced to the Customer or trigger re-authentication. |
| 5xx handling | Generic fallback with retry, while errors are logged for support. |
Analytics and Privacy
WL App and SDK deployments can include analytics tracking for loyalty engagement and user behavior.
| Area | Behavior |
|---|---|
| Event tracking | Screen views, coupon opens, redemptions, game plays, points balance views, and profile actions. |
| Custom events | Additional interactions can be configured where supported. |
| GTM / dataLayer | SDK deployments can emit tracking events to the host environment. |
| Consent-aware tracking | Analytics can respect consent state and can be disabled by SDK configuration. |
| Privacy compliance | Terms, privacy policy, consent management, account deletion, and app store privacy requirements are handled per deployment. |
Scale
WL App uses the same Loyal Guru loyalty backend as the rest of the platform. It is designed for high-volume retail scenarios, including large Customer bases, real-time voucher sync, points updates, Challenge progress, and checkout-related loyalty interactions.
Formal SLA targets, data residency, and support commitments are contract-specific.