KPI page

iOS keyboard + Share Extension KPIs

iOS keyboard plus Share Extension KPIs should prove both iPhone demand and the need for paired surfaces. The Share Extension KPI should measure source-context handoff success, while the keyboard or copy fallback KPI should measure selected editable draft placement. The strongest KPIs also include iPhone repeat sessions, context failure rate, copy fallback completion, storage-boundary checks, and manual final posting clarity.

Last updated: July 11, 2026. These are rollout metrics, not customer outcome claims.

Measurement purpose

What this metric set should prove

Use these KPIs before scoping iOS native work. iOS readiness needs two kinds of evidence: users need a way to pass visible source context into TypeToSell and a way to place the chosen draft back into the destination app.

Core metrics

Which events should be measured?

iPhone repeat sessions

Shows that iPhone users already have a repeat mobile reply workflow worth improving.

Suggested event: iphone_mobile_reply_session_returned

Share context success

Measures whether the Share Extension flow passes enough visible post context for specific drafts.

Suggested event: ios_share_context_handoff_succeeded

Selected placement completion

Measures whether keyboard insertion or copy fallback places the chosen editable draft.

Suggested event: ios_selected_draft_placed

Storage boundary pass

Confirms raw posts, private messages, and generated replies are not persisted unnecessarily.

Suggested event: ios_shared_storage_boundary_passed

Leading indicators

What should move before roadmap priority changes?

iPhone usage is not assumed

iOS work should follow measured iPhone mobile web behavior, not general mobile interest.

Share and keyboard roles are separate

The Share Extension handles context while keyboard or copy fallback handles selected draft placement.

Fallback is still useful

Selected copy should complete the workflow when insertion is limited by iOS or the target app.

Manual approval stays visible

Users should understand that TypeToSell drafts and the user publishes manually.

Decision rules

How should these metrics guide the roadmap?

Do not build keyboard-only for context problems

If the blocker is source context, Share Extension or share/copy work should come before keyboard-only scope.

Delay if storage is unclear

If shared storage boundaries are not explicit, pause native iOS scope until sensitive context handling is reviewed.

Preserve copy fallback

Copy fallback should remain a first-class completion path for constrained iOS app behavior.

Keep App Store status honest

Do not imply current App Store availability until a shipped native surface is verified.

Instrumentation guardrails

Keep metrics honest

Keep metrics as product signals

Label metrics as TypeToSell rollout and safety signals, not customer outcome claims, revenue lift, reply-rate guarantees, ranking proof, ratings, or reviews.

Separate generated from selected

Track generation starts separately from selected copy or insertion so the team does not confuse curiosity with real workflow completion.

Keep final posting outside TypeToSell

Measure draft handoff and copied or inserted text, but do not instrument TypeToSell as the system that presses the final public platform button.

Related reading

Connect metrics to audits and execution

iOS readiness audit/audits/ios-keyboard-share-extension-readiness-auditiOS readiness benchmark/benchmarks/ios-keyboard-share-extension-readiness-benchmarkiOS keyboard + Share Extension workflow/workflows/ios-keyboard-share-extension-workflowiOS keyboard + Share Extension technical spec/specs/ios-keyboard-share-extension-technical-spec

FAQ

Metrics questions

What KPI proves iOS native readiness?

iPhone repeat sessions plus successful context handoff and selected draft placement are the strongest iOS readiness signals.

Why measure Share Extension separately?

Because context handoff and draft placement are different jobs and should not be collapsed into one keyboard metric.

Is the iOS native path live?

This KPI page is roadmap planning and should not be treated as current App Store availability.