Skip to content

Optimize Applications page data fetching #81

Description

@SagiEv

Optimize Applications page data fetching

Problem

The Applications page currently retrieves all application data at once.

This is inefficient because the list view does not require all application details.

Goal

Only retrieve the data required to render the Applications list.

When the user opens an application, fetch the complete application details.

Applications list should fetch only necessary fields

For example:

  • Application ID
  • Company
  • Role
  • Current status
  • Status date
  • Applied date
  • Other fields required by visible list components

Avoid fetching:

  • Large notes
  • Full CV data
  • Complete event history
  • Large AI-generated content
  • Other detail-only fields

unless required by the list.

Details

When navigating to an application's detail page:

  • Fetch the complete application data.
  • Use appropriate loading states.
  • Avoid blocking the entire applications list.

Acceptance Criteria

  • Applications list does not fetch unnecessary detail data.
  • Detail page fetches complete application data.
  • API/database queries are optimized.
  • Network payload is measurably reduced.
  • Pagination/infinite loading continues to work if applicable.
  • Tests cover list and detail fetching.

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

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions