Searching...
12 results for “user experience”
...a really bad experience because, you know, you stare at a blank input. You need to do something. You need to initiate the thing. You need to ask the right questions, put in the right prompt. You might not know what kind of response you will get unles
35:59 / 37:00
from transcript35:59 – 37:00
...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
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
...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
But then there's actually the aesthetics, every layer. How you architect, say, like, the front end code and architecture, how they, you know, how the reactive stays sync and how you render stuff to, like, how do you, like, store these objects, how th
23:11 / 24:15
from transcript23:11 – 24:15
...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
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
...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
...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
Right. Because it was seen as a very kind of solitary thing. Like, this is my vision. I'm gonna design it. You can maybe make some improvements, but this is my thing. Yeah. A lot of designers at that point were coming from an agency culture where, yo
50:52 / 52:00
from transcript50:52 – 52:00
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
...user despite people using us for powerful things. That's something that we work on a lot as an organization. Do you find yourself curious about the next layer of non flat digital screen design interfaces? How do you think about the other potential sp
24:44 / 25:45
from transcript24:44 – 25:45
Have a podcast?
Run your podcast through Clypt
Get ranked clips, hooks, and ready-to-post copy from your own episodes. Free to try.