Flutter Product Analytics

Instrument decisions, not widgets. Begin with a product question and a stable event contract, then preserve the project's analytics provider, consent platform, state management, navigation, and data architecture unless migration is requested.

Installing this skill requires no analytics account, key, project, or SDK. Do not add a vendor, create dashboards, enable collection, or change live retention and consent configuration merely because the skill is selected.

Preflight

Read pubspec.yaml, SDK constraints, current analytics adapters and initialization, environments, consent and privacy controls, event definitions, identity lifecycle, navigation tracking, offline buffering, backend transformations, tests, dashboards or schemas in scope, and release configuration. Identify the question, decision, owner, population, and success definition before adding an event.

Each event needs a semantic trigger, stable name, bounded typed properties, identity and consent policy, delivery expectation, and verification plan. Emit once for the domain occurrence—not from widget build, incidental rebuilds, route observers, and button callbacks simultaneously.

Load references conditionally

• Read event contracts and ownership when defining names, properties, semantic triggers, funnels, revenue events, schema evolution, or duplicate prevention.
• Read identity, consent, and privacy for anonymous and authenticated identity, account switching, opt-in or opt-out, deletion, sensitive data, advertising attribution, and offline buffering.
• Read verification and experiments for DebugView or live-debug tools, backend inspection, environments, funnel validation, experiment exposure, and rollout evidence.

Boundaries