SkillAgentSearch skills...

firebase-in-app-messaging

Use when running in-app message campaigns, triggering/suppressing messages, configuring opt-in data collection, testing on specific devices, rendering campaigns with custom Flutter widgets, or handling message callbacks.

Install / Use

npx skills add evanca/flutter-ai-rules --skill firebase-in-app-messaging

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Automation

Supported Platforms

Universal

Our assessment of firebase-in-app-messaging

firebase-in-app-messaging scores 88/100 on our quality scale, 1478th of 2,768 Automation skills we index.

Its SKILL.md is 5.4 KB long, well organised into 13 sections with 7 code examples: a solid amount of guidance for an agent.

It has 670 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 13 days ago, so firebase-in-app-messaging is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

firebase-in-app-messaging compared with similar skills

All 4 of these similar skills score higher than firebase-in-app-messaging; compare them before choosing.

SkillScoreStarsUpdatedFormat
firebase-in-app-messaging (this skill)by evanca8867013d agoSKILL.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.1k9d agoCLAUDE.md
Scraplingby D4Vinci100104.2k1d agoMCP Server

Frequently asked questions

How do I install firebase-in-app-messaging?
Run npx skills add evanca/flutter-ai-rules --skill firebase-in-app-messaging. The install tabs above show the steps for each supported agent.
Which AI agents does firebase-in-app-messaging work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is firebase-in-app-messaging safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is firebase-in-app-messaging still maintained?
The repository was last updated 13 days ago, so firebase-in-app-messaging is actively maintained.

name: firebase-in-app-messaging description: "Use when running in-app message campaigns, triggering/suppressing messages, configuring opt-in data collection, testing on specific devices, or handling message callbacks." license: MIT

Firebase In-App Messaging Skill

This skill defines how to correctly implement Firebase In-App Messaging in Flutter applications, covering setup, programmatic triggers, privacy controls, testing workflows, and campaign management.

When to Use

Use this skill when:

  • Setting up Firebase In-App Messaging in a Flutter project.
  • Triggering or suppressing in-app messages programmatically.
  • Implementing opt-in data collection for GDPR or user privacy compliance.
  • Testing campaigns with specific devices before rollout.
  • Configuring message types, targeting rules, and A/B tests.

1. Setup and Configuration

flutter pub add firebase_in_app_messaging
import 'package:firebase_in_app_messaging/firebase_in_app_messaging.dart';
  • Initialize Firebase before using any In-App Messaging features.
  • In-App Messaging retrieves messages from the server once per day by default to conserve power.

Setup Checklist

  1. Confirm Firebase.initializeApp() completes before accessing In-App Messaging.
  2. Create a test campaign in the Firebase console to verify the integration.
  3. Locate the Installation ID for device-specific testing (see Testing section).

2. Message Triggering and Display

Use Google Analytics events to trigger in-app messages without additional code. For programmatic triggering:

// Trigger a message tied to a custom event
await FirebaseInAppMessaging.instance.triggerEvent("purchase_complete");

Suppress Messages During Critical Flows

class PaymentScreen extends StatefulWidget {
  @override
  State<PaymentScreen> createState() => _PaymentScreenState();
}

class _PaymentScreenState extends State<PaymentScreen> {
  @override
  void initState() {
    super.initState();
    // Suppress messages during payment
    FirebaseInAppMessaging.instance.setMessagesSuppressed(true);
  }

  @override
  void dispose() {
    // Re-enable messages when leaving payment flow
    FirebaseInAppMessaging.instance.setMessagesSuppressed(false);
    super.dispose();
  }
}
  • Suppression is automatically turned off on app restart.
  • Suppressed messages are ignored — their trigger conditions must be met again after suppression is lifted.
  • Common flows to suppress: payment processing, onboarding wizards, form submission screens.

3. User Privacy and Opt-In Data Collection

By default, In-App Messaging automatically delivers messages to all targeted users.

Disable automatic collection — iOS (Info.plist):

<key>FirebaseInAppMessagingAutomaticDataCollectionEnabled</key>
<false/>

Disable automatic collection — Android (AndroidManifest.xml):

<meta-data
    android:name="firebase_inapp_messaging_auto_data_collection_enabled"
    android:value="false" />

Enable for users who opt in at runtime:

// Call after user consents to data collection
Future<void> enableMessaging() async {
  await FirebaseInAppMessaging.instance.setAutomaticDataCollectionEnabled(true);
}

// Call if user revokes consent
Future<void> disableMessaging() async {
  await FirebaseInAppMessaging.instance.setAutomaticDataCollectionEnabled(false);
}
  • Manually set preferences persist through app restarts, overriding configuration file values.
  • For GDPR compliance, disable automatic collection by default and enable only after explicit user consent.

4. Testing and Debugging

Find the Installation ID

  • Android: Filter logcat by FIAM.Headless — look for Starting InAppMessaging runtime with Installation ID YOUR_INSTALLATION_ID.
  • iOS: Add -FIRDebugEnabled as a runtime argument in Xcode scheme settings. Look for [Firebase/InAppMessaging][I-IAM180017] in the console.

Test a Campaign

  1. In the Firebase console, open the campaign and select Test on your Device.
  2. Enter the Installation ID from the step above.
  3. The test message appears on the next app launch or foreground event.
  • Always test on actual devices for proper rendering and behavior.
  • Test each message type (modal, banner, card, image-only) to verify layout on different screen sizes.

5. Campaign Management

  • Create campaigns in the Firebase console under Messaging > In-App Messaging.
  • Message types: modal, banner, card, or image-only.

Campaign Configuration Workflow

  1. Design — Select the message type and customize appearance (title, body, image, button).
  2. Target — Define the audience by app version, language, user segment, or Analytics-based conditions.
  3. Schedule — Set start/end dates and frequency caps (once, once per session, etc.).
  4. Trigger — Choose the Analytics event that displays the message (e.g., app_open, purchase_complete).
  5. Test — Use device testing before publishing.
  6. Publish — Launch the campaign and monitor performance.
  • Use custom metadata (key-value pairs) to pass additional info accessible when users interact with messages.
  • Use A/B testing to optimize message content, timing, and conversion rates.
  • Monitor campaign performance (impressions, clicks, conversions) through Firebase console analytics.

References

Related Skills

View on GitHub
GitHub Stars670
CategoryAutomation
Updated13d ago
Forks67

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions