Effort Estimations for an AngularJS Web Client

I am a backend developer with limited web front-end experience and I need to create some cost estimates for a reasonably simple web browser client, for a desktop and mobile device.

Effort for designing the server-ware and the middle-ware I can estimate, however the web front-end is not in my field of expertise.

I have the following non functional client requirements :

1. has to be functional without a web server
2. session managed via LDAP
3. development with Angular 2
4. backend will be sprint based (SpringSecurity, Swagger, Spring Interface DAOs, Spring Rest Template)

I need to meet the following functional requirements:

• As a user I need to be able to login and logout. The client application needs to have a concept of rights, as the edit operations detailed later are not allowed for all users.
• As a user I need to be able to select a sector for the client application (a dialog with drag and drop for example), so that I can provide bespoke content for a table.
• As a user I need to be able to show a table with circa 10 columns, some with images. The table is readonly and receives sporadic server updates. When I click on a row from the table, the table will expand to show three sliders. The three sliders are the only edit operations in the client.
• As a user I can filter the table with a free text field, so that I can find table entries easier.
• As a user I will need to search for entries from the backend archives. To do so a dialog will allow me to enter search parameters.

Assumptions

• Experienced development team of 3 developers and and a scrum master
• Pragmatic UI without any major bells and whistles
• Search happens on server
• Filtering of the table content happens in the front end

Given these very general requirements and assumptions, I have the following questions.

What other technologies might I need in the front end other than angular?

What sort of ball park figure for effort would be required to design and implement just the front end (including unit tests)? Are we talking 200 days of design, development and test, or 50?