Reference¶
Config Builder Options¶
| Method | Required | Description |
|---|---|---|
firebaseProjectId |
Yes | Firebase project ID |
firebaseApiKey |
Yes | Firebase API key |
firebaseAuthDomain |
Yes | Firebase auth domain |
firebaseStorageBucket |
Yes | Firebase storage bucket |
firebaseMessagingSenderId |
Yes | Firebase messaging sender ID |
firebaseAppId |
Yes | Firebase app ID |
firebaseDatabaseId |
No | Firestore database ID (default: "(default)") |
emberEndpoint |
Yes | Ember API base URL |
bifrostEndpoint |
No | Bifrost API URL (derived from Ember if omitted) |
embedCdnEndpoint |
No | Embed CDN URL (derived from environment if omitted) |
environment |
Yes | DEVELOPMENT, UAT, or PRODUCTION |
glanceAccountEndpoint |
Yes | Glance account service URL |
googleSsoClientId |
Yes | Google OAuth client ID |
glanceAuthClientId |
No | Auth client ID (default: "ai-looks-embed") |
storeHandle |
Yes | Your store's handle/slug |
webAuthUrl |
Yes | Web auth page URL for OAuth flow |
brandName |
No | Brand display name (default: "GLANCE") |
brandLogoUrl |
No | URL for your brand logo shown in SDK UI |
productDeeplinkBaseUrl |
No | Deep link base URL for product navigation (e.g. "yourapp://product"). When set, the SDK fires {base}/{variantId} intents instead of using the onProductClick callback. |
Environment Options¶
| Environment | Description |
|---|---|
DEVELOPMENT |
Development environment |
UAT |
User acceptance testing |
PRODUCTION |
Production environment |
ProGuard / R8¶
The SDK ships with consumer ProGuard rules that are automatically applied. If you use full obfuscation and encounter issues, add these rules to app/proguard-rules.pro:
-keep class com.glance.chat.** { *; }
-keepattributes *Annotation*
Permissions¶
The SDK declares these permissions in its own manifest (merged automatically):
| Permission | Purpose | Required? |
|---|---|---|
INTERNET |
API calls, chat, product data | Yes (auto-merged) |
CAMERA |
Selfie capture for virtual try-on | Optional (auto-merged, required=false) |
You do not need to add these to your manifest — they are merged from the SDK automatically.
Firebase Compatibility¶
The SDK initializes its own Firebase app instance with the name "glance_chat". This is completely isolated from your app's default Firebase instance. If your app already uses Firebase, there will be no conflicts.
Sample App¶
A fully working sample app (GlanceStore) is included with the SDK distribution. It demonstrates all integration patterns described in this guide. Use it as a reference implementation.
FAQ¶
-
Does the SDK work without Jetpack Compose?
Yes. Wrap
GlanceChatOverlay()andProductTryOnWidget()inComposeView. See Step 3 and Step 6. -
How much does the SDK add to APK size?
The AAR is small. Adding Compose dependencies adds ~2-4 MB if your app doesn't already use Compose.
-
Does the SDK handle its own authentication?
Yes. Login is handled via Google Sign-In (web redirect), separate from your app's auth.
-
What data does the SDK store on device?
Minimal: device ID, auth tokens, conversation path, user profile. No sensitive data persisted.
-
Can I customize the chat UI colors/theme?
Basic branding via
brandNameandbrandLogoUrl. Contact Glance for more options. -
What happens without internet?
The chat FAB appears, but chat and try-on features require an active connection.
Support¶
For integration support, contact the Glance AI team at your designated partner channel.