Prompt for the UserDeviceApp

Please create a React-JS application for the UserDeviceModule. The application  has to offer the following views for the user interface: 
    1. AccountBalanceView 
    2. ChargebackView 
    3. UserDeviceView 
    4. UserLoginSessionView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The AccountBalanceView must contain the following fields: 
    - name: AvailableAmount   type: DOUBLE 
    - name: Currency   type: Currency 
    - name: LastUpdatedAt   type: DATE 
    - name: PendingAmount   type: DOUBLE 
    - name: UserAccount   type: UserAccount 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing AccountBalance entity should be loaded from the relative URL: 
    "/UserDeviceService/accountbalance/{id}"   (HTTP-GET) 
If a new AccountBalance entity has been created, the new entity should be posted to the relative URL: 
    "/UserDeviceService/accountbalance"   (HTTP-POST) 
If an existing AccountBalance entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDeviceService/accountbalance/{id}"   (HTTP-PUT) 
If an existing AccountBalance entity has to be deleted, the following relative URL should be called: 
    "/UserDeviceService/accountbalance/{id}"   (HTTP-DELETE)

2. The ChargebackView must contain the following fields: 
    - name: Amount   type: DOUBLE 
    - name: ClosedAt   type: DATE 
    - name: Currency   type: Currency 
    - name: OpenedAt   type: DATE 
    - name: ReasonCode   type: STRING 
    - name: Status   type: STRING 
    - name: Transaction   type: Transaction 
    - name: UserAccount   type: UserAccount 
The data source for the [Transaction] select control should be loaded from the relative URL: 
    "/TransactionService/transaction"   (HTTP-GET) 
The data source for the [Currency] select control should be loaded from the relative URL: 
    "/CurrencyService/currency"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Chargeback entity should be loaded from the relative URL: 
    "/UserDeviceService/chargeback/{id}"   (HTTP-GET) 
If a new Chargeback entity has been created, the new entity should be posted to the relative URL: 
    "/UserDeviceService/chargeback"   (HTTP-POST) 
If an existing Chargeback entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDeviceService/chargeback/{id}"   (HTTP-PUT) 
If an existing Chargeback entity has to be deleted, the following relative URL should be called: 
    "/UserDeviceService/chargeback/{id}"   (HTTP-DELETE)

3. The UserDeviceView must contain the following fields: 
    - name: DeviceFingerprint   type: STRING 
    - name: DeviceType   type: STRING 
    - name: LastSeenAt   type: DATE 
    - name: OperatingSystem   type: STRING 
    - name: Trusted   type: BOOL 
    - 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: 
    "/UserDeviceService/userdevice/{id}"   (HTTP-GET) 
If a new UserDevice entity has been created, the new entity should be posted to the relative URL: 
    "/UserDeviceService/userdevice"   (HTTP-POST) 
If an existing UserDevice entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDeviceService/userdevice/{id}"   (HTTP-PUT) 
If an existing UserDevice entity has to be deleted, the following relative URL should be called: 
    "/UserDeviceService/userdevice/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserLoginSession columns: 
    - column: ExpiresAt 
    - column: SessionToken 
    - column: CreatedAt 
    - column: UserAgent 
    - column: UserDevice 
    - column: Status 
    - column: UserAccount 
    - column: IpAddress 
The table should have the title "UserLoginSessions" und the data must be loaded from the server with the following relative URL: 
    "/UserDeviceService/userloginsession/userdevice/{id}"

4. The UserLoginSessionView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: ExpiresAt   type: DATE 
    - name: IpAddress   type: STRING 
    - name: SessionToken   type: STRING 
    - name: Status   type: STRING 
    - name: UserAccount   type: UserAccount 
    - name: UserAgent   type: STRING 
    - name: UserDevice   type: UserDevice 
The data source for the [UserDevice] select control should be loaded from the relative URL: 
    "/UserDeviceService/userdevice"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserLoginSession entity should be loaded from the relative URL: 
    "/UserDeviceService/userloginsession/{id}"   (HTTP-GET) 
If a new UserLoginSession entity has been created, the new entity should be posted to the relative URL: 
    "/UserDeviceService/userloginsession"   (HTTP-POST) 
If an existing UserLoginSession entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDeviceService/userloginsession/{id}"   (HTTP-PUT) 
If an existing UserLoginSession entity has to be deleted, the following relative URL should be called: 
    "/UserDeviceService/userloginsession/{id}"   (HTTP-DELETE)