Section Insights
Introduction to the Composer Box
What is the purpose of the composer box?
The composer box is a simple interface for user interaction with an AI, designed to facilitate communication.
- The composer box is a fundamental tool for user interaction.
- Design choices like button labels and icons are subjective and require careful consideration.
- The placeholder text in the box can influence user engagement.
Adding Functionality to the Composer Box
What additional features should be included in the composer box?
Images, file attachments, and web search capabilities are essential for enhancing user experience.
- Images provide context and enhance communication.
- File attachments should be represented clearly, possibly with a paperclip icon.
- Web search functionality is important and should be intuitively represented.
User Interaction Decisions
How should attachments and user inputs be managed in the composer box?
Attachments should be placed inside the input area, and the interface should allow for easy removal or closure of attachments.
- The placement of attachments affects user experience and should be intuitive.
- The interface should accommodate both voice and text inputs effectively.
- User feedback mechanisms, like showing a loading state, are crucial.
Dynamic States and Feedback
What states should the composer box indicate during use?
The composer box should reflect various states like 'working', 'sending', and 'fail', with visual cues for each state.
- Visual feedback enhances user understanding of the system's status.
- Different states can be represented through animations or color changes.
- The box should dynamically adjust its position and size based on user interaction.
Design Considerations and User Needs
What design elements should be prioritized for user engagement?
The design should incorporate user needs for functionality, such as disclaimers, upgrade options, and help features, while maintaining simplicity.
- User needs should drive design decisions, balancing functionality with usability.
- Incorporating elements like help bubbles and upgrade prompts can enhance user experience.
- The designer must assert control over the design to prevent unnecessary complexity.
Transcript
0:00 The life of a composer. Now, not the music kind. Sorry, no. This guy. The box where you type to an AI Now, I have spent years on it. Years on a box. It looks so simple, right? Just four sides, four corners. So how hard can it be? Okay, so let's get started, I guess it needs a button right now. It should say send, submit, create, talk. They all work. So how do I pick? It's all subjective, so send, I guess.
0:33 Now, should it be label an icon or just label just the icon? Again, I like all three and it's not helping. So just a straight arrow up, okay? Or maybe a curved one or a paper plane, like sending an email. Or an arrow pointing up to the right. Or you know what, a return key, you know, like. Like the keyboard one straight up. The first one, of course. Now the placeholder. What should it say? Type a message, Ask anything.
1:03 What's on your mind. Maybe just nothing at all. I mean, does anyone read it? Because I don't. But it's there to give us an idea, to give us peace of mind so it doesn't look empty and give us horror, vacuum. Because, well, we fear the vacuum, the emptiness. We gotta have something, feel the void, don't we? Okay. Anyways, so type a message, ask anything. Type a message, ask anything. Yeah, that's okay. Okay, now. Damn.
1:33 Fun, fun, fun, fun, fun. Should it be serif? Classy or maybe mono, just like a little bit techie or Comic Sans, you know, because it's so cool that now it's cool now. Yeah, just serif. Or maybe just boring. Reliable system font. Yeah, I guess that's gonna be it. Okay, now the size 14. 15. 14, 15. 14, 15 or 16. Or maybe just a little bit under 16. And on mobile it zooms in.
2:04 Now 16. Okay, now the width of it should be full width, narrow or just right, you know, with a max width so it doesn't get too, too white. Now what's the max? 720, 768, 800. You know what? I'll pick one and regret it later. Now, the background should be light gray and the input white or the opposite. Both look fine. And that's the problem. Okay, now around, it should have a shadow or an outline.
2:35 Maybe only the shadow. Or a bigger shadow, softer shadow, subtler shadow. Maybe just the outline. Perhaps both. Or none. I mean, no, no, I cannot even see it. I guess both, but soft, I think. Okay, now the box should be square. Oh, but if we do the box square, now the button should also be square, right? But maybe squarish or route? Now super round. Okay. I mean, it's just the corner, so why do I care?
3:05 Okay, okay. Okay, this is it. A box and a button. Oh, my God. We're done. No, wait. I guess we need to add images, right? For context. Because, well, images tell a thousand words. Great. That's it? Just images. Oh, no. What about other files and video? Oh, man, this is getting super crowded. Okay, I guess we're going to add a second story. It was so clean a minute ago.
3:37 Perhaps it should be just one. One icon. You know, for attachments. But what icon? Maybe a clip is better. A paper clip. We still use this paper. Okay. Also, we need web search. But that icon looks like it's searching on the chat. So what represents web? A globe, A webpage icon. I guess the globe is the web. Even round. And for tools, should it be a gear, a wrench? Three dots, sliders? A different gear?
4:07 No sliders. Final answer for today. See, every little decision is a rabbit hole. This is getting out of hands. So I guess I could put all of these things in a popover menu. You know, like under applause. But where should we put it? Left, like it is right now. Or maybe on the right. Or outside now outside, below? No, inside. Right where it started. Okay, now it's done. Oh, wait. I guess we need a model.
4:37 Switcher should say model. Or maybe the name of the selected model. Or an icon. But an icon of what? What does a popover show? Just the names, a line about each. The icons to show speed, costs, versions, the older ones, the new ones, everyone we have ever made. Okay, Just the latest ones. The rest go in a submenu and the rest of the rest in a sub. Sub menu. And on the button, just the name and the little arrow, which is called a carrot, which sounds like a caret.
5:12 Okay. No, not now. Wait. I guess this could just be inside the plus with a sub menu. Now, should I replace the current menu? You know, like this? Like this and then here. Or pop out on the side should it appear on click or on hover. Hover is for people who know what they want. So hover it is. Nah, let's just keep the switcher outside. I mean, do people even switch? I do, but I'm not people.
5:42 Okay, it needs voice. Now, should it be on the left? No, next to send. It makes sense. Now, what does listening even look like? Should it be bars? A wave? A ring? An orb? Does it breathe? Does it move when I talk? What color is a voice? What color is a voice? In the dark? A face? It's looking at me. Wait, we were on the composer. I'm getting distracted. Okay, let's just do an MVP and we'll work on this thing later.
6:16 Okay. Where do attachments go? Hmm? Should they go above or outside the input? Or inside the input? Inside. Yeah, it makes sense, right? But above was nice, so no inside. But ask me again tomorrow. I'm going to be changing my mind. I mean, just refresh the page. You're going to see something different. Okay, now, to close or remove it, the X, should it be on the attachment inside or on the corner? Should it appear on hover?
6:48 There's no hover on the phone. Now, if it's still uploading, should it appear or not? I guess it should appear, right? No or no X until it's up. Okay, now, voice versus dictation. Are they the same button? No, they're not the same. I mean, can I explain the difference? Not really. Okay, send the button when the box is empty. Should it be disabled or hidden? Or it turns into the voice button and back into send when you type.
7:21 You know, like this voice and then send when you type. Yeah, yeah, that makes sense. That way we don't need two icons, one button, two jobs. Look at that. Boom. Okay, so how do I show usage? Should it just be here with text? Or maybe a little ring? Or maybe I shouldn't. Is hiding it. Honestly. Now, what about context, skills, connectors, effort, autonomy, plugins? So much stuff. I guess some of it should go inside the plus and maybe some of it outside.
7:56 But what goes inside and what stays outside? Simplify, simplify, simplify. Yeah, that's better. Okay, now we can go back to a single story. We keep ending up where we started. Huh? I know there's a lesson in there somewhere. Okay, done for real this time. Okay, what should the enter key do? Should it send or make any line? I mean, people could use shift and enter, but there's no shift on a phone.
8:29 You know what? Enter sense and that's it. Someone will hate it. And that's okay. Now, spell check. Should it be on? I mean, does an AI care about typos? I just assume it knows I have lost all my ability to write clearly, which means long prompts. At what point does it stop growing in height? And maybe once it grows, we can make it scrollable. That is a lot. So maybe we should put a cap. Five lines.
8:57 Eight. Five, Eight. You know what? I'm going to pick five. No idea why. You know what? A pasted wall of text with you paste something. Should it Become an attachment chip instead of filling the whole box. And maybe you can drop the file anywhere on the page. The whole page has become the composer, the box. There's no escape. Okay, what about states? Working, sending, thinking, fail. All of them.
9:28 Oh, my God, that's a lot of iterations. Now fail, should shake. And thinking gets a rainbow border, a shader of colors. It's so pretty, right? But you know what? Shouldn't just the chat just say that? Yeah. Okay, some of these states are solved in the chat that they should not be solved on the composer. Which reminds me, right now the box sits in the middle of an empty page. After the first message, it has to move to the bottom.
9:59 But does it slide, jump, stay? I guess it slides. And down there it has to grow up. There you go. Okay, I hit send. While it's working, should show a stop button. And if you type the next message, does it queue or interrupt or refuse? Just like. No, no, no. You gotta load the flow, right? So it should allow you to keep going. Okay, Now, a new chat should have a welcome message. How big big should it be?
10:27 Well, I guess not that big. Show smaller, but not that small. So somewhere in between. Now, what should it say? How can I help? Where were we? Ready when you are. Or maybe should it just randomize different messages when you come back? Or be smart. Perhaps it knows the time, so it can say good morning. And you know what, in dark mode, it can say good evening. Perhaps it knows your name and the weather, the day, the city, your calendar, how you slept.
10:58 Okay, now that's creepy. Still creepy. Okay, that's good. Good morning, Pavs. Yeah, I like it. Now, should I have prompt suggestions? Should they be inside the box? I feel like people don't use those fixed suggestions. I mean, I don't use them, so maybe they should just be smarter. Perhaps they should appear in the placeholder and you just press tab, which I'm pretty sure nobody will find it. And you know what? I love it. Now, should suggestions appear as you type?
11:31 Now that kills the flow. And for coding. Oh, my God, coding. So much stuff. Because we're going to need repo and the local, or maybe the cloud and git, by the way. What's git? You know what if we separate chat in encode, that keeps things clean, right? Code chat, code chat. Now, it's the same AI I'm talking to, so it can just chat in code one box. Now, what if you type a slash for commands?
12:01 You type and then it starts filtering what you type. Now, does it open above or below? Wait, that's the plus menu too, right? Two doors, same room. And at. At is for things or people. And slash is for actions. Yeah, I like it. Now there's a file. Does it become an attachment pill or part of the sentence? That's going to be confusing, right? An attachment sentence. Attachment sentence. Okay, I'll decide later.
12:32 Now, who's going to find these? Perhaps we should add a hint. Now, if you type slash, you already know what you want. Okay, so now, legal, they want a disclaimer. You know what market once, a banner. And sales. Well, they want an upgrade button. And growth. Well, they want the streak and support. Well, they need a help bubble. And brand. Well, a mascot. And research, they need a survey. Five stars. And privacy. You know, a cookie banner, which I keep clicking.
13:05 Okay. And keeps appearing back. And obviously the CEO wants it to feel more AI and make it pop. The box becomes real estate. But you know what? I'm the designer and I'm the one saying no. Get out of here. Remove, delete, buy, bow. Or not. No, really? No, no, no. The legal stays. Legal always stays.
13:36 But now legal wants one more line, a longer one. Consent, a checkbox, the signature. You know what? One line, final offer. O. Okay, back to the design. What if I doodle my ideas like a wireframe, Just some drawing notes, A mini drawing tool. You draw your idea right there and it becomes an attachment. This is it. But it needs colors. And an eraser undo, redo layers, a layers panel, an inspector.
14:09 We have here curves, paint brushes, flexbox, grid slides. Well, I guess we're gonna need speaker notes too. And a percent button. Wait, am I creating a design tool? Okay, okay, okay, okay. Never mind. Okay, now, accessibility. We cannot skip this. Okay, but the focus ring, which honestly I find ugly, but we need anyway the icon only button. That needs a label after all. Remember, it had a label once, but I removed it.
14:42 Now, touch targets, they need to be bigger, but not pokey, just tappable. Tappable enough. You know, what about this? What about that? Okay, stop touching it. Pablo, how started where it got all of that for a text box? Okay, finished, right? What if.
15:12 What if there's no box? Okay, maybe another time. To be continued. Thank you.
Summary
- Designing a text input box involves numerous subjective decisions, including button labels, icons, and placeholder text.
- The speaker grapples with aesthetic choices like font type, size, and color schemes, emphasizing the importance of visual appeal.
- Functionality considerations include how attachments and voice input should be integrated, as well as the behavior of the send button.
- The discussion highlights the balance between simplicity and functionality, with a focus on user experience and accessibility.
- The speaker contemplates the implications of various design elements, such as popover menus and context-aware suggestions.
- Legal and marketing requirements complicate the design process, adding layers of necessity that can detract from user experience.
- The speaker humorously acknowledges the potential for endless iterations and changes, reflecting on the chaotic nature of design work.
- Ultimately, the speaker suggests that perhaps a simpler approach, or even the absence of a box, could be a solution worth exploring.
Questions Answered
What is the purpose of the composer box?
The composer box is a simple interface for user interaction with an AI, designed to facilitate communication.
What additional features should be included in the composer box?
Images, file attachments, and web search capabilities are essential for enhancing user experience.
How should attachments and user inputs be managed in the composer box?
Attachments should be placed inside the input area, and the interface should allow for easy removal or closure of attachments.
What states should the composer box indicate during use?
The composer box should reflect various states like 'working', 'sending', and 'fail', with visual cues for each state.
What design elements should be prioritized for user engagement?
The design should incorporate user needs for functionality, such as disclaimers, upgrade options, and help features, while maintaining simplicity.