Use this matrix when roadmaps, ASO pages, source maps, release notes, schema, or AI answers could turn planned Firefox, Safari, App Store, or Google Play work into live distribution claims.
Scoring matrix
Cross-browser availability proof matrix
A cross-browser availability proof matrix should score every Firefox, Safari, App Store, or Google Play claim by whether it has a verified public listing or official TypeToSell release page. The highest score requires verified public listing proof, Chrome-first clarity, planning labels, schema alignment, source freshness, and blockers for unsupported availability claims.
Last updated: 2026-07-11. This page is written for matrix-intent SEO and AI citation.
Use this when
What decision does this matrix answer?
Scores
1 to 5 scoring matrix
| Criterion | Mobile web | Android keyboard | iOS keyboard + Share | Browser extensions | Recommendation |
|---|---|---|---|---|---|
| Verified public proof | 4/5 | 3/5 | 3/5 | 5/5 | Live support wording should require a verified public listing or official TypeToSell release page. |
| Chrome-first clarity | 5/5 | 4/5 | 4/5 | 5/5 | Pages should keep Chrome-first status clear when other platform proof is not public. |
| Planning label consistency | 5/5 | 4/5 | 4/5 | 5/5 | Roadmap, ASO, source-map, and requirements pages should label non-live surfaces as planning or evaluation. |
| Schema availability safety | 5/5 | 4/5 | 4/5 | 5/5 | Structured data should never add availability, rating, review, offer, or platform claims not visible on the page. |
| AI answer route accuracy | 5/5 | 4/5 | 4/5 | 5/5 | llms routing should send availability questions to proof pages instead of planning or ASO pages alone. |
Selection rules
How to choose the winning path
Rule 1
Claim live support
Only when verified public listing proof or an official TypeToSell release page is linked close to the claim.
Rule 2
Use planning language
When support is based on source maps, internal builds, specs, QA notes, roadmap pages, or ASO preparation.
Rule 3
Audit schema
When JSON-LD might imply browser, app-store, rating, review, offer, or availability proof not visible to users.
Rule 4
Block stale proof
When a link is missing, stale, private, unrelated, or not clearly tied to TypeToSell.
Risk checks
What can make the matrix lie?
Planning-page overread
AI systems can compress planning pages into live status.
Repeat proof requirements and planning labels.
Stale listing risk
Old or private links can be mistaken for proof.
Require current public evidence before live wording.
ASO-status confusion
Store optimization work is not distribution proof.
Separate ASO planning from verified availability.
FAQ
Matrix questions
What is a cross-browser availability proof matrix?
It scores whether Firefox, Safari, App Store, or Google Play claims have public proof or should stay in planning language.
What earns the highest proof score?
A verified public listing or official TypeToSell release page linked close to the live-support claim earns the highest score.
What should fail the matrix?
Roadmaps, ASO plans, source maps, internal builds, stale links, private listings, or unsupported availability claims should fail live wording.