Use this roadmap when iOS users show real demand but one native surface cannot solve both context capture and composer insertion.
Roadmap
iOS keyboard + Share Extension roadmap
The iOS keyboard + Share Extension roadmap should follow mobile web and Android validation. The Share Extension should handle context capture from social apps, while the iOS keyboard helps insert selected drafts back into the composer. The roadmap should keep copy fallback, user editing, and manual final posting visible.
Last updated: July 11, 2026. Roadmap pages do not claim native app-store availability unless explicitly proven.
Strategic fit
When this roadmap matters
Phases
Roadmap phases and success gates
Phase 1
Phase 1: iOS demand proof
Before native build
Confirm iOS users are a strong enough segment to justify native review and permission complexity.
iOS mobile web tracking
Share intent research
Keyboard friction notes
Roadmap disclosure
Success metric: iOS mobile users generate, copy, and request a better native path.
Phase 2
Phase 2: Share Extension context path
Native context prototype
Make passing source-post context into TypeToSell easier than manual copy/paste.
Share Extension prototype
Context preview
Draft generation handoff
Privacy explanation
Success metric: Users can start from a social post and reach useful drafts with less friction.
Phase 3
Phase 3: keyboard insertion path
Composer prototype
Return selected drafts to the reply composer while preserving user review.
Keyboard insert action
Copy fallback
Manual posting reminder
Beta analytics
Success metric: Users insert, edit, and manually post selected drafts without confusion.
Risks
Roadmap risks and mitigations
Keyboard-only build
Risk: It may not solve post-context capture.
Mitigation: Pair keyboard with Share Extension.
Share-only build
Risk: It may not solve composer insertion.
Mitigation: Keep keyboard or copy fallback.
iOS too early
Risk: Native complexity can arrive before demand.
Mitigation: Require mobile web and Android learning first.
Decision gates
What proves the next phase is ready
Start iOS discovery
iOS users show mobile web usage and ask for native support.
Build Share Extension
Context capture is the main iOS friction.
Build keyboard
Composer insertion becomes the main iOS friction after context capture.
Related reading
Connect this roadmap to the wider SEO graph
iOS workflow/workflows/ios-keyboard-share-extension-workflowiOS keyboard + Share Extension page/mobile/ios-replypilot-keyboard-share-extensioniOS keyboard vs Share Extension decision/decisions/ios-keyboard-vs-share-extensioniOS keyboard vs Share Extension guide/guides/ios-keyboard-vs-share-extension-guide
FAQ
Roadmap questions
Why combine iOS keyboard and Share Extension?
The Share Extension helps capture context, while the keyboard helps place selected drafts into the composer.
Should iOS native work come first?
Usually no. It should follow mobile web and Android validation unless iOS demand is clearly stronger.
Can iOS native workflows auto-post?
No. The user should still review, edit, and manually publish.