...
| Option 1 | Option 2 | Option 3 |
|---|
Description | Replicate Open Hospital structure
(Spring + React + Material UI) | Use a different JS library
(e.g. Devias Kit, Creative Tim, Tabler, etc…) | Use existing softwares
(e.g. Grafana, Jasper, etc…) |
|---|
Pros and cons |  Same as Open Hospital, in the future the two projects could be easily merged
Homogeneity, same community can contribute to the project  The current material UI could be poor in terms of widgets and layout managers
| Leverage special features It may need specific knowledge | Some features granted by the software itself Levering high quality features In case of Jasper, it could be useful for porting the current reporting system in the “gui” It could include several unwanted features making the application heavier than needed Strong binding to an existing software can be risky |
|---|
Estimated cost | / | / | / / | / / |
|---|
✅ Action items
- To decide the final Option
- To create Jira issues with analysis' outcome Alessandro Domanico and to group them under an Epic issue
\uD83C\uDF1F Outcome
Option 2: to develop some components from scratch might be overkilling, one library (from Option 2) will be used for the POC.
Jira issue →
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | f0d90336-9135-337c-8387-a97c21b1155f |
|---|
| key | OP-934 |
|---|
|