Quickstart

The prompt does steps 1–3 for you, then interviews you about your screens, paywall and core actions and implements the events, a funnel and — only if you want — user identification. You still need a write key: create your app in the dashboard and replace glance_live_… below, or let the agent ask you for it.

You are integrating AppGlance (privacy-first, live analytics for iOS and Android apps) into this Xcode project. Do the whole setup, then interview me about what to track and implement it. Work in small, reviewable steps and show me the diff before committing anything.

SWIFT PACKAGE: https://github.com/AppGlance/AppGlance  (module: AppGlance, version 1.0.0 or later, "Up to Next Major")
WRITE KEY (write-only, safe to ship in the binary): glance_live_…  — if this still says glance_live_…, ask me for the key; it's in the dashboard under the app's Setup tab: https://appglance.app/app/
DASHBOARD: https://appglance.app/app/

1. Add the Swift package to the app target (File → Add Package Dependencies…, or the project.yml / Package.swift if this project generates its Xcode project). Import it where needed with `import AppGlance`.

2. In the @main App's init(), as early as possible:
   AppGlance.configure(apiKey: "glance_live_…", debug: true)
   Attach `.trackAppLifecycle()` to the root view inside WindowGroup — this gives sessions, "active right now", installs and retention automatically. If the app is UIKit-based, call `AppGlance.setActive(true/false)` from the scene's foreground/background delegates instead.
   `debug: true` is there so I can verify the integration from Xcode right away: this build sends (events tagged simulator/debug — visible under the dashboard's "All" scope, never in Live) and the SDK logs each event and send to the console. Remind me to remove `debug: true` before shipping (or gate it on `#if DEBUG`). Without it, Debug and Simulator builds never send anything (TestFlight and App Store do) — that default is the right one for shipping.

3. Interview me (ask, don't guess — a few short questions, one message):
   a. What are the 3–6 key screens or steps a user moves through? (I'll get `.trackScreen("name")` on each, e.g. onboarding, paywall, the main screen.)
   b. Is there a paywall / purchase (StoreKit 2, RevenueCat…)? Where does a purchase or trial succeed?
   c. What is the core "job done" action (workout completed, entry saved, export finished…)? Any small, non-personal detail worth attaching (type, count, plan)?
   d. Do users sign in / have accounts? If so, do I want to put a name or email on their install with identify (it changes the App Store privacy answers), or keep everyone anonymous?
   e. Anything else worth counting (a feature toggled on, a share, an error the user sees)?

4. Implement the tracking plan from my answers, using ONLY these APIs:
   a. `AppGlance.track("event.name", metadata: ["key": "value"])` — event names lowercase, dot.separated, stable, ≤80 chars (e.g. paywall.viewed, purchase, trial.started, workout.completed, checkin.logged). Metadata is [String: String], short values, at most 20 keys. Never put names, emails, ids or free text a user typed into event names or metadata.
   b. `.trackScreen("paywall")` on the SwiftUI views for the key screens (records screen.paywall on appear).
   c. If there is a paywall, track `paywall.viewed`, and `purchase` / `trial.started` when they complete (with the product id as metadata) — and tell me, because that changes the App Store privacy answers (Purchases → Purchase History).
   d. Do NOT call AppGlance.identify unless I said yes in 3d — users are anonymous by default and that's the point. If I said yes: on sign-in call `AppGlance.identify(id: , email: , name: )` with only the fields I approved, and `AppGlance.reset()` on sign-out. Nothing the person didn't give the app.
   e. You may propose user properties (`AppGlance.setUserProperties(["plan": "pro"])`) for things I would want to filter users by (plan, cohort, goal…), but ask before adding them. Values are short strings; they show up as filterable pills in the dashboard's Users tab.
   f. Analytics calls must never block the UI, throw, or run in unit/UI tests. Don't add a consent banner or an ATT prompt — nothing here is tracking in Apple's sense.

5. When done, reply with:
   - the list of events you added, one line each: name — where it fires — metadata keys;
   - a suggested funnel of 2–6 of those events in order, as this link (replace <app id> with the id from my dashboard URL, and the names): https://appglance.app/app/#app/<app id>/events?funnel=paywall.viewed,purchase — opening it saves the funnel in my dashboard;
   - what my App Store privacy answers should be, based on what you implemented. Default: Identifiers → User ID and Usage Data → Product Interaction, not linked to the user, tracking No, no ATT prompt; add Purchases → Purchase History if you tracked purchases; if identify is used, add Contact Info and everything becomes "linked to the user". The dashboard's Setup tab generates the exact ticks.

Documentation: https://appglance.app/docs · this quickstart: https://appglance.app/quickstart. Keep it minimal — the whole point of AppGlance is that setup takes two minutes.You are integrating AppGlance (privacy-first, live analytics for iOS and Android apps) into this Android project. Do the whole setup, then interview me about what to track and implement it. Work in small, reviewable steps and show me the diff before committing anything.

GRADLE DEPENDENCY: implementation("app.appglance:appglance:1.0.0")  (Kotlin, minSdk 21, package app.appglance). NOTE: this artifact is not on Maven Central yet, so that line will not resolve on its own. Build it locally first: clone https://github.com/AppGlance/AppGlance, run `cd android && ./gradlew :appglance:publishToMavenLocal`, then add mavenLocal() to the project's repositories. Tell me if that fails rather than guessing at a different coordinate.
WRITE KEY (write-only, safe to ship in the binary): glance_live_…  — if this still says glance_live_…, ask me for the key; it's in the dashboard under the app's Setup tab: https://appglance.app/app/
DASHBOARD: https://appglance.app/app/

1. Add the dependency to the app module. Nothing to add to the manifest (INTERNET comes with the library). Import with `import app.appglance.AppGlance`.

2. In the Application subclass's onCreate() (create one and register it in the manifest if the app doesn't have one), as early as possible:
   AppGlance.configure(this, "glance_live_…", debug = BuildConfig.DEBUG)
   Sessions, "active right now", installs and retention are automatic (the SDK watches ProcessLifecycleOwner) — nothing to attach to activities.
   `debug = BuildConfig.DEBUG` is there so I can verify the integration from Android Studio right away: debug builds send (events tagged emulator/debug — visible under the dashboard's "All" scope, never in Live) and the SDK narrates to logcat under the tag AppGlance. Release builds behave normally: emulator and debuggable builds never send anything, production and beta builds do — that default is the right one for shipping.

3. Interview me (ask, don't guess — a few short questions, one message):
   a. What are the 3–6 key screens or steps a user moves through? (I'll get `AppGlance.trackScreen("name")` on each — Compose LaunchedEffect or onResume — e.g. onboarding, paywall, the main screen.)
   b. Is there a paywall / purchase (Play Billing, RevenueCat…)? Where does a purchase or trial succeed?
   c. What is the core "job done" action (workout completed, entry saved, export finished…)? Any small, non-personal detail worth attaching (type, count, plan)?
   d. Do users sign in / have accounts? If so, do I want to put a name or email on their install with identify (it changes the Play Data safety answers), or keep everyone anonymous?
   e. Anything else worth counting (a feature toggled on, a share, an error the user sees)?

4. Implement the tracking plan from my answers, using ONLY these APIs:
   a. `AppGlance.track("event.name", mapOf("key" to "value"))` — event names lowercase, dot.separated, stable, ≤80 chars (e.g. paywall.viewed, purchase, trial.started, workout.completed, checkin.logged). Metadata is Map<String, String>, short values, at most 20 keys. Never put names, emails, ids or free text a user typed into event names or metadata.
   b. `AppGlance.trackScreen("paywall")` where the key screens appear (records screen.paywall).
   c. If there is a paywall, track `paywall.viewed`, and `purchase` / `trial.started` when they complete (with the product id as metadata) — and tell me, because that changes the Play Data safety answers (Purchase history).
   d. Do NOT call AppGlance.identify unless I said yes in 3d — users are anonymous by default and that's the point. If I said yes: on sign-in call `AppGlance.identify(id = <account id>, email = <email>, name = <name>)` with only the fields I approved, and `AppGlance.reset()` on sign-out. Nothing the person didn't give the app.
   e. You may propose user properties (`AppGlance.setUserProperties(mapOf("plan" to "pro"))`) for things I would want to filter users by (plan, cohort, goal…), but ask before adding them. Values are short strings; they show up as filterable pills in the dashboard's Users tab.
   f. Analytics calls must never block the UI, throw, or run in unit/instrumented tests. Don't add a consent banner — nothing here uses the advertising id, IP or location.

5. When done, reply with:
   - the list of events you added, one line each: name — where it fires — metadata keys;
   - a suggested funnel of 2–6 of those events in order, as this link (replace <app id> with the id from my dashboard URL, and the names): https://appglance.app/app/#app/<app id>/events?funnel=paywall.viewed,purchase — opening it saves the funnel in my dashboard;
   - what my Google Play Data safety answers should be, based on what you implemented. Default: Device or other IDs (the random install id) and App interactions — collected, not shared, encrypted in transit, deletable on request, purpose Analytics; add Purchase history if you tracked purchases; if identify is used, add Personal info → Name / Email address.

Documentation: https://appglance.app/docs · this quickstart: https://appglance.app/quickstart?platform=android. Keep it minimal — the whole point of AppGlance is that setup takes two minutes.