Interview folks about thoughts on rerun/canonical desktop app

Person A:

• wants visual feedback that its working when he does a command (camera, lidar, go forward, move an arm)
• after installation, wants live visualization of what it did and what its thinking and what it wants to do
  • rerun fails bc reliability
  • needs it to work on the phone
  • he cant customize in real-time colors in LIDAR in rerun
  • custom keybindings
  • turn on/off obst avoidance
  • emergency stop: one for freeze, another for collapse
  • need visual affordance for connectivity (i.e. it disconnects) and be able to reconnect
  • actions panel (wave, sit down, say a voice line)
    • record movement and repeat it (i.e. move arm, then replay it and itll do that)
  • wants to annotate map (right click and label it)
  • define a route
  • define zones and regions
  • wants modules to have blueprinteditable/blueprintconfigurable-esque functionality
  • "i want to add things to it" ex: wants to add temp gauge, motor sensor
  • GIS interropability
  • if im doing product inventory, have viewer of the inventory: basically, interroppability/transformation layer btwn external APIs and our entire internal API
  • always have feedback so you know what the robot is doing so you know its not broken Ar

Person B:

• one line install, step-by-step guide to get robot working

Synced from DIM-1555 by henry

Start by reviewing the Person A and Person B interview notes, including the Rerun reliability and mobile-app concerns. Group the requested visualization, control, mapping, interoperability, and installation capabilities into a defined direction for the canonical desktop app; done is a documented scope and decision, which the issue currently does not provide.