docs/in-app-messaging/_get-started.md
{# This content gets published to the following location: #} {# https://firebase.google.com/docs/in-app-messaging/get-started?platform=flutter #}
Install and initialize the Firebase SDKs for Flutter if you haven't already done so.
From the root directory of your Flutter project, run the following command to install the Firebase In-App Messaging plugin:
flutter pub add firebase_in_app_messaging
Rebuild your project:
flutter run
Import the Firebase In-App Messaging plugin:
import 'package:firebase_in_app_messaging/firebase_in_app_messaging.dart';
To conserve power, Firebase In-App Messaging only retrieves messages from the server once per day. That can make testing difficult, so the Firebase console allows you to specify a test device that displays messages on demand.
That testing device is determined by a FID. Find your testing app's FID by checking the console output when you run your app.
On Android, the message looks like the following:
I/FIAM.Headless: Starting InAppMessaging runtime with Installation ID YOUR_INSTALLATION_ID
On iOS, run the app with the runtime command argument -FIRDebugEnabled:
Once your app starts running, look for the following line in the Xcode console's logs:
[Firebase/InAppMessaging][I-IAM180017] Starting InAppMessaging runtime with Firebase Installation ID YOUR_INSTALLATION_ID
Once you've launched your app on the testing device and you have its Firebase installation ID (FID), you can try out your Firebase In-App Messaging setup by sending a test message:
Firebase In-App Messaging sends your test message as soon as you click Test. To see the message, you need to close, then reopen the app on your testing device.
To confirm whether your device is a test device, look for one of the following log messages.
Android
I/FIAM.Headless: Setting this device as a test device
iOS
[Firebase/InAppMessaging][I-IAM180017] Seeing test message in fetch response. Turn the current instance into a testing instance.