It totally depends on the choice of the team and the ease of the implementation for the QA team. There is a no hard and fast rule that you should USE Protractor when the UI is built with Angular or Angular JS.

The real BENEFIT for using Protractor NARROW down to the two major points that I think should be taken into consideration while deciding whether or not to use Protractor

Protractor handles the $http or $TIMEOUT synchronization issues arising out of Angular/Angular JS very well.

Since Angular/Angular JS code is written in JavaScript/TypeScript, and Protractor SUPPORTS both these languages, so there is sync between the devs and QA when using a single operating language for FE as well as the test framework.

It totally depends on the choice of the team and the ease of the implementation for the QA team. There is a no hard and fast rule that you should use Protractor when the UI is built with Angular or Angular JS.

The real benefit for using Protractor narrow down to the two major points that I think should be taken into consideration while deciding whether or not to use Protractor

Protractor handles the $http or $timeout synchronization issues arising out of Angular/Angular JS very well.

Since Angular/Angular JS code is written in JavaScript/TypeScript, and Protractor supports both these languages, so there is sync between the devs and QA when using a single operating language for FE as well as the test framework.