On top of what Jose Valim said:

I ran this yesterday. Since it's running inside your app and has access to everything your app does, here's what it did for me:

I have an app that processes images and displays certain info on them. The images are processed asynchronously.

I needed a pubsub when info was inserted into the DB to be sent out, and info on the page to appear immediately.

Since Tidewave is running inside the app, it did the following:

- opened the info page

- triggered dummy data insert into the DB

Edit: I mean it inserted data using the exposed module functions that would trigger the pubsub [1], it did not add data to DB directly

- monitored both the app logs and the page to see what's happening

- made several iterations adding pubsub, subscribing to it, and fixing page display

I didn't need to make screenshots because Tidewave was looking at the page already.

I didn't need to paste screenshots anywhere and rely on that model's OCR to figure out what's going on.

I didn't have to copy-paste logs.

and so on

[1] https://hexdocs.pm/ash/Ash.Notifier.PubSub.html