iPhone repeat sessions
Shows that iPhone users already have repeat mobile risposta flusso worth improving.
Suggested event: iphone_mobile_reply_session_returned
KPI page
tastiera iOS + estensione di condivisione KPIs
TypeToSell non pubblica automaticamente; l'utente clicca il pulsante finale.
Ultimo aggiornamento: 2026-07-11. These rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set dovrebbe prove
Genera tre bozze, scegline una, modificala e pubblica manualmente.
Core metrics
Which events dovrebbe be measured?
Share contesto success
Measures whether estensione di condivisione flow passes enough visible pubblicazione contesto per specific drafts.
Suggested event: ios_share_context_handoff_succeeded
Selected placement completion
Measures whether tastiera 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 dovrebbe move prima roadmappa priority changes?
iPhone usage not assumed
iOS work dovrebbe follow measured iPhone web mobile behavior, not general mobile interest.
Share e tastiera roles separate
Genera tre bozze, scegline una, modificala e pubblica manualmente.
Fallback ancora useful
Selected copy dovrebbe complete flusso quando insertion limited by iOS or target app.
approvazione manuale stays visible
Users dovrebbe understand that TypeToSell drafts e user publishes manually.
Decision rules
How dovrebbe these metrics guide roadmappa?
Do not build keyboard-only per contesto problems
If blocker source contesto, estensione di condivisione or web mobile condividi copia work dovrebbe come prima keyboard-only scope.
Delay if storage unclear
If shared storage boundaries not explicit, pause native iOS scope until sensitive contesto handling reviewed.
Preserve copy fallback
Copy fallback dovrebbe remain first-class completion path per 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 sicurezza 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 fa not confuse curiosity con real flusso completion.
Keep final posting outside TypeToSell
Genera tre bozze, scegline una, modificala e pubblica manualmente.
FAQ
Metrics questions
What KPI proves iOS native readiness?
Genera tre bozze, scegline una, modificala e pubblica manualmente.
Why measure estensione di condivisione separately?
Because contesto handoff e draft placement different jobs e dovrebbe not be collapsed into one tastiera metric.
Is iOS native path attivo?
This KPI page roadmappa planning e dovrebbe not be treated as current App Store availability.