Firebase Agency

Firebase is never sold on its own: it is part of the overall budget of your mobile application, whose price depends on the number of screens, the volume of notifications to structure and the authentication methods chosen, email, phone or existing account. An application with simple authentication and generic notifications costs markedly less than a system with user segments and targeted campaigns. Every project is priced on quotation after scoping, with a detailed quote sent within 24 hours.

An application with a limited scope takes 21 to 60 days between scoping and publication on the stores, the time to develop the application, configure the notifications and plug in the authentication chosen. A project with fine-grained user segmentation and several automated campaigns calls for closer to 60 days. This lead time includes validation by Apple and by Google, a stage partly outside our own schedule and which can push the publication date back by a few days.

Firebase avoids rebuilding notifications and authentication from scratch for every application, which speeds up the start and reduces the surface to maintain over time. A solution developed entirely to measure keeps its appeal when your data constraints require depending on no third-party managed service, which remains rare for these three specific uses. We settle this point from the scoping stage, according to your real requirements, your sector and the constraints specific to your end users.

Yes, we start with an audit of the configuration in place: security rules set on the authentication, structure of the notification campaigns already sent, and the measurement events actually tracked compared with those missing. This diagnosis separates a sound configuration from a base to be corrected before adding new functions. A complete reconfiguration remains rare, reserved for projects where Firebase was plugged in with no real plan at the outset and no documented handover from one team to the next.

An optional annual maintenance package can cover Firebase after publication: updating the software kit integrated into the application, monitoring the notification and authentication quotas, and adjusting the events measured if your priorities change. This package is priced according to the actual scope of the project, never at a fixed rate announced without having seen it, and remains optional at each renewal, adjustable if your application gains functions over successive published versions.

Yes. The Firebase project is opened under your Google account from the start, with collaborator access for our team, revocable at any time without depending on us. The authenticated identities, the notification tokens and the events measured remain attached to your account, exportable if you change technical team afterwards. The code of the application itself, developed in Flutter or React Native, belongs to you in full from delivery onwards, with no dependency clause towards our agency.

Visibility for an application does not work like that of a website: Apple and Google index the listing published on their stores, not the internal screens of the application. Firebase intervenes further downstream, on loyalty: a well-targeted notification brings back a user who has already installed it, and usage measurement shows which functions genuinely hold their attention. A higher retention rate also counts in the ranking used by the stores themselves, over successive published updates.