December 2012 Summaries

Firebase introduced a Security API intended to let developers build secure real-time applications in which clients access Firebase directly, often without requiring server-side code. The API combines flexible authentication methods, including server-signed tokens, Firebase Simple Login, and third-party providers, with centrally managed Firebase Rules that control read, write, and data-validation permissions. Written as JavaScript-like expressions and stored as JSON, rules can use database data, incoming values, authentication credentials, and server time to enforce permissions and schemas consistently at scale, while supporting static analysis and predictable performance. Firebase also highlighted security implementation measures such as SSL, 2048-bit certificate keys, SHA256 HMAC token signing, BCrypt password storage, and JSON Web Tokens. Alongside the API, it launched a rules debugger called Forge, a security simulator for testing authentication and data operations, and firebase.github.io for reusable examples, libraries, and code snippets.

Firebase participated in the Silicon Valley AngelHack event at PayPal’s San Jose headquarters, where its team distributed more than 400 beta invitations, supported participants through a booth and breakout session, and provided overnight assistance. The two-day hackathon produced 85 submissions, with 57 teams using APIs and 25 using Firebase, making it the most-used API at the event. Firebase-powered projects included finalist Rohan Pai’s FireMap, which created real-time website behavior heatmaps, while prize-winning teams included Reboxed, which repurposed old phones as sensors with alert capabilities, and LevelUp, a fitness coaching application. Other commonly used services included Filepicker.io, KeenIO, and Singly, and the event highlighted how third-party APIs can help developers focus on product development rather than backend infrastructure.