Prompt for the EpisodeApp

Please create a React-JS application for the EpisodeModule. The application  has to offer the following views for the user interface: 
    1. DeviceView 
    2. EpisodeView 
    3. PlaybackSessionView 
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 DeviceView must contain the following fields: 
    - name: AppVersion   type: STRING 
    - name: DeviceType   type: STRING 
    - name: LastActiveAt   type: STRING 
    - name: Manufacturer   type: STRING 
    - name: Model   type: STRING 
    - name: OsName   type: STRING 
    - name: OsVersion   type: STRING 
    - name: RegisteredAt   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 Device entity should be loaded from the relative URL: 
    "/EpisodeService/device/{id}"   (HTTP-GET) 
If a new Device entity has been created, the new entity should be posted to the relative URL: 
    "/EpisodeService/device"   (HTTP-POST) 
If an existing Device entity has been updated, the modified entity should be sent to the relative URL: 
    "/EpisodeService/device/{id}"   (HTTP-PUT) 
If an existing Device entity has to be deleted, the following relative URL should be called: 
    "/EpisodeService/device/{id}"   (HTTP-DELETE) 
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/device/{id}"

2. The EpisodeView must contain the following fields: 
    - name: EpisodeNumber   type: LONG 
    - name: Name   type: STRING 
    - name: ReleaseDate   type: DATE 
    - name: RuntimeMinutes   type: LONG 
    - name: Season   type: Season 
    - name: Synopsis   type: STRING 
    - 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 [Season] select control should be loaded from the relative URL: 
    "/SeasonService/season"   (HTTP-GET) 
An existing Episode entity should be loaded from the relative URL: 
    "/EpisodeService/episode/{id}"   (HTTP-GET) 
If a new Episode entity has been created, the new entity should be posted to the relative URL: 
    "/EpisodeService/episode"   (HTTP-POST) 
If an existing Episode entity has been updated, the modified entity should be sent to the relative URL: 
    "/EpisodeService/episode/{id}"   (HTTP-PUT) 
If an existing Episode entity has to be deleted, the following relative URL should be called: 
    "/EpisodeService/episode/{id}"   (HTTP-DELETE) 
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/episode/{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/episode/{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/episode/{id}"

3. The PlaybackSessionView must contain the following fields: 
    - name: Device   type: Device 
    - name: EndedAt   type: STRING 
    - name: Episode   type: Episode 
    - name: IsLive   type: BOOL 
    - name: PlaybackType   type: STRING 
    - name: Profile   type: Profile 
    - 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 [Device] select control should be loaded from the relative URL: 
    "/EpisodeService/device"   (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 PlaybackSession entity should be loaded from the relative URL: 
    "/EpisodeService/playbacksession/{id}"   (HTTP-GET) 
If a new PlaybackSession entity has been created, the new entity should be posted to the relative URL: 
    "/EpisodeService/playbacksession"   (HTTP-POST) 
If an existing PlaybackSession entity has been updated, the modified entity should be sent to the relative URL: 
    "/EpisodeService/playbacksession/{id}"   (HTTP-PUT) 
If an existing PlaybackSession entity has to be deleted, the following relative URL should be called: 
    "/EpisodeService/playbacksession/{id}"   (HTTP-DELETE)