Firebase
Firebase development
Firestore, Cloud Messaging, auth and analytics, on the apps where Firebase is already the backend.
Part of backend and api developmentI have used Firestore where it is the right tool rather than the default one: the real-time half of an app, with the request/response half left on a REST API. On The R&I Guys that split is chat, attachments and presence on Firestore, and the posts, comments and upvotes on a REST backend, because a feed with pagination and moderation is not a thing Firestore listeners are good at.
I write the Android half of push in Kotlin as a native module rather than wiring it together in JavaScript, because permission requests, token registration and background message handling are the three places where the JavaScript-only approach quietly stops working.
What that covers
- Firestore data modelling and security rules
- Cloud Messaging on both platforms, including background handling
- Firebase Authentication, including on legacy codebases
- Crashlytics and Analytics wired to something someone reads
- Migration paths off Firestore when a product outgrows it
Where this has shipped
The R&I Guys
Inara Consultancy Services, 2025
A social app for four-wheeler repair and replacement work, built end to end and shipped to the stores.
How it is built
Revolt Summit and Streaming
Inara Consultancy Services, 2022 to 2023
Two apps for one brand: a live event platform and a streaming service, with offline video and deep links on both.
How it is built
Next: Cloudflare Workers
Tell me what you are building.
A sentence about the product and where it is stuck is enough to start. I answer every mail myself, including the ones where the answer is that I am not the right person.