3 ms·

Very cool but why do we have to use GUI "prototyping" (mockups) nowadays, why we can't compile a prototype straight into release code anymore like we did during

Very cool but why do we have to use GUI "prototyping" (mockups) nowadays, why we can't compile a prototype straight into release code anymore like we did during the Delphi and WinForms days?

flakiness 6y ago
It's mostly because of the job specialization - In a project, there is an engineer and there is a UX person. There are also UX-minded engineers and these people tend to skip the mock-up and just dive into the code. The semi-WYSIWYG editing in IDEs still aren't that bad.
mhd 6y ago
Note that "GUI" in this case can often mean "web page" and/or cross-platform mobile views. (Also because a company might up to three non-coding jobs being entangled in this mess before it even reaches a programmer.)
- spacemanmatt 6y ago
  Exactly this. Giving non-developers a communication tool that lets them compile their needs into a form developers can work with rather directly is extremely valuable to organizations.
robertlagrant 6y ago
> why we can't compile a prototype straight into release code anymore like we did during the Delphi and WinForms days? You probably can if you're making something with zero styling for one version of one OS on a 640x480 non-touch screen in one language that can't be deeplinked into from other applications for people with no accessibility requirements.
- tl 6y ago
  Ok, sure. Why can't we start with something that works with zero styling for one version of one OS on a [fixed resolution] non-touch screen in one language that can't be deeplinked into from other applications for [some people] and figure out if we're even building the right thing before we go "zOMG web-scale" and pretend we're making the next iPhone? I'd also argue that "zero styling" means "standard controls" which often already have good accessibility, and everything (including accessibility?) can be added (re-written in?) after you have a winner.
  - robertlagrant 6y ago
    We can and do start with things like that. E.g. bubble.io can be good. People also often start with Excel, or Google Forms and Google Sheets. Or just use a tool like pencil and go more design-first.
- zikzak 6y ago
  Is that company hiring?
GordonS 6y ago
I'm an Architect and/or Tech Lead (depending on project), rather than a UI/UX person, but sometimes I work on smaller projects that don't have a UI/UX Designer assigned to them. At the start of a project, I generally have several workshop meetings with relevant people from the customer. After finding out a bit about what they want, I use Figma to start building UI mockups - I can adjust these on the fly during calls, based on the discussion. Being able to make tweaks in seconds (basically in real-time with the conversation) is really important. Having these visualisations always helps generate/foster discussion.

Very cool but why do we have to use GUI "prototyping" (mockups) nowadays, why we can't compile a prototype straight into release code anymore like we did during the Delphi and WinForms days?

flakiness 6y ago

It's mostly because of the job specialization - In a project, there is an engineer and there is a UX person. There are also UX-minded engineers and these people tend to skip the mock-up and just dive into the code. The semi-WYSIWYG editing in IDEs still aren't that bad.

mhd 6y ago

Note that "GUI" in this case can often mean "web page" and/or cross-platform mobile views. (Also because a company might up to three non-coding jobs being entangled in this mess before it even reaches a programmer.)

spacemanmatt 6y ago
Exactly this. Giving non-developers a communication tool that lets them compile their needs into a form developers can work with rather directly is extremely valuable to organizations.

robertlagrant 6y ago

> why we can't compile a prototype straight into release code anymore like we did during the Delphi and WinForms days? You probably can if you're making something with zero styling for one version of one OS on a 640x480 non-touch screen in one language that can't be deeplinked into from other applications for people with no accessibility requirements.

tl 6y ago
Ok, sure. Why can't we start with something that works with zero styling for one version of one OS on a [fixed resolution] non-touch screen in one language that can't be deeplinked into from other applications for [some people] and figure out if we're even building the right thing before we go "zOMG web-scale" and pretend we're making the next iPhone? I'd also argue that "zero styling" means "standard controls" which often already have good accessibility, and everything (including accessibility?) can be added (re-written in?) after you have a winner.
- robertlagrant 6y ago
  We can and do start with things like that. E.g. bubble.io can be good. People also often start with Excel, or Google Forms and Google Sheets. Or just use a tool like pencil and go more design-first.
zikzak 6y ago
Is that company hiring?

GordonS 6y ago

I'm an Architect and/or Tech Lead (depending on project), rather than a UI/UX person, but sometimes I work on smaller projects that don't have a UI/UX Designer assigned to them. At the start of a project, I generally have several workshop meetings with relevant people from the customer. After finding out a bit about what they want, I use Figma to start building UI mockups - I can adjust these on the fly during calls, based on the discussion. Being able to make tweaks in seconds (basically in real-time with the conversation) is really important. Having these visualisations always helps generate/foster discussion.