Motivation:
Imagine big company using our product.
HR people use Collaborators page.
Project managers use Projects page.
Their submanagers could use Works page.
And individual workers can mark their changes in Changes page.
Changes page for HR is useless, so don't load it, only if their explicitly request.
Works page is useless for project managers, they have submanagers for this purpose, and so on...
Make each route small bundle of our app that can be loaded lazily.
Route based code-splitting was implemented as illustrated in docs: https://reactjs.org/docs/code-splitting.html#route-based-code-splitting
Motivation: Imagine big company using our product. HR people use Collaborators page. Project managers use Projects page. Their submanagers could use Works page. And individual workers can mark their changes in Changes page.
Changes page for HR is useless, so don't load it, only if their explicitly request. Works page is useless for project managers, they have submanagers for this purpose, and so on...