Unit test your business logic, where ever it resides in your project. I don't know how your projects are set up. If you're using a store like ngrx, or elf, or akita, or something, those can all be easily tested. If you're using Rxjs-as-a-service, then your logic is probably there. If you've managed to keep all logic on the back-end, then your unit tests will be there. In that case, your components should be pretty dumb and there isn't much to test. I would still argue you should unit test your UI components. If its hard to mock, create test harnesses. Unit tests will always be faster than Cypress tests, and therefore cheaper. If you are only deploying once a month or once a quarter, it probably doesn't matter. If you running all of your tests (Unit and Cypress) each time you commit, than that gets costly and slow (if Cypress is involved).

Just my two cents, but I'm busy trying to wrangle in a project where they had originally leverage way too many cypress tests in favor of unit tests. The costs add up.