It depends in which way you mean to use Play with Angular. The first option is to integrate angular stuff inside Play (like it is in the example you mentioned). According to the tutorial the route entry should be like this:
GET /*file controllers.Assets.versioned(path="/public", file: Asset)
You should also follow the rest of directions of the tutorial.
Another approach is to develop Angular as a detached project. Play in this case is just a REST server. Integration between them is reached by locating all Angular stuff into the public folder and adding a static Play route. Play is not aware about Angular at all.
It should be like following:
Put all angular files under the public folder of the Play project. Files may be organized in whatever directory structure.
Create a static index.html somewhere under the public folder. This will be an entry point for the Angular stuff.
Add the route to index.html into routes. In case index.html is directly in the public folder the route is like this:
GET / controllers.Assets.at(path="/public", file ="index.html")
Add routing to the Angular files into the routes:
GET /*file controllers.Assets.at(path="/public", file)
You can see some more details here.