January 2017 Summaries

Debugging Firebase Cloud Messaging on iOS requires isolating failures across the delivery chain from an app server or Firebase Notifications through FCM, Apple Push Notification service (APNs), iOS, and the target app. The guide recommends first disabling explicit FCM foreground connections to avoid masking APNs issues, then adding app-delegate logging to verify APNs registration, device-token receipt, and common configuration mistakes such as simulator testing, missing push capabilities, or failure to register for remote notifications. Developers should confirm that users have granted notification permissions, test delivery directly through APNs using an HTTP/2 curl request and the correct certificate, bundle ID, and device token, and then test FCM separately using a Firebase server key and registration token. Although an FCM success response confirms message acceptance, device delivery must still be verified, with attention to token errors, iOS priority settings, proper FCM rather than APNs payload syntax, valid uploaded APNs certificates, and correct handling of silent notifications. If direct APNs and FCM tests work but Firebase Notifications or a custom server does not, the remaining investigation should focus on Firebase service status, message formatting, or server-side implementation.

Firebase Test Lab introduced several Android testing enhancements in early 2017 to improve test customization, efficiency, and cost control. Sparse device matrix selection lets developers choose only specific device and API-level pairings rather than automatically testing every possible combination, making it easier to rerun tests only where failures occurred. Saved matrix templates allow frequently used device configurations to be stored and reused for future tests. Robo tests also gained custom text-input support, enabling automated entry of credentials, search terms, and other strings into EditText fields identified by Android resource IDs, which can help Robo navigate custom login screens and app workflows, although the capability does not support WebView elements.

Firebase Remote Config implementation involves setting local default values, fetching updated cloud values, and activating fetched values, but network delays require apps to choose an appropriate loading strategy. Developers can activate and refresh immediately, use a startup loading screen to ensure fresh values before users enter the app, or activate previously fetched values at launch while asynchronously downloading updates for the next session; hybrid approaches can use the age of the last fetch to determine which method to use. Remote Config caches values, typically for 12 hours, and throttles frequent requests to preserve service capacity, prevent accidental overuse, and reduce users’ battery and data consumption, while developer mode can relax local throttling during testing. For highly time-sensitive content, Firebase Realtime Database may be more suitable, while urgent but infrequent Remote Config updates can be prompted through Firebase Cloud Messaging by flagging clients to perform an uncached fetch on their next app launch rather than triggering simultaneous fetches across all devices.

Google announced an agreement to acquire Fabric from Twitter and integrate its team into Google’s Developer Product Group alongside Firebase, aiming to simplify mobile app development across iOS, Android, and the web. Firebase had recently expanded and enhanced services including Analytics, Test Lab, Cloud Messaging, and support for game developers through C++ and Unity tools. Fabric’s Crashlytics is expected to become Firebase’s primary crash-reporting solution, while Fabric’s other products, such as Answers and Fastlane, may complement Firebase’s broader platform as the companies determine integration plans after the deal closes. Twitter will continue maintaining Digits, Fabric’s SMS authentication service, during the transition, while Google frames the acquisition as part of a long-term effort to provide developers with a comprehensive suite of tools for building, growing, and monetizing apps.

Rather than making New Year’s resolutions, the author encourages developers to use 2017 as an opportunity to improve mobile app quality, defined through reliability, user delight, and ultimately app-store ratings. Firebase Crash Reporting can identify user-facing crashes for developers to fix, while Firebase Test Lab for Android enables testing on real devices, either through uploaded test suites or automated Robo tests, before problems reach users. Firebase Remote Config supports safer feature rollouts by gradually enabling functionality for selected users and quickly disabling it if crashes or negative feedback emerge, and it can also facilitate experiments measured with Firebase Analytics to determine user preferences. Finally, Firebase Realtime Database can improve user experience by delivering live updates through reactive listeners rather than repeated polling, reducing manual refreshes as well as battery and data use.