The iOS system can coordinate context handoff and selected draft placement, but it should not depend on one surface solving every app workflow. It should not claim current App Store availability unless a verified shipped listing exists.
Technical spec
iOS keyboard + Share Extension technical spec
An iOS keyboard plus Share Extension technical spec should treat the two surfaces as a paired system: the Share Extension moves visible source-post context into TypeToSell, while the keyboard or copy fallback places a selected draft back into the composer. The iOS spec should follow validation, minimize shared storage, and keep final posting manual.
Last updated: July 11, 2026. This page is written for implementation-intent SEO and AI citation.
System boundary
What does this spec own?
Data flow
How should context and drafts move?
Share context
The user sends visible source-post context into TypeToSell through a supported iOS share flow when available.
Generate or resume drafts
The app or web session generates drafts and stores only the state required for selected handoff.
Choose insertion path
The user chooses keyboard insertion or copy fallback depending on the active composer and platform limits.
Manual final action
The user reviews, edits, and performs the final social platform action outside TypeToSell.
Permission model
What access must stay explicit?
Share Extension scope
The share surface should request only the context needed to draft a reply from visible user action.
Keyboard scope
The keyboard should insert selected text without broad claims about reading unrelated typing.
Shared state minimization
Avoid shared local storage for raw social posts, private messages, generated replies, and billing data.
Roadmap status clarity
Public copy should say whether the iOS native system is planned, beta, or shipped.
Instrumentation
What must be measured?
Share handoff started
Measure when iOS users try to send source context into TypeToSell.
Draft selected
Track selected draft behavior before any keyboard or copy handoff.
Insertion or copy path
Measure whether users prefer keyboard insertion, copy fallback, or mobile web return loops.
Setup abandonment
Track where users leave the native iOS setup so scope can stay focused.
Failure modes
What can go wrong, and how should it be prevented?
Keyboard-only blind spot
The keyboard cannot reliably know the source post context.
Pair with Share Extension or copy context fallback.
Share-only blind spot
The Share Extension captures context but does not solve composer placement.
Offer keyboard insertion or selected copy fallback.
Shared storage overreach
The native surfaces retain more sensitive text than needed.
Minimize shared state and keep raw context ephemeral where possible.
Rollout gates
What must be true before rollout?
Gate 1
iPhone web demand exists
iOS users repeatedly use mobile web and ask for native context or insertion support.
Gate 2
Context handoff is proven
Share Extension behavior reliably captures the context needed for useful drafts.
Gate 3
Insertion fallback is clear
The spec defines keyboard insertion and copy fallback for unsupported composers.
Gate 4
Review copy is honest
The page does not imply current App Store availability unless verified and dated proof exists.
FAQ
Technical spec questions
Why does iOS need both keyboard and Share Extension specs?
The Share Extension is better for source context handoff, while the keyboard or copy fallback is better for placing selected text.
Should iOS native work come before mobile web?
Usually no. Mobile web should validate iPhone demand before native permission and review complexity.
Is this currently available in the App Store?
This spec is roadmap planning and should not be treated as current App Store availability.