82547870-a225-4398-9034-75c41500ab8b #13284
Replies: 21 comments 1 reply
|
I've seen AI Done Video once. It was pretty cool, but I'd like to see more and give it a few tries |
|
I see the benefit of getting agents to repeatedly check and fix UI issues, but I wonder if there’s a risk of this leading to over-complexity in the code itself. Could the visual feedback sometimes cause the agent to over-engineer the fix? |
|
Done videos can take a lot of time. Automating this is a great idea. Historically done videos include footage of the developer so it's clear who did the work (and how awesome SSW is). With this new approach we need to ensure done videos have a title screen that includes the developers name, so that they get attribution towards the work. This is especially important when working for a client with a mixture of client devs and consultants. |
|
I really like this AI done video! One less thing to do at the end of a prompting session 😂 🤖 This really does put a massive emphasis on a well defined backlog in my opinion. If the PBI is lacking details, AC clarity or context about common workflows in the application (Which tbh - Is most of the time), I could see the implementation and resulting demo really deviating from the initial intent. |
|
I have not used AI to generate Done Videos before, but saw that done and was pretty impressed! |
|
Sometimes... an agent will try and recreate a version of the page to take a screenshot of rather than running the whole solution. I've had to discourage that, but otherwise it's a great practice. |
|
I like the concept behind agents "seeing" their changes, and being able to iterate before it comes back to the human driver - but I'm on the fence about fully AI done videos/screenshots. Allowing AI to automate these done videos and screenshots are great for time, but at the same time, most people don't "teach" their agents how to communicate like them, or in a way that a human would really want to read, so it ends up padding content unnecessarily and being a painful process to review. |
|
I can see this saving me a lot of time when making a video for non-hardware related projects. |
|
When AI can reliably get data and use it to create pages to display in a format a user wants, ~as fast as a browser can load one, will front ends still be relevant? 🤔 |
|
I was expecting SSW.AgentSkills for this so that I could ask my AI agent with that skill to follow the same SSW standard to make done video. Now I have to find out the voice tool, and setup myself. |
|
Definitely a great use of AI in the pipeline, keen to see how AI done videos contribute to our work! |
|
Great resource for updating PBIs |
|
AI video and voice would cost a bit extra, and it may take a few attempts to get the output right. Happy to use this feature on a project once it is fully set up. |
|
If it’s just a quick and simple screenshot, I would capture it myself rather than wait for the agent to do it, but AI Done Video looks cool and I’ll try it next time. |
|
It's a nice way to capture a bunch of screenshots quickly. I still re-test the UI myself to make sure that the agent hasn't followed a path biased by the context of our conversation, e.g. making sure that the new popup is there despite exploding the rest of the page. |
|
Yes, I do this with pretty much all of my UI changes. An example is a CTA button was invisible on the teal panels. The PR carried before/after grids of both the resting and hovered states on teal, black and white, plus a capture of the four live production pages the fix would change. The next level is getting done videos for them, not sure about the AI voice though 😅 |
|
If it's made part of Playwright tests, it's probably a good 2-birds-1-stone solution. |
|
Yeah, it's often hard for other devs to reproduce my changes locally, especially UI that only shows up in rare cases, and most of them just care about the logic. So using AI to mock it up and share screenshots really helps. |
|
I'm a little bit worried about this because most of our PBI is written by Yakshaver. It's already generated. So if it has a wrong description or AC. It could go wrong for the whole AI toolchain. |
|
Great way to save time on PR approvals |
|
Where visual updates on changes matter I can see this helping alot. |
Uh oh!
There was an error while loading. Please reload this page.
82547870-a225-4398-9034-75c41500ab8b
An AI agent that verifies its UI change in a real browser should keep the screenshot or video it took. Put that evidence on the PR and the Done comment, so bugs get fixed before a human reviews and reviewers see the change without checking out the branch.
https://www.ssw.com.au/rules/done-video-by-ai
All reactions