iPhone repeat sessions
Shows that iPhone users already have repeat mobile reponse flux worth improving.
Suggested event: iphone_mobile_reply_session_returned
KPI page
clavier iOS + module de partage KPIs
TypeToSell ne publie pas automatiquement; l'utilisateur clique sur le bouton final.
Dernière mise à jour : 2026-07-11. These rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set devrait prove
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Core metrics
Which events devrait be measured?
Share contexte success
Measures whether module de partage flow passes enough visible publication contexte pour specific drafts.
Suggested event: ios_share_context_handoff_succeeded
Selected placement completion
Measures whether clavier insertion or copy fallback places chosen editable draft.
Suggested event: ios_selected_draft_placed
Storage boundary pass
Confirms raw posts, private messages, et generated replies not persisted unnecessarily.
Suggested event: ios_shared_storage_boundary_passed
Leading indicators
What devrait move avant roadcarte priority changes?
iPhone usage not assumed
iOS work devrait follow measured iPhone web mobile behavior, not general mobile interest.
Share et clavier roles separate
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Fallback encore useful
Selected copy devrait complete flux quand insertion limited by iOS or target app.
approbation manuelle stays visible
Users devrait understand that TypeToSell drafts et user publishes manually.
Decision rules
How devrait these metrics guide roadcarte?
Do not build keyboard-only pour contexte problems
If blocker source contexte, module de partage or web mobile partager copier work devrait come avant keyboard-only scope.
Delay if storage unclear
If shared storage boundaries not explicit, pause native iOS scope until sensitive contexte handling reviewed.
Preserve copy fallback
Copy fallback devrait remain first-class completion path pour constrained iOS app behavior.
Keep App Store status honest
Do not imply current App Store availability until shipped native surface verified.
Instrumentation guardrails
Keep metrics honest
Keep metrics as product signals
Label metrics as TypeToSell rollout et securite 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 team fait not confuse curiosity avec real flux completion.
Keep final posting outside TypeToSell
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Related reading
Connect metrics vers audits et execution
FAQ
Metrics questions
What KPI proves iOS native readiness?
Generez trois brouillons, choisissez-en un, modifiez-le puis publiez manuellement.
Why measure module de partage separately?
Because contexte handoff et draft placement different jobs et devrait not be collapsed into one clavier metric.
Is iOS native path actif?
This KPI page roadcarte planning et devrait not be treated as current App Store availability.