"engineering can catch up". The problem there is that the engineering cost is about 1000 times the design cost. What takes an hour to do in Sketch, can take weeks to do properly in code, if it's even possible. And then there are all the edge cases, hacks and maintenance problems. Instead of creating designs that require the "engineering to catch up" a professional designer needs to be working WITH engineers, and producing designs that can be implemented in the real world, in a reasonable time frame, within available budgets. Otherwise, these are just designs that can work only in the imaginary world of Dribbble, where things like project cost, status bars, different display sizes, Dynamic Type and German localization don't matter. If the engineering team already has a realistic shadow compositing system in place, that's great: use it! But requiring (possibly very difficult) technical requirements in the design is going to give your team (and you) some big problems.
@@jatodaro It's not just design that pushes things forward -- anyone with a bit of training can push out aesthetically pleasing graphics -- it's the melding of design with engineering that makes the things people want and need. The concept is nothing without a practical, workable implementation. That's why for every 10,000 beautiful designs on Dribbble, there are a handful of truly excellent production apps out there.
And SwiftUI makes this concept easy to apply (despite not having quite as much control over the drop shadows). Here is some example code and screenshots: gist.github.com/brandenbyers/123b4978c1be00d72f908c84a53229cb I don't think the lighting is correct for the top rectangle's bottom shadow, but it should still convey the basic idea.
That's great for Dribbble, but developers hate me if I send this design on zeplin :(
You are doing the best video about sketch program. thank you
Great tutorial, can you add a file to download? can't repeat this in sketch 65
Thanks for nice video and explanation. Very useful tips.
You got it!
Nice explanation, is a lot useful.
Glad to hear it!
Sorry sir, how can you get that smoooooooth cursor movements? Thank you!
That's motion blur from Screenflow :)
"engineering can catch up". The problem there is that the engineering cost is about 1000 times the design cost. What takes an hour to do in Sketch, can take weeks to do properly in code, if it's even possible. And then there are all the edge cases, hacks and maintenance problems.
Instead of creating designs that require the "engineering to catch up" a professional designer needs to be working WITH engineers, and producing designs that can be implemented in the real world, in a reasonable time frame, within available budgets. Otherwise, these are just designs that can work only in the imaginary world of Dribbble, where things like project cost, status bars, different display sizes, Dynamic Type and German localization don't matter.
If the engineering team already has a realistic shadow compositing system in place, that's great: use it! But requiring (possibly very difficult) technical requirements in the design is going to give your team (and you) some big problems.
True to a degree - but if it weren't for design pushing things forward, everything would still look like Windows 3.1
@@jatodaro It's not just design that pushes things forward -- anyone with a bit of training can push out aesthetically pleasing graphics -- it's the melding of design with engineering that makes the things people want and need. The concept is nothing without a practical, workable implementation. That's why for every 10,000 beautiful designs on Dribbble, there are a handful of truly excellent production apps out there.
And SwiftUI makes this concept easy to apply (despite not having quite as much control over the drop shadows). Here is some example code and screenshots: gist.github.com/brandenbyers/123b4978c1be00d72f908c84a53229cb
I don't think the lighting is correct for the top rectangle's bottom shadow, but it should still convey the basic idea.
Very useful thx 😊
yes... black