Measure iPhone demand
Separate iPhone mobile web generations, selected copies, return sessions, and iOS-specific friction from total mobile data.
Pre-launch audit
iOS keyboard + Share Extension readiness audit
An iOS keyboard plus Share Extension readiness audit should prove iPhone demand and the need for two complementary surfaces. The Share Extension should help pass visible source context into TypeToSell, while the keyboard or copy fallback should place only the selected editable draft. The audit should fail if raw social content is stored unnecessarily, if App Store availability is implied without proof, or if final posting stops being manual.
Last updated: July 11, 2026. These are readiness audits, not customer outcome claims.
Audit purpose
What this audit should prove
Use this audit before publishing iOS native roadmap content or scoping implementation. It keeps source-context handoff, selected placement, shared storage, copy fallback, and manual approval boundaries visible.
Audit steps
How to run the review
Audit context handoff
Check whether Share Extension flow can capture enough visible source context for specific drafts.
Audit placement fallback
Confirm selected copy remains available when keyboard insertion or target-app behavior is limited.
Audit shared storage
Confirm raw posts, generated replies, private messages, and profile URLs are not persisted unnecessarily in shared storage.
Audit App Store status
Keep iOS keyboard and Share Extension copy in roadmap language until shipped availability is verified.
Pass criteria
What must be true before moving forward?
iPhone demand is proven
Native iOS work follows repeat iPhone mobile web usage, not general excitement about mobile.
Share and keyboard roles are separate
The Share Extension handles source context while keyboard or copy fallback handles selected draft placement.
Storage is minimized
Shared storage should avoid persistent raw social content and keep sensitive context short-lived.
Manual posting remains true
The user still edits and presses the final platform button in the destination social app.
Failure signals
What should block launch or publication?
Auto-posting implication
Any copy that suggests hands-free posting, bulk engagement, or hidden platform control should fail the audit because TypeToSell is a draft-and-approval workflow.
Unsupported availability claim
Android keyboard, iOS keyboard, Share Extension, Safari iOS extension, and Firefox Android extension pages must stay in roadmap or planning language until shipped proof exists.
Outcome proof overreach
Audit copy should be labeled as readiness review and not customer outcome claims; it should not claim revenue lift, reply-rate lift, ratings, reviews, app-store status, or platform partnership without dated public evidence.
Recommended fixes
How to repair the page or workflow
Split iOS concepts
Rewrite pages so keyboard and Share Extension roles are complementary rather than blurred together.
Add storage boundary copy
State that raw social content should not persist unnecessarily in shared state.
Preserve copy fallback
Make selected copy the reliable fallback when insertion is limited by iOS or target app behavior.
Remove App Store implication
Use roadmap or readiness language until a shipped iOS surface is verified.
Related reading
Connect audit findings to execution
iOS keyboard + Share Extension/mobile/ios-replypilot-keyboard-share-extensioniOS keyboard benchmark/benchmarks/ios-keyboard-share-extension-readiness-benchmarkiOS Share Extension constraints/platforms/ios-share-extension-platform-constraintsiOS technical spec/specs/ios-keyboard-share-extension-technical-spec
FAQ
Audit questions
Why audit iOS keyboard and Share Extension together?
Because a keyboard helps selected draft placement while a Share Extension helps source-context handoff.
What fails the iOS audit?
Weak context handoff, persistent raw social content, no copy fallback, unsupported App Store claims, or auto-posting implications should fail it.
Is the iOS native path live?
This audit is roadmap planning and should not be treated as current App Store availability.