16 lines
1.1 KiB
Markdown
16 lines
1.1 KiB
Markdown
# Open questions
|
||
|
||
1. **SSO redirect URIs** — which App Auth / Custom Tabs redirect URIs to register with Google / Microsoft + `chat_backend`?
|
||
2. **Document storage on mobile** — still required for Play v1, or web-only?
|
||
3. **Markdown strategy** — native Markwon/Coil vs small WebView islands for charts?
|
||
4. **Analytics** — Tianji parity, Firebase, or none for native v1?
|
||
5. **Push notifications** — defer confirmed?
|
||
6. **Encrypted session storage** — DataStore OK for MVP, or EncryptedSharedPreferences required at launch?
|
||
7. **Capacitor freeze date** — who owns Play Console cutover once native internal test passes?
|
||
8. **JWT login field** — confirm backend `token/` expects `email` vs `username` (wire against live OpenAPI).
|
||
9. **Cost estimate** — eng weeks for auth → chat → IAP after scaffolding (update epic AC #1).
|
||
|
||
## Spike verdict (initial)
|
||
|
||
**Proceed** with native Compose client. Capacitor remains interim Play track until native IAP path is proven (ADR-002). Rough order-of-magnitude after scaffold: **6–10 eng weeks** for auth + chat MVP + RevenueCat + store checklist (SSO + polish extra).
|