Firebase is Google's mobile and web backend platform — Firestore (NoSQL document database), Authentication, Cloud Storage, Cloud Functions, Firebase Hosting, Firebase Analytics and Firebase Cloud Messaging (push notifications). We use Firebase selectively — primarily for push notifications (via FCM), crash reporting (Crashlytics) and remote configuration in React Native and Flutter projects.
Why we chose it
Why Ascii-Core uses Firebase
1
Firebase Cloud Messaging (FCM) is the industry-standard push notification delivery for Android and iOS
2
Crashlytics provides real-time crash reporting with symbolicated stack traces for React Native and Flutter
3
Remote Config enables feature flags and A/B tests without app store update cycles
4
Firestore real-time listeners suit highly collaborative, high-frequency update use cases
Ideal use cases
When to use Firebase
Push notification delivery in mobile applications
Crash reporting and performance monitoring for React Native and Flutter
Real-time collaborative features (live cursors, shared state, chat)
Feature flags and remote configuration in mobile apps
Projects already committed to the Google Cloud ecosystem
Trade-offs
Honest limitations
We believe in accurate trade-offs. These are the cases where a different tool may be the better choice.
Firestore is NoSQL — relational queries, joins and transactions are painful or impossible
Pricing is per-read/write — costs can scale unexpectedly with high-frequency operations
Vendor lock-in to Google Cloud — migration to another provider is expensive
Firebase Auth has limitations for enterprise SSO compared to Auth0 or Clerk
Services
Services using Firebase
Ascii-Core service offerings where this technology plays a central role.