Let's try the minimal lab application

LabApplicationxxx are real public applications.
Try the web application and the Android app to understand how everything works.

1 · Plan URL, DNS, profile — register in the Console.

2 · Lab Try the reference web and mobile apps.

3 · Understand Embed styles, sign-in flow, server checks. 4 · Implement Starters, server routes, page stack, CSS.

Try the lab apps

Web lab

LabApplicationNodejs at https://nodejs.lab.kie.la — header embed, native session, same backend as the other starters: go, python, php, java, ruby, rust, csharp.

Open web lab ↗

Mobile lab

Android partner app for the same LabApplicationNodejs — no login screen in the partner app; sign-in is delegated to the Kie.la app.

Get Kie.la app ↗ Mobile lab on Google Play ↗

Optional: set MOBILE_LAB_PLAY_STORE_URL for a Play listing of the mobile lab app. The APK is served from ktest-android when built (./gradlew assembleDebug).

Understand the profile fields returned to the application after authentication.

The application always receives the fields enabled on the user’s chosen persona. Nickname and email are always included. After the user approves sign-in on their phone, enabled fields are sent to your backend as json:

Field	Notes
`nickname`	Always included. Unique display name on the platform — often the primary identifier in your UI.
`firstname`, `lastname`	Given name and family name as stored on the chosen persona.
`email`, `mobile`	Always includes email. Mobile when enabled on the persona. Unverified markers are added at auth time when needed.
`device`	Device hint from the approving mobile client, when enabled on the persona.
`avatar`	Avatar URL when enabled on the persona.

For the impatient

Go straight to the starters.

Starter packages →

← Plan

Next, see how the sign-in prompt fits into your application.

Understand sign-in →