Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Teknik spec
iOS klavyesi + Paylasim Uzantisi technical spec
TypeToSell otomatik paylasim yapmaz; son butona kullanici basar.
Son guncelleme: 2026-07-11. Bu sayfa uygulama niyetli SEO ve AI alintisi icin yazildi.
Sistem siniri
Bu spec neyi sahiplenir?
Veri akisi
Baglam ve taslaklar nasil hareket etmeli?
Share context
The user sends visible source-paylasim baglam into TypeToSell through supported iOS share flow ne zaman available.
Generate or resume drafts
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Choose insertion path
The user chooses klavye insertion or copy fallback depending on active yazma alani ve platform limits.
Manuel final action
The user reviews, edits, ve performs final sosyal platform action outside TypeToSell.
Izin modeli
Hangi erisim acik kalmali?
Paylasim Uzantisi scope
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Klavye scope
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Shared state minimization
Avoid shared local storage icin raw sosyal posts, private messages, generated replies, ve billing data.
Roadharita status clarity
Public copy gerekir say whether iOS native system planned, beta, or shipped.
Olcumleme
Ne olculmeli?
Share handoff started
Measure ne zaman iOS users try icin send source baglam into TypeToSell.
Draft selected
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Insertion or copy path
Measure whether users prefer klavye insertion, copy fallback, or mobil web return loops.
Setup abandonment
Track where users leave native iOS setup so scope can stay focused.
Hata modlari
Ne ters gidebilir ve nasil onlenmeli?
Keyboard-only blind spot
The klavye cannot reliably know source paylasim baglam.
Pair ile Paylasim Uzantisi or copy baglam fallback.
Share-only blind spot
The Paylasim Uzantisi captures baglam but gerekir not solve yazma alani placement.
Offer klavye insertion or selected copy fallback.
Shared storage overreach
The native surfaces retain more sensitive text than needed.
Minimize shared state ve keep raw baglam ephemeral where possible.
Rollout kapilari
Rollout oncesi ne dogru olmali?
Kapi 1
iPhone web demand exists
iOS users repeatedly kullan mobil web ve ask icin native baglam or insertion destek.
Kapi 2
Baglam handoff proven
Paylasim Uzantisi behavior reliably captures baglam needed icin kullanisli drafts.
Kapi 3
Insertion fallback clear
The spec defines klavye insertion ve copy fallback icin unsupported composers.
Kapi 4
Review copy honest
The page gerekir not imply current App Store availability unless verified ve dated proof exists.
Ilgili okumalar
Spec'ten uygulamaya devam et
SSS
Teknik spec sorulari
Neden gerekir iOS need both klavye ve Paylasim Uzantisi specs?
Uc taslak uret, birini sec, duzenle ve son paylasimi manuel yap.
Gerekir mi iOS native work come once mobil web?
Usually no. Mobil web gerekir validate iPhone demand once native permission ve review complexity.
Is this currently available in App Store?
This spec roadharita planning ve gerekir not be treated as current App Store availability.