Marketing Automation Tools and App Engineers — Automating Pushes and Notification Dialog Operations
summary
A marketing automation SDK used in 48 countries (≈3,800 installs) describes engineering solutions for push notifications and in‑app announcement automation: resolving FCM/GCM version conflicts by adding a compile‑only Gradle configuration and making some libraries compile‑time‑only to avoid runtime crashes; exposing an API so apps control registration token retrieval to prevent unexpected background calls; integrating with Cocos2d‑x for cross‑platform builds; adding manifest‑level checks for multiple push SDKs; and automating builds and tests (Espresso, XCUITest, Appium) while documenting targetSdk and long‑text layout behaviors.
AI-written summary · about
chapters (7)
- 0:00Marketing automation tools
- 2:43Push SDK conflicts
- 11:28SDK integration risks
- 16:13Android dialog challenges
- 19:32Cross-platform push SDKs
- 24:59Push notification testing
- 30:02Summary & Q&A
related talks
28mUsing Communication APIs to enhance your UX (and reduce notifications!)
30mApp Actions
24mDriving Adoption by Generating High Value Notifications in Backstage
41mUniversal Pushes for Android: FCM, HMS and RuStore in One Place
25mGrowth Hacking with Firebase
22mEngage your users with targeted notifications
30mAutoMobile
38mPush Notifications that Don’t Suck