Sound familiar?
What teams with apps built on Firebase tell us before a project starts.
- Sign-in works for most people and fails for a few, and we cannot see why.
- Our Firestore bill climbs and nobody knows which screen is reading so much.
- Anyone could read our database at the start and we are not sure the rules are right now.
- Push notifications arrive late on some phones or not at all.
- The developer who built the app is gone and the code has no notes.
What we build
Each one is a working piece you can open and check when it's done.
Authentication that holds up
Email, phone, Google and Apple sign-in, password reset, account linking and sensible handling of the odd cases, such as users who sign up twice.
Web apps and MVPs Website bug fixesFirestore data and security rules
Collections reshaped for the questions your app asks, indexes added, and security rules written and tested so each user sees only their own data.
Web apps and MVPsCloud Functions for the background work
Triggers that send emails, call outside services, resize images, take payments or sync records when data changes, with retries and logs.
API integrations and data sync n8n, Make and Zapier automationPush notifications
Firebase Cloud Messaging set up for iOS, Android and web, with topics, quiet hours and a record of what was sent to whom.
Mobile apps for iPhone and Android Web apps and MVPsRepairing and extending existing apps
Crashes, slow screens and failed deploys traced, repaired and written up, with new features added in small steps you can test.
Website bug fixes Lovable, Bubble and Replit app rescueMigrations in and out
Moving data between Firebase and Postgres, Supabase or another Firebase project, with counts compared before and after cutover.
ETL and data pipelines Python scripts and utilitiesWhat we connect it to: Stripe, Supabase, Google Sheets, Zapier, Make, Twilio, SendGrid.
Industries that use it: SaaS startups, Fitness, Schools and tutoring, Online courses.
Full detail: Mobile apps for iPhone and Android.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Booking app that stopped sending reminders
Example: a studio's mobile app has reminders that stopped after a library update. We trace the function, repair it, add a log of each send, and test on both phone platforms.
Firebase Cloud Functions, FCM, FirestoreExample project
Moving a small app off the Realtime Database
Example: a coaching app stores progress data in the Realtime Database and needs queries it cannot do. We plan a move to Firestore, copy the data in stages and run both until the counts agree.
Firebase, Node.js scriptsExample project
Rules review for a members app
Example: a community app lets members message each other. We read the security rules, write tests for what each role may read or write, and close the gaps we find.
Firestore rules, Firebase emulatorQuestions people ask first
Can you take over an app someone else built?
Usually. We read the code and the Firebase project first, then send you a short note on what we found and what we would change before we touch anything.
Do we have to stay on Firebase?
No. If it suits your app we keep it. If another database serves you better, we lay out the options and you decide.
Will our users lose anything in a migration?
We copy and compare first, run both side by side where we can, and agree a cutover time with you. Nothing is switched off until the counts match.
How do we start?
Tell us what the app does and what is going wrong, or what you want it to do next. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com