Design is less to do with the implementation and more to do with the planning. Engineering is more the implementation, less so of the pre-planning stuff.
it would be a good start if people stop using the damn termn „UX“ in the first view sentences and then want to talk about design and its language. The strict language in design is there to avoid vague and almost esoteric terms such as „experience“
I'd like to know : 1. how to tell the designers, how to use Photoshop so that they would work with DP and not pixels. 2. creating vectorDrawable, since currently they create SVG file that I need to convert via online tool 3. creating small-space images files (png and WebP), right within their tools. It's quite annoying to do it manually
This was very informative, even as a designer it is good to refresh the old noodle.
I'd love to see a sequel focused on research!
awesome, I feel like a designer now
Jank - what Samsung's TouchWiz produces on older phones and older Android devices from other OEMs.
What about *Desiigner*
I'm a designer. But i don't speak much for a designer which is i think is a personal problem for me.
Good to see I'm not the only one.
Design is less to do with the implementation and more to do with the planning. Engineering is more the implementation, less so of the pre-planning stuff.
it would be a good start if people stop using the damn termn „UX“ in the first view sentences and then want to talk about design and its language. The strict language in design is there to avoid vague and almost esoteric terms such as „experience“
Cool video, thanks!
I'd like to know :
1. how to tell the designers, how to use Photoshop so that they would work with DP and not pixels.
2. creating vectorDrawable, since currently they create SVG file that I need to convert via online tool
3. creating small-space images files (png and WebP), right within their tools. It's quite annoying to do it manually
call me google
Hey Google, how are you?
+Pedro M. Zamboni (Zambonifofex) stupid.
+Pedro M. Zamboni (Zambonifofex) lol