that moving background is terrible, i can't read it properly
document.querySelectorAll('div').forEach(x => x.classList.remove('jumbo'));
The Speed of Prototyping in the Age of AI
101–110 of 119 posts
Re: The Speed of Prototyping in the Age of AI
#102What are people doing with prototypes afterward? Do you end up shipping it as is to production? What about at work? Are the prototypes useful in that context?
In my day job, we commonly create prototypes to sell the idea/concept to the higher ups, then if we get the green light, we throw the prototype in the bin and start from scratch to build it out properly.
I find this is where AI is genuinely useful, it lets us prototype an idea a lot faster, make no bones about the fact that it is a buggy proof of concept but lets people see the potential and get an idea for what the final product might look like.
Re: The Speed of Prototyping in the Age of AI
#103The page shows up however briefly and then there's a full screen error message saying "This page couldn’t load"
In the browser javascript console I see "Uncaught TypeError: can't access property "ordinal", r is undefined"
Re: The Speed of Prototyping in the Age of AI
#104I think it is mostly accurate to say that the cost of execution has dropped to zero. In this new world, the ability to say "no" is more important than ever. It has never been so easy to burn time, money and energy. The fact that you can try anything now can be modeled as a disadvantage. The space of possible solutions got a lot bigger. Unless you have good taste you could wander and get lost very quickly in this vast…
Very well said. The relative importance of prioritisation has shot up massively (and it was already essential before).
Re: The Speed of Prototyping in the Age of AI
#105Earlier quoted context omitted.
The same thing happened when figma made it easier make prototypes that looked real and people stopped doing low fidelity mockups. Everyone understands that a wireframe isn’t done yet and it’s easy to change at that phase.
This I believe is lowkey one of the core ways design broke at tech companies. There are other big ones, design (really product) is broke deeply, but once mockups became easy we stopped having discussions about information architecture and UX. We're talking about whether we think this looks nicer in blue or green. Happened before Figma, but Figma really grew it. The designers that tried to hold onto wireframes (or wen…
It’s a bit like having a 1:1 scale architectural model made of cardboard. You walk people through it and everything looks good on the surface so they start asking “when can we move in?” skipping all of the hidden engineering that still needs to be done and in some cases pressuring you to just waterproof the exterior so they can live in the model instead of building the real thing.
Re: The Speed of Prototyping in the Age of AI
#106Earlier quoted context omitted.
The same thing happened when figma made it easier make prototypes that looked real and people stopped doing low fidelity mockups. Everyone understands that a wireframe isn’t done yet and it’s easy to change at that phase.
Yes, though this has been a problem long before Figma or AI. Photoshop enabled pretty pictures of what a website / app / service might look like, and then these often became set in stone. One solution is to keep all mockups / prototypes strictly grey scale using bare bones vectors until every stakeholder has weighed in / signed off.
Oh yeah designers definitely did it with photoshop too but it took a lot more effort than sketching a wireframe.
Re: The Speed of Prototyping in the Age of AI
#107Earlier quoted context omitted.
The same thing happened when figma made it easier make prototypes that looked real and people stopped doing low fidelity mockups. Everyone understands that a wireframe isn’t done yet and it’s easy to change at that phase.
Yes, though this has been a problem long before Figma or AI. Photoshop enabled pretty pictures of what a website / app / service might look like, and then these often became set in stone. One solution is to keep all mockups / prototypes strictly grey scale using bare bones vectors until every stakeholder has weighed in / signed off.
"Signing off" doesn't exist because even after the thing is in a MVP stage the stakeholders will still want to change it
Re: The Speed of Prototyping in the Age of AI
#108The page shows up however briefly and then there's a full screen error message saying "This page couldn’t load" In the browser javascript console I see "Uncaught TypeError: can't access property "ordinal", r is undefined"
I guess they prototyped the site too quickly.
Re: The Speed of Prototyping in the Age of AI
#109[dead]
Re: The Speed of Prototyping in the Age of AI
#110Productivity has increased only for people who knows what they are doing. I have been able to increase my productivity to build and turn around things faster and in a much polished manner. One problem is too many things goes on in your head and I see using tools like Jira or notion are very handy to capture all edge scenarios, integrations need to be captured. Taking break from AI is very very essential for this to w…
AI is like a really fast car - a good driver can cross a state a day but a bad driver can go the wrong way fast