Prompt for the PhotoApp

Please create a React-JS application for the PhotoModule. The application  has to offer the following views for the user interface: 
    1. PhotoView 
    2. PhotoRatingView 
    3. UserDeviceView 
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 PhotoView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsApproved   type: BOOL 
    - name: PhotographerName   type: STRING 
    - name: Source   type: STRING 
    - name: TakenUtc   type: DATE 
    - name: Title   type: STRING 
    - name: UploadedUtc   type: DATE 
    - name: Url   type: STRING 
    - name: UserAccount   type: UserAccount 
    - name: Vessel   type: Vessel 
The data source for the [Vessel] select control should be loaded from the relative URL: 
    "/VesselService/vessel"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Photo entity should be loaded from the relative URL: 
    "/PhotoService/photo/{id}"   (HTTP-GET) 
If a new Photo entity has been created, the new entity should be posted to the relative URL: 
    "/PhotoService/photo"   (HTTP-POST) 
If an existing Photo entity has been updated, the modified entity should be sent to the relative URL: 
    "/PhotoService/photo/{id}"   (HTTP-PUT) 
If an existing Photo entity has to be deleted, the following relative URL should be called: 
    "/PhotoService/photo/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PhotoRating columns: 
    - column: Photo 
    - column: UserAccount 
    - column: RatingValue 
    - column: RatedUtc 
The table should have the title "PhotoRatings" und the data must be loaded from the server with the following relative URL: 
    "/PhotoService/photorating/photo/{id}"

2. The PhotoRatingView must contain the following fields: 
    - name: Photo   type: Photo 
    - name: RatedUtc   type: DATE 
    - name: RatingValue   type: LONG 
    - name: UserAccount   type: UserAccount 
The data source for the [Photo] select control should be loaded from the relative URL: 
    "/PhotoService/photo"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing PhotoRating entity should be loaded from the relative URL: 
    "/PhotoService/photorating/{id}"   (HTTP-GET) 
If a new PhotoRating entity has been created, the new entity should be posted to the relative URL: 
    "/PhotoService/photorating"   (HTTP-POST) 
If an existing PhotoRating entity has been updated, the modified entity should be sent to the relative URL: 
    "/PhotoService/photorating/{id}"   (HTTP-PUT) 
If an existing PhotoRating entity has to be deleted, the following relative URL should be called: 
    "/PhotoService/photorating/{id}"   (HTTP-DELETE)

3. The UserDeviceView must contain the following fields: 
    - name: DeviceToken   type: STRING 
    - name: IsActive   type: BOOL 
    - name: LastSeenUtc   type: DATE 
    - name: Platform   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserDevice entity should be loaded from the relative URL: 
    "/PhotoService/userdevice/{id}"   (HTTP-GET) 
If a new UserDevice entity has been created, the new entity should be posted to the relative URL: 
    "/PhotoService/userdevice"   (HTTP-POST) 
If an existing UserDevice entity has been updated, the modified entity should be sent to the relative URL: 
    "/PhotoService/userdevice/{id}"   (HTTP-PUT) 
If an existing UserDevice entity has to be deleted, the following relative URL should be called: 
    "/PhotoService/userdevice/{id}"   (HTTP-DELETE)