January 2016 Summaries

Firebase’s JavaScript SDK added optional, A+-compatible Promise support as an alternative to callbacks, enabling clearer asynchronous code, simpler error handling, and more composable workflows. Firebase operations such as reading data and running transactions can return Promises, allowing developers to chain tasks with `then`, transform returned values, and avoid deeply nested callback structures. Errors can propagate through a Promise chain until handled with a second `then` callback or the `catch` shorthand, while recovery is possible by returning a replacement Promise and failures can be rethrown through rejected Promises or thrown errors. The update also supports `Promise.all()` for coordinating concurrent operations, such as loading an article, its author’s profile image, and a user’s starred status before rendering results and updating a read counter. Although Firebase-returned Promises work across browsers, developers creating their own Promises for older environments may need a library such as Q.

An Ionic and Cordova tutorial explains how to implement Firebase-based social login in a hybrid mobile app while minimizing direct interaction with Cordova’s underlying complexity. It outlines creating an Ionic tabs project, adding Android and iOS platforms, installing AngularFire and the Cordova InAppBrowser plugin, and verifying builds in emulators or Ionic Labs. Firebase is configured by including its JavaScript libraries, registering AngularFire as a module dependency, and creating injectable Firebase and authentication services. The example uses Google OAuth, requiring API credentials to be configured in Firebase, then adds a login controller, template, and route that authenticate users and redirect successful logins to the dashboard. Because native mobile environments do not natively support browser popups, the InAppBrowser plugin automatically handles the window opened by Firebase’s OAuth popup method, displaying the provider’s login page within the app.

Jen Looper presents a tutorial for integrating Eddy Verbruggen’s NativeScript Firebase plugin into a cross-platform Groceries app, replacing Telerik backend services with Firebase for realtime data management. After installing NativeScript and the plugin, developers configure a Firebase URL, initialize the service during login-page loading, and enable email-and-password authentication in the Firebase dashboard. The app then uses Firebase to register and authenticate users, store each user’s generated ID, and simplify validation and error handling through Firebase’s built-in responses. A child-event listener monitors the Groceries collection for additions and deletions, filtering items by user ID so each account sees its own list, while Firebase push and remove operations provide fast creation and deletion of grocery entries. The tutorial also notes that future enhancements could include file uploads, social authentication, and item editing through Firebase value listeners.