If you have legacy Adobe AIR apps, updating them might seem intimidating. You need modern backend capabilities to track user behavior and send notifications when they matter, but native ecosystems move fast. Fortunately, there is an easy way to bridge the gap. With an AIR Native Extension, this connection can be made directly from your app to modern Firebase services without having to rewrite your codebase. No need to spend hours on research, we have listed all the stages you should go through.
Setting up your core integration
Getting Firebase to talk to your ActionScript code takes just a few configuration steps. Here is how to handle the setup for both Android and iOS platforms:
- Register your app: Head to the Firebase Console. Add your iOS and Android app bundle IDs. Download the Google-services.json file for Android and the GoogleService-Info.plist file for iOS.
- Update platform requirements: Firebase native SDKs require specific OS versions. For iOS, update your app descriptor XML to include <key>MinimumOSVersion</key><string>12.2</string>. For Android, ensure your minimum SDK targets API 19 or higher.
- Package the files: Include the downloaded configuration files in your root app directory before compiling. Link the Firebase ANE library in your IDE settings.
Google Analytics for AIR
Tracking user behavior allows you to make informed updates. The ANE integrates seamlessly with Firebase Analytics to track engagement.
- Initialize the SDK. Call the Firebase initialization method in your app when it finishes!
- Log custom events: Track specific actions with simple ActionScript commands, such as completing a level or making a purchase.
- Check your data: Events are sent directly in batches to Firebase at the maximum upload rate, reducing battery consumption. If you wish, you can view user retention and engagement directly in the Firebase console.
Firebase Cloud Messaging (FCM)
Push notifications make it easier to re-engage users. FCM handles message delivery across various devices.
- Request Permissions: Always ask users for notification permissions first on iOS.
- Get token: Get the unique device registration token and store it in your database.
- Listen for payloads: Register ActionScript event listeners to receive incoming messages when the app is in the foreground, or simply handle the payload when the user taps a notification in the background.
FCM vs. standard WebSockets
One question developers frequently have about their apps is whether to use persistent WebSockets over native push notifications. Mobile devices are aggressively managed by operating systems to keep them battery-efficient. Here is exactly how ANE-based FCM works compared with standard WebSockets on Android and iOS.
| Metric | ANE-based Push (FCM / APNs) | Standard WebSockets |
| Background Network Access | System-managed delivery (Wakes app) | Suspended entirely during Android Doze |
| Pending Message Queue | Stores up to 100 messages per app instance | None (Messages lost if connection drops) |
| Message Time-to-Live (TTL) | Retained on servers for up to 28 days | Fails instantly on disconnect |
| Inactive Device Handling | ~15% drop rate if tokens go unmanaged | 100% failure rate when app is closed |
Strategic advice for modern developers
If you’re all about optimizing your tech stack, then you know that keeping persistent connections is a fast way to suck dried batteries. This is a much more clever move that offloads this work to OS-level services such as FCM. Alpha geeks seeking additional tips for optimizing their digital setups can find excellent insights at digitalconnectmag. com. They provide real-world tech tips on everything from setting up a VPN account to digital privacy and streaming alternatives.
Bringing new life to legacy apps
Adobe AIR is still a very capable platform for cross-platform SaaS deployment as long as you maintain with the Harman SDKs. Integrating Firebase via native extensions allows your app to leverage analytics and push notifications as a fully native app would. It is a great, low-cost way to keep your project at the cutting edge.
FAQs
Do Firebase ANEs support 64-bit architectures?
Yes. But 64-bit is a requirement for all app updates, as Apple and Google are not about to budge on it. Modern Firebase ANEs are designed to run in 64-bit architectures, and you need Adobe AIR 33+ (from Harman) to package them correctly.
Why are my iOS push notifications not arriving?
Check your provisioning profiles. For iOS, you need a Push Notification entitlement associated with your App ID. Also, you must upload your APNs authentication key to the Firebase Console.
How do I fix ANE packaging conflicts on Android?
Double. If you see a “multiple dex files” error, you likely have a duplicate of the Google Play Services dependency. Make sure that your Firebase ANE is the only thing wrapping those particular Android support libraries.
Can I use Firebase security rules with AIR?
Absolutely. For Firestore or Realtime Database, if you access them through an ANE, your security rules should already be configured in the Firebase Console. Your users authenticate natively with your AIR app, and access is automatically enforced by the backend rules.
Why are messages dropping due to inactive devices?
FCM will discard messages if a device has been offline for extended periods. Firebase suggests regularly updating registration tokens on your server and removing stale tokens in order to keep delivery rates high.