Coming from https://expensify.slack.com/archives/C05LX9D6E07/p1694767889647489
### Problem:
Because of the way we chose to do navigation, every time we navigate to a new report, we're adding a new component to the navigation stack. That is bad because, overtime, we'll have so many components in the navigation stack that it will consume too much memory and make the app slow. This is a problem mainly for desktop since we don't really click on back and the app doesn't restart frequently, but can affect web too.
### Solution:
Still to be explored, but we need to keep the same navigation patterns and ideally limit the number of memory the screens even frozen would take
Issue Owner
Current Issue Owner: @johncschusterUpwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01fb0ef201d2d160a5
- Upwork Job ID: 1729882695643987968
- Last Price Increase: 2023-11-29
Coming from https://expensify.slack.com/archives/C05LX9D6E07/p1694767889647489
### Problem:
Because of the way we chose to do navigation, every time we navigate to a new report, we're adding a new component to the navigation stack. That is bad because, overtime, we'll have so many components in the navigation stack that it will consume too much memory and make the app slow. This is a problem mainly for desktop since we don't really click on back and the app doesn't restart frequently, but can affect web too.
### Solution:
Still to be explored, but we need to keep the same navigation patterns and ideally limit the number of memory the screens even frozen would take
Issue Owner
Current Issue Owner: @johncschusterUpwork Automation - Do Not Edit