Skip to content

Contingent later: tiny TEFAS cache backend if the device cannot reach TEFAS #30

Description

@beagle1903

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contingentOnly if TEFAS/device conditions faillaterAfter the A23 APK has been used (Play and contingencies)

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions