Use this matrix when evaluating whether an iOS Share Extension, an iOS keyboard, or both should handle mobile reply generation.
Scoring matrix
Share Extension vs keyboard context matrix
A Share Extension vs keyboard context matrix should treat the two iOS surfaces as complements. The Share Extension scores highest for sending source-post context into TypeToSell, while the keyboard scores highest for inserting selected drafts into a composer. The best iPhone roadmap pairs them after mobile web validation and keeps copy fallback available.
Last updated: July 11, 2026. 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 |
|---|---|---|---|---|---|
| Source-post context capture | 3/5 | 2/5 | 5/5 | 3/5 | The Share Extension side is strongest for moving source context into the generator. |
| Composer insertion | 3/5 | 5/5 | 4/5 | 3/5 | The keyboard side is strongest for placing selected draft text where the user replies. |
| Fallback reliability | 5/5 | 4/5 | 4/5 | 4/5 | Copy fallback should remain available when native context or insertion is limited. |
| Permission explanation | 5/5 | 3/5 | 3/5 | 4/5 | Native surfaces need more visible privacy and manual-posting explanation than mobile web. |
| Best iPhone coverage | 3/5 | 1/5 | 5/5 | 3/5 | The pair wins on iPhone because it separates context handoff from text insertion. |
Selection rules
How to choose the winning path
Rule 1
Use Share Extension for context
When the user starts from a social post and needs to pass visible source text into TypeToSell.
Rule 2
Use keyboard for insertion
When the user is already in a reply composer and needs to insert or revise a selected draft.
Rule 3
Use both for iOS coverage
When iPhone demand is proven and the team can maintain the paired workflow.
Rule 4
Keep copy fallback
When API, permission, or UX limitations make direct insertion unreliable.
Risk checks
What can make the matrix lie?
Keyboard-only context gap
A keyboard can be near the composer but still lack the post context.
Pair with Share Extension or explicit user-provided context.
Share-only insertion gap
A Share Extension can capture context but may not return text smoothly.
Keep keyboard insertion or copy fallback.
Hidden posting assumption
Users may confuse insertion with publishing.
Repeat that final posting stays manual.
Related reading
Continue the decision path
FAQ
Matrix questions
Is Share Extension better than keyboard?
It is better for context handoff, while the keyboard is better for composer insertion.
Should TypeToSell build both for iOS?
Yes, but only after mobile web validation shows iPhone demand strong enough for native complexity.
Can either iOS surface auto-post?
No. Both should support selected draft generation or insertion while the user makes the final post manually.