First-Party Integration

What This Is

Guidance for Lovelace teams integrating the shared auth SDK into first-party apps.

Who This Is For

Internal product teams that ship on the Lovelace platform.

What You Will Finish With

• SDK-only integration for core auth flow.
• Clear bootstrap model for client provisioning.
• Separation between Accounts runtime and app-specific setup.

Recommended Provisioning Model

• Keep app client definitions in bootstrap manifests or setup scripts.
• Sync client definitions into Accounts during environment bootstrap.
• Keep Accounts runtime logic app-agnostic.

Runtime Model

• UI uses AuthProvider and useLovelaceSignIn().
• Verification route uses createLovelaceSignInRoute().
• Accounts service remains generic and does not depend on app-specific code paths.

Why This Model

It preserves clean service boundaries while keeping app integration turnkey.

Related

• Production Hardening
• Reference