Could this be utilized to improve the actual UI itself? As a somewhat naive LLM user, I have often found that when coding up projects, when you get into the area of the UI (in projects with a web-front end), the LLM immediately reaches for curl...which feels like a very inefficient way of debugging or changing a UI....
Yes for sure. We actually use the map we build of the UI + the questions people ask to automatically identify product gap patterns. These are the presented in a dashboard where you can use these insights to improve the product itself.
Comments
Could this be utilized to improve the actual UI itself? As a somewhat naive LLM user, I have often found that when coding up projects, when you get into the area of the UI (in projects with a web-front end), the LLM immediately reaches for curl...which feels like a very inefficient way of debugging or changing a UI....
Yes for sure. We actually use the map we build of the UI + the questions people ask to automatically identify product gap patterns. These are the presented in a dashboard where you can use these insights to improve the product itself.