Prompt for the ProfileApp

Please create a React-JS application for the ProfileModule. The application  has to offer the following views for the user interface: 
    1. ProfileView 
    2. WatchHistoryView 
    3. WatchlistItemView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The ProfileView must contain the following fields: 
    - name: AvatarUrl   type: STRING 
    - name: CreatedAt   type: STRING 
    - name: IsKidsProfile   type: BOOL 
    - name: Name   type: STRING 
    - name: User   type: User 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing Profile entity should be loaded from the relative URL: 
    "/ProfileService/profile/{id}"   (HTTP-GET) 
If a new Profile entity has been created, the new entity should be posted to the relative URL: 
    "/ProfileService/profile"   (HTTP-POST) 
If an existing Profile entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProfileService/profile/{id}"   (HTTP-PUT) 
If an existing Profile entity has to be deleted, the following relative URL should be called: 
    "/ProfileService/profile/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserRating columns: 
    - column: RatedAt 
    - column: Profile 
    - column: RatingValue 
    - column: Title 
The table should have the title "UserRatings" und the data must be loaded from the server with the following relative URL: 
    "/VideoFormatService/userrating/profile/{id}" 
Add a HTML table to the view with the following WatchHistory columns: 
    - column: Episode 
    - column: Profile 
    - column: StartedAt 
    - column: ProgressPercent 
    - column: Season 
    - column: CompletedAt 
    - column: Title 
    - column: LastPositionSeconds 
The table should have the title "WatchHistorys" und the data must be loaded from the server with the following relative URL: 
    "/ProfileService/watchhistory/profile/{id}" 
Add a HTML table to the view with the following PlaybackSession columns: 
    - column: IsLive 
    - column: Season 
    - column: Title 
    - column: Profile 
    - column: Episode 
    - column: EndedAt 
    - column: PlaybackType 
    - column: Device 
    - column: StartedAt 
The table should have the title "PlaybackSessions" und the data must be loaded from the server with the following relative URL: 
    "/EpisodeService/playbacksession/profile/{id}" 
Add a HTML table to the view with the following WatchlistItem columns: 
    - column: Profile 
    - column: AddedAt 
    - column: Title 
The table should have the title "WatchlistItems" und the data must be loaded from the server with the following relative URL: 
    "/ProfileService/watchlistitem/profile/{id}" 
Add a HTML table to the view with the following DownloadLicense columns: 
    - column: Episode 
    - column: Profile 
    - column: Season 
    - column: DeviceLimit 
    - column: GrantedAt 
    - column: IsExpired 
    - column: ExpiresAt 
    - column: Title 
The table should have the title "DownloadLicenses" und the data must be loaded from the server with the following relative URL: 
    "/SeasonService/downloadlicense/profile/{id}"

2. The WatchHistoryView must contain the following fields: 
    - name: CompletedAt   type: STRING 
    - name: Episode   type: Episode 
    - name: LastPositionSeconds   type: LONG 
    - name: Profile   type: Profile 
    - name: ProgressPercent   type: STRING 
    - name: Season   type: Season 
    - name: StartedAt   type: STRING 
    - name: Title   type: Title 
The data source for the [Episode] select control should be loaded from the relative URL: 
    "/EpisodeService/episode"   (HTTP-GET) 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (HTTP-GET) 
The data source for the [Season] select control should be loaded from the relative URL: 
    "/SeasonService/season"   (HTTP-GET) 
The data source for the [Profile] select control should be loaded from the relative URL: 
    "/ProfileService/profile"   (HTTP-GET) 
An existing WatchHistory entity should be loaded from the relative URL: 
    "/ProfileService/watchhistory/{id}"   (HTTP-GET) 
If a new WatchHistory entity has been created, the new entity should be posted to the relative URL: 
    "/ProfileService/watchhistory"   (HTTP-POST) 
If an existing WatchHistory entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProfileService/watchhistory/{id}"   (HTTP-PUT) 
If an existing WatchHistory entity has to be deleted, the following relative URL should be called: 
    "/ProfileService/watchhistory/{id}"   (HTTP-DELETE)

3. The WatchlistItemView must contain the following fields: 
    - name: AddedAt   type: STRING 
    - name: Profile   type: Profile 
    - name: Title   type: Title 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (HTTP-GET) 
The data source for the [Profile] select control should be loaded from the relative URL: 
    "/ProfileService/profile"   (HTTP-GET) 
An existing WatchlistItem entity should be loaded from the relative URL: 
    "/ProfileService/watchlistitem/{id}"   (HTTP-GET) 
If a new WatchlistItem entity has been created, the new entity should be posted to the relative URL: 
    "/ProfileService/watchlistitem"   (HTTP-POST) 
If an existing WatchlistItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProfileService/watchlistitem/{id}"   (HTTP-PUT) 
If an existing WatchlistItem entity has to be deleted, the following relative URL should be called: 
    "/ProfileService/watchlistitem/{id}"   (HTTP-DELETE)