Fire one event per step completion — tutorial_step_1_complete, tutorial_step_2_complete, etc. — and a final tutorial_complete. Don't pass step numbers as parameters. The pattern matches onboarding-completion intentionally; the two events serve different products but the funnel discipline is identical.
▸Install the Flutter SDK
# pubspec.yaml
dependencies:
flutter:
sdk: flutter
respectlytics_flutter: ^3.0.0Pure Dart — no platform channels for analytics. Same code on every platform Flutter compiles to (iOS, Android, web, macOS, Windows, Linux). On web, events are sent via the REST API; mobile platforms use the same path.
▸Initialize Respectlytics in Flutter
import 'package:flutter/material.dart';
import 'package:respectlytics_flutter/respectlytics_flutter.dart';
Future<void> main() async {
WidgetsFlutterBinding.ensureInitialized();
await Respectlytics.configure(appKey: '<YOUR_APP_KEY>');
runApp(const MyApp());
}Initialize in main() after WidgetsFlutterBinding.ensureInitialized() and before runApp(). The future completes immediately on configuration; events queued before completion are flushed once the network is available.
▸Track the event in Flutter
import 'package:respectlytics_flutter/respectlytics_flutter.dart';
void reportTutorialStep(int step) {
Respectlytics.track('tutorial_step_${step}_complete');
}
void reportTutorialFinish({required bool skipped}) {
Respectlytics.track(skipped ? 'tutorial_skipped' : 'tutorial_complete');
}Pair tutorial completion with first-day retention events to compute D1-from-tutorial — the highest-leverage retention signal in games.
✦Privacy & implementation notes
Common confusion: "tutorial" and "onboarding" are different events. Onboarding is account / profile setup (sign in, opt in, give consent, verify email); tutorial is feature instruction (how to play the game, how to navigate the app). Most apps have both, with different drop-off patterns. Instrument them as separate funnels.
First-day retention from tutorial completion is the most actionable single metric a games team can read — it tells you whether the introduction is doing its job. Session-grouped Respectlytics events give you the rate; per-player retention curves live in your game backend if you need them at the individual level.
The Flutter SDK is pure Dart. No MethodChannel, no platform-specific iOS or Android plugin code. The same code runs on every platform Flutter supports — including web and desktop targets. This eliminates one common audit surface ("what's the Android implementation doing?").
Always initialize after WidgetsFlutterBinding.ensureInitialized() and before runApp(). If you skip the binding step, the configure call will throw on platforms that need a binding for asynchronous I/O. The SDK documentation example uses this pattern by default.
⇋How this compares to other analytics SDKs
| Tutorial finish event | Firebase Analytics | Mixpanel | Respectlytics |
|---|---|---|---|
| Step number as parameter | Recommended | Recommended | Use distinct event_name |
| Time-on-step in seconds | Recommended | Recommended | Server-side derivation |
| Skip-tutorial as parameter | Recommended | Recommended | Use distinct event_name |
| Per-user tutorial completion history | Yes | Yes | Out of scope |
| Step-by-step funnel rate | Per-user | Per-user | Session-grouped |
❓Frequently asked questions
Should we differentiate skipped vs completed?
Yes, distinct event names: tutorial_complete, tutorial_skipped. The ratio is product information — a high skip rate may mean the tutorial is redundant or annoying; a low skip rate may mean it's actually useful. Either interpretation needs the two signals separated.
What about tutorials with branches (gameplay style choice, e.g. easy vs hard)?
Distinct event names per branch: tutorial_complete_easy, tutorial_complete_hard. Per-branch retention curves come from comparing subsequent retention events across the two cohorts.
Do we measure D1 retention from tutorial finish?
Session-scoped, yes — the rate of sessions emitting any meaningful event in the 24-hour window after a session that emitted tutorial_complete is your D1-from-tutorial signal. Country / platform breakdowns surface the variation.
How is this different from `onboarding-completion`?
Onboarding is account-level setup (email verification, push opt-in, profile creation). Tutorial is gameplay/feature-level instruction. Most apps have both — a sign-in flow + a how-to-use-the-app flow. Treat them as distinct, and instrument both.