Searching...
14 results for “user experience”
...user's coming from. They think only about a certain state that someone's in right now. And that context, if they lack it, can hurt them and hurt their experience. I think that they often are too indirect, so they have complex ways of manipulating dat
23:15 / 24:43
from transcript23:15 – 24:43
or folks that are going to be founders, when we look at the students that we reach with Figma through our EDU efforts, it's just incredible to see how advanced they are and how much they are deep diving on design as a discipline. And I think that mor
22:27 / 23:36
from transcript22:27 – 23:36
Like, there's there's lots of opportunities to try to develop that intuition of how people navigate the human computer interaction. And we we need to find ways to go do that. An important, element of what you're describing here, which I think, maybe
51:39 / 52:54
from transcript51:39 – 52:54
And when you when you jump to the expression of them, I think you're putting them at risk. I'll also say that, you know, everybody, when they when they look at a prototype, what they're focusing on is the visual and textual expression. And so as soon
1:13:29 / 1:14:33
from transcript1:13:29 – 1:14:33
Because I think that's the other piece of design is it's not just the artifact. It's knowing this is good, and, you know, we're gonna put the right sort of message behind it. And so for aesthetic, I mean, the ability to go think of all the possibilit
54:43 / 55:45
from transcript54:43 – 55:45
...do user studies and all that kind of stuff to figure out if it's approachable for a layperson.
21:45 / 22:49
from transcript21:45 – 22:49
...problems. You're trying to get to the hard user problems. Like, what is it they really want? You're trying to think about the system and how it shows up in all these different places. Yep. The brand, the way that you're able to incorporate culture, t
15:44 / 16:55
from transcript15:44 – 16:55
what should be in code, that is, I think, much more blurry than it used to be. Used to be that we had, obviously, this, like, very kind of waterfolly process of, oh, yeah. We're gonna go gather some requirements, and then we're gonna go, you know, ma
10:34 / 11:39
from transcript10:34 – 11:39
...of the experience that you're meant to pay extra attention to. And that I think that's good. But sometimes design just gets in the way. That we try too hard. You're putting too much weight on the user to overcome the interface and completely learn a
20:14 / 21:18
from transcript20:14 – 21:18
command lines, agents, IDs are kind of moving moving, to not be cool anymore since and it makes a lot of sense. You just wanna edit some CSS things, some, like, color stuff. And so I could see why not just telling the agent, hey. Just come on. Change
21:57 / 23:30
from transcript21:57 – 23:30
...experiences that you create are no longer bound to the scope of a surface. Just think about even how you interface with like a chattyPT, like in one conversation, you're going in multiple different directions. One, you're asking about the weather and
32:46 / 34:00
from transcript32:46 – 34:00
...user, what are the breakthroughs we can introduce? Can we make a better way to create
37:30 / 38:33
from transcript37:30 – 38:33
...for the user right on? It's like, hey. I'm actually not gonna you you need to make some aesthetic choices, early on. Yeah. I I feel very strongly that, across the Fumo platform, we should do our best to find ways to help people explore more of the sp
23:54 / 25:04
from transcript23:54 – 25:04
app. It's a bit more complex product, so it's harder to give the context to an LLM to build things that are that look very close to the original one. Do you think we are going to skip the design phase in the future of product build outs and move stra
26:54 / 28:03
from transcript26:54 – 28:03
Have a podcast?
Run your podcast through Clypt
Get ranked clips, hooks, and ready-to-post copy from your own episodes. Free to try.