| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| In-app messaging and customer communications | Customer | 2% | 15 of 105 | 18% | 11 | accepted challenger | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Mobile apps | Marketing | 0% | 29 of 117 | 0% | 7 | under 10 labels · led by Customer.io at 17% | ▼−2Since September 2026: 2% → 0%, −2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Experimentation and personalization | Marketing | 0% | 45 of 71 | 0% | 1 | under 10 labels · led by VWO at 27% | newNew since September 2026: not ranked then, 0% now. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Mobile apps | 2% | 0% | ▼−2Since September 2026: 2% → 0%, −2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 11 → 29 of 117 |
| In-app messaging | 0% | 2% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 22 → 15 of 105 |
| Experimentation | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 45 of 71, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 1 | 0 | 1 | 0 | 2 |
| GPT-5.4 mini | 0 | 1 | 1 | 0 | 2 |
| Gemini 3.5 Flash | 0 | 0 | 1 | 1 | 2 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.20 | 0 | 1 | 1 | 0 | 2 |
| Mistral Small | 0 | 0 | 3 | 0 | 3 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 0 | 1 |
| Kimi K2 | 0 | 0 | 0 | 1 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 1 | 0 | 1 |
| MiniMax M2.5 | 0 | 1 | 1 | 0 | 2 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“OneSignal or Firebase are ideal starting points since they offer generous free tiers” Claude Haiku 4.5 · In-app messaging · budget prompt · first choice
“Many analytics tools like Firebase (free tier available) ... have built-in attribution that allows you to track referral links easily.” Qwen 3.7 Flash · Mobile apps · budget prompt · alternative
“Completely free for in-app messaging (via Cloud Messaging/FCM)... perfect for very small budgets but requires more dev work.” Grok 4.20 · In-app messaging · budget prompt · alternative
“OneSignal or Firebase would be the top recommendations due to their genuinely useful free tiers” MiniMax M2.5 · In-app messaging · budget prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“OneSignal/Firebase: Too lightweight for B2B product messaging” Kimi K2 · In-app messaging · paraphrase prompt · hard negative
“Firebase Realtime Database caps out at 200,000 concurrent connections. Sharding a database to get around this limit is a complex architectural nightmare.” Gemini 3.5 Flash · In-app messaging · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 40 of the 44 answers that named Firebase and are not a share of its labels.
118 of the 118 domain citations in answers naming Firebase came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Fetched September 14, 2026, with a correction applied. These describe the company, not the product's standing, and a claimed page can dispute any of them. · Wikidata
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Firebase's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Firebase, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Firebase by email, built from the raw record of the edition. It shows: