Skip to content

Implement client side caching for Bodies #75

@Jyotirya

Description

@Jyotirya

Currently the app makes a fresh API call every time a Club or Body profile is opened, even if the data hasn't changed. Since Club and Body profile data (description, logo, members, social links) changes very infrequently, this is unnecessary network usage. The profile should load instantly from cache and silently refresh in the background

Affected screens:

  • Body profiles
  • Explore section - the list of bodies under Tech, Cult, Sports etc should also load from cache

Expected behavior:

  • On opening a Club/Body profile, cached data is shown immediately
  • A background API call is made silently to fetch latest data in both cases
  • If new data is available, the UI updates in place (stale-while-revalidate pattern)
  • Pull to refresh always bypasses cache and fetches fresh data

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions