No/low-code platforms have won the non-programmer users in the web development community. Do we really need front-end developers for the robotics community? So far yes, robotic front-end work requires special skills such as graphics programming on web (e.g., Three.js/Babylon.js, WebGL, Leaflet, etc.)

What can we do to:

  • Enable designers to directly work with backend/product engineers?
  • Free engineers from implementing design details?

This page captures the notes I made for finding answers to these questions.

Background Research

  • Where do existing no-code tools & services fall short?
    • Plasmic won’t work for creating robotics data visualization components
      • But it could probably handle user interactions outside of visual components like map, 3D world, etc.
    • Q: Is there any no/low-code tools that will work for robotics data visualization?
    • What about providing:
      • A DSL like Vega-Lite
        • No more no-code, target users would be developers who doesn’t have time
      • A library like Streamlit

Possible Experiments

  • Try to convert
    • Autoware RVIZ Plugins, e.g., to Foxglove components

Related Tools & Services