September 2017 Summaries

Firebase CLI version 3.11.0 introduced an experimental Cloud Functions shell that enables local testing of all Firebase function types before deployment, extending capabilities previously limited mainly to HTTPS functions. Using a Realtime Database `onCreate` trigger as an example, the shell can emulate incoming events, automatically supply wildcard parameters such as database push IDs, or accept custom parameter values, while allowing developers to inspect function logs and database writes. It also supports Database, HTTPS, Pub/Sub, Analytics, Storage, and Auth triggers, each with appropriate invocation syntax. Because the shell operates as a full Node.js REPL, developers can reuse command history, run arbitrary JavaScript, load external test files with `require()`, and pipe test scripts into the CLI, though users are encouraged to report issues because the feature remains experimental.

Sprynt, a ridesharing service with an all-electric fleet and free rides funded by local and corporate sponsors, partnered with Savvy Apps to build a platform capable of real-time rider-driver coordination and scalable operational management. The agency selected Firebase for its Realtime Database, which supported synchronized apps, GPS tracking, and ride-request queues, while Firebase Authentication enabled streamlined phone-number sign-up and Firebase Cloud Messaging handled automated and administrative notifications. Additional Firebase services, including Cloud Functions, Cloud Storage, Analytics, and management dashboards, helped Sprynt process service-area updates, monitor user behavior, and operate with limited ongoing developer support. During its first pilot month, Sprynt reportedly served about 5,000 passengers, maintained a five-star app rating, and attracted growing demand from riders, advertisers, and drivers. Although Firebase Realtime Database had limitations for complex filtering and sorting queries, Savvy Apps considered its real-time synchronization and integrated tools effective for rapidly launching and expanding the service.

Crashlytics, available through the Fabric dashboard, offers tools to help app teams identify, prioritize, and resolve stability problems more efficiently. Its crash insights feature provides possible root causes and troubleshooting resources, while closing resolved issues enables regression detection if they return in later app versions; teams can also close and lock low-priority or external issues to reduce dashboard clutter. Wildcard build searches simplify analysis across similarly named builds, and pinned builds keep important releases visible for the entire team. Velocity alerts notify developers through the dashboard, email, and mobile push notifications when an issue rapidly increases in impact. The Crashlytics SDK also supports logs for pre-crash activity trails, keys for the latest state values or summaries, and non-fatal reports for actionable errors requiring stack traces, while custom events are better suited to counting occurrences without diagnostic traces.

FriendlyPix is an open-source narrative app intended to help developers move beyond Firebase quickstarts by demonstrating how multiple Firebase products work together in a realistic application. Available for Android, iOS, and web, it uses services including Analytics, Cloud Messaging, Cloud Functions, Authentication with FirebaseUI, Realtime Database, Storage, Remote Config, Invites, and AdMob. The project showcases practices such as FirebaseUI authentication, database indexing, fan-out writes to prevent race conditions, flat denormalized data structures, filtered queries, lazy-loading feeds, and coordinated image storage with Cloud Functions. Developers can review its design documentation and source code on GitHub, try the hosted web version at friendly-pix.com, ask questions through Stack Overflow, report issues in platform-specific repositories, and contribute according to the project’s contributor guidelines.

Firebase Dynamic Links, which direct users to specific locations in iOS or Android apps including after installation, has introduced several improvements focused especially on iOS usability and measurement. Updates include a redesigned App Preview page for users without the iOS app, using App Store or custom assets to improve click-throughs while retaining options to bypass the page; clearer error messages linked to relevant documentation; and an iOS diagnostic function that identifies common configuration issues. Analytics for short links now distinguish total clicks, app reopens, and first-time app opens, with data available through both the Firebase Console and REST API and compatible with UTM attribution in Google Analytics for Firebase. Additional recent enhancements include a link-debugging flow chart, REST analytics access, and improved on-the-fly link-building tools for both iOS and Android.

Smash.gg, an esports platform supporting nearly 2,000 monthly events and more than 60,000 competitors, adopted Firebase in 2016 after an unreliable third-party chat service exposed the need for dependable real-time tournament interactions. Firebase Realtime Database synchronized match status between players, while a Firebase-based chat feature was built and productionized within days; Firebase Cloud Messaging and Cloud Functions later enabled browser notifications for events such as moderator requests. After evaluating Google Cloud Platform at Google Cloud Next 2017, the company migrated key systems to Container Engine, Kubernetes, Pub/Sub, Cloud SQL, Datastore, BigQuery, and Stackdriver, using the transition to re-architect core services. Although moving from its prior platform removed some built-in application metrics, Smash.gg recreated them through Stackdriver log-based metrics and BigQuery, and also assembled an interim asynchronous tracing workflow using logs, Pub/Sub, Cloud Functions, and the Trace API. After one month in production on GCP, the company reported roughly 10% lower costs without committed-use discounts, available capacity, centralized logging that accelerated troubleshooting, and improved ability for engineers across the team to handle DevOps work.