Status
Contingent + later. Frozen spec: if device-TEFAS is impossible on the A23, a cache backend is a separate product decision. It is not a v1 task.
Do this only after (1) the browser-like TefasClient fails on the phone, and (2) we explicitly decide to add a server. Until then, isolate and swap the client only.
Why it exists as a tracked item
A cache would be more reliable than the phone hitting TEFAS (rate limits, Akamai). v1 chose no backend / no accounts to get a sideload APK first.
If we ever do it
- Same UI and
FundRepository.
- Only
TefasClient (or a new client behind it) changes.
- Still refresh followed funds, not the whole market on a timer.
- Failure still keeps last cache + follows.
- Multi-device sync is still out of v1 unless we reopen accounts (see accounts issue).
Explicitly not this
- HTML scraping of tefas.gov.tr
- Restoring
BindHistory*
- Turning the app into a chat consultant or broker
Links
Status
Contingent + later. Frozen spec: if device-TEFAS is impossible on the A23, a cache backend is a separate product decision. It is not a v1 task.
Do this only after (1) the browser-like
TefasClientfails on the phone, and (2) we explicitly decide to add a server. Until then, isolate and swap the client only.Why it exists as a tracked item
A cache would be more reliable than the phone hitting TEFAS (rate limits, Akamai). v1 chose no backend / no accounts to get a sideload APK first.
If we ever do it
FundRepository.TefasClient(or a new client behind it) changes.Explicitly not this
BindHistory*Links