On app boot, we currently initiate eager load of tx history. Depending on existing cache this can be:
In the worst case: Full tx history paging for all accounts on all chains
In the best case: Single tx history page for all accounts on all chains to update state
The main driver of the need for eager tx history loading is the balance history which requires full tx history to be known for the time period being displayed on the balance history chart. If we negate this requirement, we should be able to request a single page of tx history for the specific account(s) a user is viewing, lazily.
References and additional details
This should be don incrementally in case our requirements change:
Hide the balance history chart from the "My Wallet" page to measure users reaction
Remove all code relating to balance history chart
Remove balance history fetch on boot, make specific parts of the app page on-demand (with caching in redux store)
Implement replacement chart/feature not requiring large numbers of requests on boot @twblack88
Overview
On app boot, we currently initiate eager load of tx history. Depending on existing cache this can be:
The main driver of the need for eager tx history loading is the balance history which requires full tx history to be known for the time period being displayed on the balance history chart. If we negate this requirement, we should be able to request a single page of tx history for the specific account(s) a user is viewing, lazily.
References and additional details
This should be don incrementally in case our requirements change:
Acceptance Criteria
App doesn't eagerly load balance history on boot
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response