iPhone repeat sessions
Shows that iPhone users already have repeat movil respuesta flujo worth improving.
Suggested event: iphone_mobile_reply_session_returned
KPI page
teclado iOS + complemento de compartir KPIs
TypeToSell no publica automaticamente; el usuario pulsa el boton final.
Última actualización: 2026-07-11. These rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set deberia prove
Genera tres borradores, elige uno, editalo y publica manualmente.
Core metrics
Which events deberia be measured?
Share contexto success
Measures whether complemento de compartir flow passes enough visible publicacion 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, y generated replies not persisted unnecessarily.
Suggested event: ios_shared_storage_boundary_passed
Leading indicators
What deberia move antes roadmapa priority changes?
iPhone usage not assumed
iOS work deberia follow measured iPhone web movil behavior, not general movil interest.
Share y teclado roles separate
Genera tres borradores, elige uno, editalo y publica manualmente.
Fallback todavia useful
Selected copy deberia complete flujo cuando insertion limited by iOS or target app.
aprobacion manual stays visible
Users deberia understand that TypeToSell drafts y user publishes manually.
Decision rules
How deberia these metrics guide roadmapa?
Do not build keyboard-only para contexto problems
If blocker source contexto, complemento de compartir or web movil compartir copiar work deberia 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 deberia 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 y seguridad 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 hace not confuse curiosity con real flujo completion.
Keep final posting outside TypeToSell
Genera tres borradores, elige uno, editalo y publica manualmente.
FAQ
Metrics questions
What KPI proves iOS native readiness?
Genera tres borradores, elige uno, editalo y publica manualmente.
Por qué measure complemento de compartir separately?
Because contexto handoff y draft placement different jobs y deberia not be collapsed into one teclado metric.
Is iOS native path activo?
This KPI page roadmapa planning y deberia not be treated as current App Store availability.