the visuals in this presentation are beautiful, really shows the intricate in-depth appreciation and knowledge of good design principles, especially well suited for explainer-type situations like these.
Great video.... thanks. You should use a pop-filter in front of your mic. And please add a High Pass Filter (HPF) on your audio, to cut the low end. I use a real high level audio system to my computer setup and your POPs are smashing all my windows in my studio..... well. not true, but close.
Good video. It's essential that designers understand that their beautful designs are only a starting point; they are NOT the product. For many reasons -- from technical to usability to financial -- it may well be that a design cannot be implemented fully. In this case, the source of truth is actually the built product, whether it's an app or a web page or a magazine. The design is an *aspiration* that may need to be continually changed, refined or even discarded during the process. Also: pixel-perfect should not always be a design goal. Pixel-perfect hasn't been a real thing for a long time now, given the need for dynamic type, localizations, responsive layouts, accessibility settings etc.
We had many instances where the development was just sloppy/lazy and didn't follow the design, aligned with our own DS we have in Figma and angular, for absolutely no reason. Do you say that this questionable implementation should become the source of truth, and that I should revert back the designs to the bad dev execution because someone decided to overlooked design? I think not, and this is something that I told them that it is not going to happen. Dev should cease being lazy and stop working using the old ways.
@@effectvision The reality is that the build is the source of truth, regardless of how shoddy. It's subject to iteration, but the actual thing that the consumer is using, is the source of truth. The design remains an aspiration, until actually implemented. As for "following the design", it may be impossible or economically impractical to fully implement a design. (Design is relatively issue, development is hard.)
Hey Jake. Thanks for the series. Love it! We need a 7 Minute Snippets Playlist. Meanwhile, you can at least put links to the previous/next videos in the description. We're all product designers after all and we strive to make other's life easier ;) So for those who landed on this first and want to see the previous one - here you go ruclips.net/video/Gd1U79ReW00/видео.html
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
the visuals in this presentation are beautiful, really shows the intricate in-depth appreciation and knowledge of good design principles, especially well suited for explainer-type situations like these.
Loved this. Perfect acknowledgment of the realities we face. “Sometimes translation is easier than alignment” 👍
A good explanation for a sensitive topic in product development. Identifying the source of truth is the first step towards improvement.
I've been designing and building web UI for 20+ years, and I believe you'll make a great head of engineering one day, Jake. Real talk.
I’m gonna call it: this video is going to be referred to A LOT. ❤
Great video.... thanks. You should use a pop-filter in front of your mic. And please add a High Pass Filter (HPF) on your audio, to cut the low end. I use a real high level audio system to my computer setup and your POPs are smashing all my windows in my studio..... well. not true, but close.
Fantastic video. Thanks for making it ❤
Fantastic video, thank you! Production tip: try using a pop filter on your mic to reduce the harshness of the "p" and "s" sounds in the recording😊
Great explanation
Good video.
It's essential that designers understand that their beautful designs are only a starting point; they are NOT the product.
For many reasons -- from technical to usability to financial -- it may well be that a design cannot be implemented fully.
In this case, the source of truth is actually the built product, whether it's an app or a web page or a magazine.
The design is an *aspiration* that may need to be continually changed, refined or even discarded during the process.
Also: pixel-perfect should not always be a design goal. Pixel-perfect hasn't been a real thing for a long time now, given the need for dynamic type, localizations, responsive layouts, accessibility settings etc.
We had many instances where the development was just sloppy/lazy and didn't follow the design, aligned with our own DS we have in Figma and angular, for absolutely no reason. Do you say that this questionable implementation should become the source of truth, and that I should revert back the designs to the bad dev execution because someone decided to overlooked design? I think not, and this is something that I told them that it is not going to happen. Dev should cease being lazy and stop working using the old ways.
@@effectvision The reality is that the build is the source of truth, regardless of how shoddy.
It's subject to iteration, but the actual thing that the consumer is using, is the source of truth.
The design remains an aspiration, until actually implemented.
As for "following the design", it may be impossible or economically impractical to fully implement a design. (Design is relatively issue, development is hard.)
Amazing
“A quick polish” 🙃
Yes, that was a very practical advice there....
Hey Jake. Thanks for the series. Love it! We need a 7 Minute Snippets Playlist. Meanwhile, you can at least put links to the previous/next videos in the description. We're all product designers after all and we strive to make other's life easier ;)
So for those who landed on this first and want to see the previous one - here you go ruclips.net/video/Gd1U79ReW00/видео.html