ReactJS developer needed to make a web site front end (to existing back end) using WebSockets -- 2
Budget: $25 – $50 USD
TelXL Limited is a telecommunications company that provides phone call routing and other services to call centres. It main user interface for administration and for call centre agents to use is outdated and in need of a refresh.
An example of this user interface is a screen (web page) where a call centre agent has areas of their display (widgets) for controlling their phone calls, another for setting their status, another for sending internal messages and so on. The attached screenshot is an example of this.
The back-end systems that send and receive information to these widgets already exists and takes the form of a WebSocket and some standardised JSON messages.
This project is to provide a web site front end framework where:
1) The front end framework establishes and maintains a WebSocket connection to our back-end servers.
2) Our JSON messages can be sent and received over this websocket.
3) One of a set of pre-configured display grid arrangements is laid out on the screen.
4) The framework will allow "widgets" to be positioned in these grid panels. Note that the design and details of individual widgets is NOT part of this project.
5) You will provide an example of at least one widget, likely one that set/shows the call centre agent's status, as a demonstration of the communication methods.
6) That demonstration widget will show how the display of the widget can be updated upon the event of receiving a message addressed to it over the websocket (e.g. information about a change in status)
7) That demonstration widget will show how clicking a button or taking some other action on the widget can result in a suitable message being sent down the websocket.
8) You will provide details (using examples of the widget(s) described above) of how our in-house web designers/developers can create further widgets.
9) The grid that these widgets sit inside must allow us to pre-configure multiple grid layouts.
10) These grid layouts must be responsive to changes in browser/screen layout, such as mobile phone screen shape and rotation, with well defined rules about which parts of the grid are shown/hidden or re-positioned as the layout is forced to change.
11) In the event of a WebSocket disconnection, or a lack of data coming over it (a "ping" should arrive every 30 seconds), the application should alert the user of a problem.
You will be asked to answer the following questions when submitting a proposal:
1. What existing technologies relating to the WebSocket communications can you make use of to reduce the need for bespoke code?
2. What existing technologies relating to the grid layout requirements would you suggest using?
3. What frameworks have you worked with?
An example of this user interface is a screen (web page) where a call centre agent has areas of their display (widgets) for controlling their phone calls, another for setting their status, another for sending internal messages and so on. The attached screenshot is an example of this.
The back-end systems that send and receive information to these widgets already exists and takes the form of a WebSocket and some standardised JSON messages.
This project is to provide a web site front end framework where:
1) The front end framework establishes and maintains a WebSocket connection to our back-end servers.
2) Our JSON messages can be sent and received over this websocket.
3) One of a set of pre-configured display grid arrangements is laid out on the screen.
4) The framework will allow "widgets" to be positioned in these grid panels. Note that the design and details of individual widgets is NOT part of this project.
5) You will provide an example of at least one widget, likely one that set/shows the call centre agent's status, as a demonstration of the communication methods.
6) That demonstration widget will show how the display of the widget can be updated upon the event of receiving a message addressed to it over the websocket (e.g. information about a change in status)
7) That demonstration widget will show how clicking a button or taking some other action on the widget can result in a suitable message being sent down the websocket.
8) You will provide details (using examples of the widget(s) described above) of how our in-house web designers/developers can create further widgets.
9) The grid that these widgets sit inside must allow us to pre-configure multiple grid layouts.
10) These grid layouts must be responsive to changes in browser/screen layout, such as mobile phone screen shape and rotation, with well defined rules about which parts of the grid are shown/hidden or re-positioned as the layout is forced to change.
11) In the event of a WebSocket disconnection, or a lack of data coming over it (a "ping" should arrive every 30 seconds), the application should alert the user of a problem.
You will be asked to answer the following questions when submitting a proposal:
1. What existing technologies relating to the WebSocket communications can you make use of to reduce the need for bespoke code?
2. What existing technologies relating to the grid layout requirements would you suggest using?
3. What frameworks have you worked with?