chapter: User Interfaces

[codebot]

This chapter will talk about how to create custom UI's for system operators and users (not developers).

• Assumption: it will be a web UI because it will probably need to be installed on many different machines and many OS'es (desktop/mobile, etc.). Making native apps for everybody is a lot harder.
• Assumption: probably multiple UI's are required for each installation, for different types of operators and users.
• Tasks for each custom UI
  • user authentication
  • get data feeds somehow in and out (uilib and friends)
  • viewing data spatially (robots driving around on maps)
  • dispatching tasks and monitoring state on minimal UI's without maps, just task-request buttons and status lights/text, etc.

[koonpeng]

user authentication

theres no authentication system in RoMi (yet). There are plans for a oauth2 based system, but that is independent from RoMi. That could also be large and complicated enough to be its own chapter.

[mdfesto]

That could also be large and complicated enough to be its own chapter.

use your discretion and feel free to create a new chapter if you feel it's better structured that way. Also this is meant to be a "living document" so if you want to introduce the plans but not go into detail yet, you could put a teaser in there that a chapter will be added soon...