search

Path-Check / safeplaces-ct-frontend

MIT License
22 stars 28 forks source link

Safe places Roadmap [draft] #11

Open mundanelunacy opened 4 years ago

mundanelunacy commented 4 years ago

https://github.com/tripleblindmarket/safe-places/issues/47

mundanelunacy commented 4 years ago

Ideas up for discussion

Technical requirements:

  • the application itself should be server independent (just html & js) cc: @penrods
  • health organizations can host the application on there own (actually, they can just download the application and use it locally) cc: @penrods
  • simple modifications should be possible using a standardized/common tecstack cc: @penrods
  • the use of APIs like Google Places API, or the Safe Path API should be optional (saving, editing, etc. should work without an API and local files)

Technical actions:

  • [ ] start using a frontend framework (react.js & redux)
  • [ ] Unifying location scrubber (reduction tool), publisher and path creator into a single PWA

Backend

  • [ ] enable downloading clustered case download (the app will send it's path boundaries to the server and only receives data for this area)
  • [ ] having a sample implementation of a API

Version 0.1-alpha

  • Create branch for react implementation @kyletowle
  • Have all the current features in place with a nice UX and a solid technical foundation

Version x.x-beta

  • Implement feature requests and ideas from health officials
  • having the API implementation
mundanelunacy commented 4 years ago

@kylemtowle

Seems a bit misplace. Should we address technical roadmap issues in Google Docs ?

https://docs.google.com/document/d/1hJNOaElk9aP9SNgnHA_eZOynAMb3Kvo_pzCwofbRHEQ/edit

iamdcj commented 4 years ago

@mundanelunacy is this ticket still relevant/useful?