It's good to keep in mind that it's worth doing a few projects full of these concepts if you're unfamiliar with them just to know that they exist and how to utilize them. This way when you decide not to use those concepts in the future you make a conscious decision about it rather than having a barrier and being influenced by opinions from others
Gary, I have a question for you about auto layout. I am one of those people who likes to use a lot of auto layout so that the design behaves almost like a real website in terms of vertical flow. For example, I can make changes somewhere at the top of the page and everything below will automatically adjust without me having to move elements around. How do you deal with situations like this? Especially on long pages, don't you find it annoying to reposition elements all the time just because a heading became one line longer?
I just thought about this as well. I agree that newbies shouldn't touch auto layout until they understand basic design principles but I cannot imagine not doing it while you understand it. Auto layout saved me a tons of time just by giving ability to swap things instead of moving everything around.
My boss is asking me to create only one frame for desktop, tablet and mobile and make everything responsive within one frame. Is this doable or should i tell him to stick with separate frames for each viewport?
I think frequently using auto layout makes a lot of sense because those are the constraints a developer will face. To fight against auto layout, means more work in the front end. Well, I'm a developer myself, so I don't want to make things harder to me in the next step haha
LETS DO THIS WHILE YOU SPEAK: 1. Correct, auto layout is always asking for problems. I even tried to do this with tables during the "best viewed in Nutscape" days and uh heeheheheh well... I got yelled at. 2. I still do desktop first or rather I'm forced to because many designers still like do it this way. 3. I tend to use Flexbox more often and not because I prefer it, it just fits the design better. 4. Yeah, a design system adds a good 35% extra work time from my past experiences. 5. LOL I think might've used all that stuff in... 5 projects? Over the past 15 years... 6. Again, used a wireframe maybe 3 times in a project over the past 15 years. 7. Did this all the time... Back in Flash... Which was 2003. Useless now. 8. Speed made the 80's and wallstreet, we need to go back.
03:24 that it's not a Myth -_- but I understand that from a pure UI Designer perspective may seem a myth, unfortunately thinking about as a myth, it's just ignorance about how UX Design was born an how interactions are actually designed and they are not designed by guessing, which was what was happening up to the middle of 70s and early 80s when within HCI people began to understand it was the wrong approach as was leading to poor products and waste of time and money, I mean it's an historical fact, it's on papers and books. Indeed that is main difference between UX Design and Web Design, the second one design by guessing, UX doesn't.
The way i look at this is that you are talking 100% from a UI perspective and not UX. I understand what you are saying in the video, but i fundamentally disagree with all of them i think, except for the one about prpototypes. The micro animations and stuff like that are most of the time not needed for prototypes except if the developers ask for it so they can recreate them. A big positive of doing all of this is to develop habits, which is a big part of being new in any field. Developing bad habits will serve you no good, and to "break rules" is another one that is imho a bad idea when starting out. To break the rules you need to first know the rules. Learning the fundamentals is crucial in any field, and all of this is fundamental..they are the buildingblocks. Design isnt art, its design. Good video, but, i disagree with all of it 😄
What do you do, or DON'T do, that other designers would think you're nuts for?
Design desktop first and move down. Co workers say that’s not the way but I work much faster and my designs come out much better on all screens
It's good to keep in mind that it's worth doing a few projects full of these concepts if you're unfamiliar with them just to know that they exist and how to utilize them. This way when you decide not to use those concepts in the future you make a conscious decision about it rather than having a barrier and being influenced by opinions from others
💯
Gary, I have a question for you about auto layout. I am one of those people who likes to use a lot of auto layout so that the design behaves almost like a real website in terms of vertical flow. For example, I can make changes somewhere at the top of the page and everything below will automatically adjust without me having to move elements around. How do you deal with situations like this? Especially on long pages, don't you find it annoying to reposition elements all the time just because a heading became one line longer?
I just thought about this as well. I agree that newbies shouldn't touch auto layout until they understand basic design principles but I cannot imagine not doing it while you understand it. Auto layout saved me a tons of time just by giving ability to swap things instead of moving everything around.
I agree with all of this. Exactly how I work too
My boss is asking me to create only one frame for desktop, tablet and mobile and make everything responsive within one frame. Is this doable or should i tell him to stick with separate frames for each viewport?
Yes, you can do it with autolayout.
auto layout is goated for frontend devs who already know how flexboxes work
half of time I'm just staring at your biceps.
I don't even know what auto-layout is.
I Just auto layout for cards and sections
Since I started making sites in Framer, I have understood why auto layout is needed.
I think frequently using auto layout makes a lot of sense because those are the constraints a developer will face. To fight against auto layout, means more work in the front end. Well, I'm a developer myself, so I don't want to make things harder to me in the next step haha
LETS DO THIS WHILE YOU SPEAK:
1. Correct, auto layout is always asking for problems. I even tried to do this with tables during the "best viewed in Nutscape" days and uh heeheheheh well... I got yelled at.
2. I still do desktop first or rather I'm forced to because many designers still like do it this way.
3. I tend to use Flexbox more often and not because I prefer it, it just fits the design better.
4. Yeah, a design system adds a good 35% extra work time from my past experiences.
5. LOL I think might've used all that stuff in... 5 projects? Over the past 15 years...
6. Again, used a wireframe maybe 3 times in a project over the past 15 years.
7. Did this all the time... Back in Flash... Which was 2003. Useless now.
8. Speed made the 80's and wallstreet, we need to go back.
Nice video, need to come back to this in future!!
03:24 that it's not a Myth -_- but I understand that from a pure UI Designer perspective may seem a myth, unfortunately thinking about as a myth, it's just ignorance about how UX Design was born an how interactions are actually designed and they are not designed by guessing, which was what was happening up to the middle of 70s and early 80s when within HCI people began to understand it was the wrong approach as was leading to poor products and waste of time and money, I mean it's an historical fact, it's on papers and books.
Indeed that is main difference between UX Design and Web Design, the second one design by guessing, UX doesn't.
The way i look at this is that you are talking 100% from a UI perspective and not UX. I understand what you are saying in the video, but i fundamentally disagree with all of them i think, except for the one about prpototypes. The micro animations and stuff like that are most of the time not needed for prototypes except if the developers ask for it so they can recreate them. A big positive of doing all of this is to develop habits, which is a big part of being new in any field. Developing bad habits will serve you no good, and to "break rules" is another one that is imho a bad idea when starting out. To break the rules you need to first know the rules. Learning the fundamentals is crucial in any field, and all of this is fundamental..they are the buildingblocks. Design isnt art, its design. Good video, but, i disagree with all of it 😄
It wastes my time so i skip it unless absolutely necessary
I auto layout everything !