I think the biggest issue I have with this, are the in-between devices, like smaller screen laptops and tablets. People still use these things and this type of split makes no sense for them as you will likely have a combination of both for these tween devices.
Also, the bulk of your overhead is more likely your library packages, and even the component libraries themselves, not your application component modules. While you *can* break these down, I don't know that it's worth the consideration in many/most cases.
You can wrap most of your components in async load and your bundler can break these out... you will lose some benefits, but http2+ can offset some of the disadvantages in practice.
tracker1 1105 days ago. link 1 point ▲ ▼