But if you get the framing from the terrible prototype/draft, it can lead you into a bad direction. It is like the "Don't think of an Elephant". Once you see the "Elephant" you will struggle not to make something that looks more like an Elephant.

[–] NikkiDimes@lemmy.world 3 points 4 hours ago* (last edited 4 hours ago)

True, but I see it more as a tool for a non-technical person to make a prototype of a user experience more than making a foundation for how a project will actually be built and designed from a code perspective. Like, when it comes to the actual implementation of said project, the developer(s) shouldn't even look at the prototype code. I envision, in this example, as it solely being a tool for non-technical people to express their ideas to the technical side of the operation.

I agree with you though, that still has potential to pollute a project entirely, and we already have methods of creating requirements and documentation for projects so this isn't exactly the most useful thing ever.