iPhone repeat sessions
Shows that iPhone users already have repeat mobilny odpowiedz przeplyw worth improving.
Suggested event: iphone_mobile_reply_session_returned
KPI page
klawiatura iOS + rozszerzenie udostepniania KPIs
TypeToSell nie publikuje automatycznie; ostatni przycisk klika uzytkownik.
Ostatnia aktualizacja: 2026-07-11. These rollout metrics, not customer outcome claims.
Measurement purpose
What this metric set powinien prove
Wygeneruj trzy szkice, wybierz jeden, edytuj i opublikuj recznie.
Core metrics
Which events powinien be measured?
Share kontekst success
Measures whether rozszerzenie udostepniania flow passes enough visible publikacja kontekst dla specific drafts.
Suggested event: ios_share_context_handoff_succeeded
Selected placement completion
Measures whether klawiatura insertion or copy fallback places chosen editable draft.
Suggested event: ios_selected_draft_placed
Storage boundary pass
Confirms raw posts, private messages, i generated replies not persisted unnecessarily.
Suggested event: ios_shared_storage_boundary_passed
Leading indicators
What powinien move przed roadmapa priority changes?
iPhone usage not assumed
iOS work powinien follow measured iPhone mobilny web behavior, not general mobilny interest.
Share i klawiatura roles separate
Wygeneruj trzy szkice, wybierz jeden, edytuj i opublikuj recznie.
Fallback nadal useful
Selected copy powinien complete przeplyw kiedy insertion limited by iOS or target app.
reczna akceptacja stays visible
Users powinien understand that TypeToSell drafts i user publishes manually.
Decision rules
How powinien these metrics guide roadmapa?
Do not build keyboard-only dla kontekst problems
If blocker source kontekst, rozszerzenie udostepniania or mobilny web udostepnij kopiuj work powinien come przed keyboard-only scope.
Delay if storage unclear
If shared storage boundaries not explicit, pause native iOS scope until sensitive kontekst handling reviewed.
Preserve copy fallback
Copy fallback powinien remain first-class completion path dla 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 i bezpieczenstwo 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 robi not confuse curiosity z real przeplyw completion.
Keep final posting outside TypeToSell
Wygeneruj trzy szkice, wybierz jeden, edytuj i opublikuj recznie.
FAQ
Metrics questions
What KPI proves iOS native readiness?
Wygeneruj trzy szkice, wybierz jeden, edytuj i opublikuj recznie.
Why measure rozszerzenie udostepniania separately?
Because kontekst handoff i draft placement different jobs i powinien not be collapsed into one klawiatura metric.
Is iOS native path aktywny?
This KPI page roadmapa planning i powinien not be treated as current App Store availability.