iPhone repeat sessions
Shows that iPhone users already have repeat movel resposta fluxo worth improving.
Suggested event: iphone_mobile_reply_session_returned
KPI page
teclado iOS + extensao de compartilhamento KPIs
TypeToSell nao publica automaticamente; o usuario clica no botao final.
Última atualização: 2026-07-11. These rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set deveria prove
Gere tres rascunhos, escolha um, edite e publique manualmente.
Core metrics
Which events deveria be measured?
Share contexto success
Measures whether extensao de compartilhamento flow passes enough visible publicacao contexto para specific drafts.
Suggested event: ios_share_context_handoff_succeeded
Selected placement completion
Measures whether teclado insertion or copy fallback places chosen editable draft.
Suggested event: ios_selected_draft_placed
Storage boundary pass
Confirms raw posts, private messages, e generated replies not persisted unnecessarily.
Suggested event: ios_shared_storage_boundary_passed
Leading indicators
What deveria move antes roadmapa priority changes?
iPhone usage not assumed
iOS work deveria follow measured iPhone web movel behavior, not general movel interest.
Share e teclado roles separate
Gere tres rascunhos, escolha um, edite e publique manualmente.
Fallback ainda useful
Selected copy deveria complete fluxo quando insertion limited by iOS or target app.
aprovacao manual stays visible
Users deveria understand that TypeToSell drafts e user publishes manually.
Decision rules
How deveria these metrics guide roadmapa?
Do not build keyboard-only para contexto problems
If blocker source contexto, extensao de compartilhamento or web movel compartilhar copiar work deveria come antes keyboard-only scope.
Delay if storage unclear
If shared storage boundaries not explicit, pause native iOS scope until sensitive contexto handling reviewed.
Preserve copy fallback
Copy fallback deveria remain first-class completion path para 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 e seguranca 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 faz not confuse curiosity com real fluxo completion.
Keep final posting outside TypeToSell
Gere tres rascunhos, escolha um, edite e publique manualmente.
Related reading
Connect metrics para audits e execution
FAQ
Metrics questions
What KPI proves iOS native readiness?
Gere tres rascunhos, escolha um, edite e publique manualmente.
Why measure extensao de compartilhamento separately?
Because contexto handoff e draft placement different jobs e deveria not be collapsed into one teclado metric.
Is iOS native path ativo?
This KPI page roadmapa planning e deveria not be treated as current App Store availability.