πŸ“± Webviews
Overview

Gamification Webviews

Ready-made gamification UI (overview, challenges, leaderboards, offers, shops, and more) that Lynes hosts for you. Your mobile app opens it inside a WKWebView or WebView and authenticates the user with a JWT.

Audience: Developers integrating the Webview into a host app.
Not covered here: Running or modifying the Webview codebase β€” Lynes operates the deployment.

For REST API access without a Webview, see JWT Authentication.

How it works

Your app                         Lynes-hosted Webview              Lynes API
   |                                      |                            |
   |  GET /leaderboard                    |                            |
   |  Authorization: Bearer <JWT>         |                            |
   |------------------------------------->|                            |
   |                                      |  POST /auth/token (exchange) |
   |                                      |--------------------------->|
   |                                      |  session established       |
   |  UI renders for user (sub)           |                            |
   |<-------------------------------------|                            |
   |                                      |                            |
   |  myapp://loyalty/back  (close)       |                            |
   |<-------------------------------------|                            |
  1. You open the Webview URL Lynes assigned to your project.
  2. The first HTTP request includes Authorization: Bearer <JWT>.
  3. The Webview exchanges the JWT for a session and loads data from the Lynes API.
  4. To close the Webview or open external links, the UI navigates to callback URLs you register in your app (configured on your hosted instance).

What Lynes provides vs. what you build

Lynes (hosted)Your app
HTTPS Webview URLWebView + URL loading
UI, routing, API calls inside the WebviewJWT from your backend
Callback URLs on your instance (…/back, …/external)Handlers for those URLs
Lynes API backendUser identity (sub in JWT) aligned with your user IDs

Documentation

PageWhen to read
Partner ChecklistWas Lynes vom Partner braucht (kurze Checkliste)
Quick StartFirst integration β€” start here (app developers)
Integration GuideiOS/Android details, refresh, errors
URL Parameters & RoutesQuery params and paths
AuthenticationJWT and session exchange
Native BridgeCallback URLs
ℹ️

Onboarding

Partners: see the Partner Checklist for everything Lynes needs (Keycloak, callbacks, branding). App developers: request your Webview URL and exact callback URLs from Lynes before production.