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.
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:
Avoid fetching:
unless required by the list.
Details
When navigating to an application's detail page:
Acceptance Criteria