October 2016 Summaries

Firebase announced the full speaker lineup and agenda for its first Firebase Dev Summit, scheduled for Monday, November 7. The day-long event will include talks, codelabs, and office hours covering topics such as building reliable Firebase apps, Firebase Analytics, and mobile development without infrastructure, followed by an afterparty with music and networking opportunities. Although tickets are sold out, interested attendees can join a waitlist, while the full event will also be livestreamed with optional session-start email alerts. Participants are additionally invited to discuss the event through Slack and Twitter.

Firebase released updates to its iOS, Android, and JavaScript SDKs, including Firebase Analytics screen tracking that automatically records screens through view controllers or activities while allowing developers to define screens manually. Crash reporting for iOS now supports Swift 2 and Swift 3, and the Firebase console adds project nicknames and configurable currency settings for analytics reports. Dynamic Links also gains a REST endpoint for automatically shortening created links, alongside various bug fixes across the platforms.

Firebase has introduced a self-service Private Backups interface for Blaze plan customers that enables daily exports of Firebase Database application data and rules to a Google Cloud Storage bucket. Available through the Database section’s Backups tab, the setup wizard supports default Gzip compression and an optional 30-day lifecycle policy to reduce storage costs, while the console provides backup status, history, and a Manual Backup option for on-demand snapshots. The exported JSON backups can support offline scripting and analysis without affecting live database performance, enable historical trend analysis, and help recover from data loss or corruption by downloading and importing a prior backup. Compressed files must be decompressed before import, and Firebase recommends contacting support for restoration of very large databases.

Firebase announced a JavaScript library that extends Firebase Cloud Messaging to web browsers supporting the Push API, allowing developers to send notifications beyond Chrome to Firefox, Opera, and other compatible browsers. The library simplifies implementation by handling functions such as payload encryption and service workers, while offering default configurations that developers can later customize. It also brings FCM features previously available for native apps to the web, including single-device messaging, topic messaging, and device group messaging, enabling campaigns across Android, iOS, and web users. At launch, support includes Chrome 50+, Firefox 44+, and Opera Mobile 37+, with broader coverage expected as browser support for relevant web standards expands. Early adopters including Alibaba.com, AliExpress, and Settle Up reported improved engagement, open rates, and conversions after implementing web notifications, and FCM is available free as part of Firebase.

Firebase Authentication natively supports Google, Facebook, Twitter, and GitHub, but integrating Instagram or other OAuth 2.0 providers requires a custom server-side flow. The process involves registering an app with Instagram, configuring authorized callback URLs and OAuth credentials, opening an Instagram consent screen in a popup, and validating a state parameter stored in a secure cookie to mitigate session-fixation attacks. After Instagram redirects the user back with an authorization code, a Node.js backend exchanges it for an access token and user profile information, then uses Firebase service-account credentials to generate a custom Firebase authentication token based on the Instagram user ID. A callback page signs the user in with that token, stores the Instagram access token securely in Firebase Realtime Database if needed for API access, updates the Firebase profile with the Instagram name and photo, and closes the popup, allowing the main application to recognize the authenticated user across tabs.

Firebase Remote Config can personalize app content by targeting users through Firebase Analytics audiences or, more flexibly, user properties. While audiences support complex combinations of events and properties, they are limited to 50 shared groups and users cannot leave once they join, making them less suitable for dynamic targeting such as player progression. User properties enable many smaller, adjustable Remote Config conditions, allowing apps to tailor experiences based on changing values like preferred fitness activities or game levels without consuming audience slots. These properties are stored as strings but can be evaluated with string or numeric comparisons when their values can be converted to numbers, and Remote Config conditions can be updated quickly through the Firebase console.

Firebase Realtime Database security rules can restrict private group-chat or shared-content access by checking whether an authenticated user appears in a chat’s membership data. The example uses wildcard chat IDs and role-based member entries to allow all members to read messages while permitting only designated owners or chatters to write, favoring explicit allowlists over blocklists to reduce risks when new roles are introduced. It outlines several membership-management models, including allowing any existing member to add users, limiting additions to owners, and using a pending-request list where users can request access and owners approve them. The rules also support safely creating a new chat by allowing an authenticated user to establish an empty members list only when adding themselves as its owner. The discussion emphasizes testing rules through Firebase’s Rules Simulator before deployment and notes possible further validation, such as restricting role assignments and message formats.

Firebase announced its first Dev Summit in Berlin on November 7, inviting app developers to register for the free event while spaces remain available. The summit will feature product announcements and previews of new Firebase releases, opportunities to meet founders, product managers, and engineers, and sessions covering topics such as growth, app quality, infrastructure-free development, and new-feature training. In partnership with Women Techmakers, Firebase is offering travel grants for women in technology to support diverse attendance. Participants will also have opportunities to network with other developers, while those unable to attend can sign up for livestream updates and watch the event online.

Play Services Task API can integrate asynchronous work that does not natively return a Task by using TaskCompletionSource, which supplies a placeholder Task that external threads, callbacks, or delayed operations can complete successfully with setResult() or fail with setException(). This enables disparate work, such as Firebase Realtime Database listeners, Remote Config fetches, and timed splash-screen delays, to be handled through a consistent listener-based model. The post demonstrates combining these operations in parallel with Tasks.whenAll(), which produces a single completion Task that succeeds only after every component succeeds or fails if any component fails, allowing an app to proceed efficiently once data and timing requirements are met. Individual task results remain accessible from their original Tasks, while the aggregate Task coordinates completion. Although Tasks.await() can synchronously block a background thread until a Task finishes or times out, it should never be used on Android’s main thread.