WEBVTT 00:00.000 --> 00:06.000 Oh, everyone can hear me, take it. 00:06.000 --> 00:13.000 Everyone, this is Laurel Thorelesky, and they're gonna get started. 00:13.000 --> 00:15.000 I am high. 00:15.000 --> 00:21.000 Okay, well it's okay, right? 00:21.000 --> 00:22.000 Everybody can see? 00:22.000 --> 00:24.000 Can you hear me in the back? 00:24.000 --> 00:25.000 Yeah, okay, good. 00:25.000 --> 00:28.000 Does anyone need to stand up and kind of move for a minute? 00:28.000 --> 00:29.000 I've been in here a while. 00:29.000 --> 00:30.000 Oh, good. 00:30.000 --> 00:31.000 Come on. 00:31.000 --> 00:32.000 Thunderbird. 00:32.000 --> 00:33.000 Okay. 00:33.000 --> 00:35.000 Who's a Thunderbird fan out there? 00:35.000 --> 00:36.000 Which one? 00:36.000 --> 00:37.000 Yeah. 00:37.000 --> 00:39.000 And who's downloaded Thunderbird for Android? 00:39.000 --> 00:40.000 Oh, couple. 00:40.000 --> 00:42.000 Oh, more, more, more popping up. 00:42.000 --> 00:45.000 And are you excited for Thunderbird for iOS? 00:45.000 --> 00:46.000 Question mark. 00:46.000 --> 00:47.000 Question mark. 00:47.000 --> 00:48.000 Okay. 00:48.000 --> 00:49.000 Okay. 00:49.000 --> 00:51.000 As I'm up here with all my Mac devices, right? 00:51.000 --> 00:52.000 Okay. 00:52.000 --> 00:53.000 Hello. 00:53.000 --> 00:58.000 So I'm excited to be here at Phosem, and thank you to Earl and your team for organizing this room. 00:58.000 --> 01:01.000 It's great in the sea of development. 01:01.000 --> 01:05.000 This is my first, so please be gentle and kind. 01:05.000 --> 01:08.000 I'm the design manager at Thunderbird. 01:08.000 --> 01:13.000 Just some of my team here, and some of the team is here as well in the audience. 01:13.000 --> 01:18.000 A pause for just a moment and ask if anyone is visually impaired on the audience. 01:18.000 --> 01:21.000 If you are, I'll describe the slides. 01:21.000 --> 01:22.000 Hey, hands. 01:22.000 --> 01:23.000 Everybody's good. 01:23.000 --> 01:24.000 Okay. 01:24.000 --> 01:25.000 I won't double up then. 01:25.000 --> 01:27.000 There's some text up there. 01:28.000 --> 01:29.000 Okay. 01:29.000 --> 01:40.000 So last year, Alessandro, our director of desktop and mobile apps, talked about how Thunderbird entered the modern UI era of simplicity and consistency. 01:40.000 --> 01:46.000 By prioritizing user-centered design and accessibility, Thunderbird is finally catching up with the competition. 01:46.000 --> 01:52.000 We're working really hard to reduce visual clutter and enhance the mutability of our productivity tool. 01:52.000 --> 01:56.000 And take your camera. 01:56.000 --> 01:57.000 Okay. 01:57.000 --> 02:07.000 Now, if you're familiar with Thunderbird and the UI UX journey, you're probably familiar with the complexity and challenges of its dense interface. 02:07.000 --> 02:16.000 Many of you experience the improvements introduced by version 115, also known as Supernova, and more recently improvements in 128 known as Nebula. 02:16.000 --> 02:23.000 These go to on that foundation, adding new features, better organization and visual refinements. 02:23.000 --> 02:32.000 Improvements to card's view, made scanning emails faster, and enhance the threaded experience, all while delivering a more visually pleasing design. 02:32.000 --> 02:38.000 Plus, the height of cards, making sure, based on your settings, it'll adjust automatically. 02:38.000 --> 02:44.000 So it ensures everything looks perfectly balanced at the end of the day. 02:44.000 --> 02:48.000 So that's simple, right? 02:48.000 --> 02:52.000 When designers need spreadsheets, we're in trouble. 02:52.000 --> 03:05.000 So as you can see through this project, there was the discovery of at least 42 different selection states, each with its own style, completely inconsistent and a nightmare to implement properly. 03:05.000 --> 03:13.000 So it took a while, but new selection states were landed, and you see them today in the interface. 03:13.000 --> 03:17.000 So if you've explored the code base, you know it's not so simple. 03:17.000 --> 03:31.000 That said, when using Thunderbird, you recognize the visual cues and the interaction states, and there's an expectation for these elements to maintain their integrity across Thunderbird experiences. 03:31.000 --> 03:38.000 With Thunderbird for Android, launching last year, the introduction of beta of Thunderbird appointment. 03:38.000 --> 03:40.000 Anybody tried that? 03:40.000 --> 03:42.000 Ooh, something to look at. 03:42.000 --> 03:49.000 Okay, anticipation of Thunderbird for iOS, and the value and importance of a cohesive design system become clear. 03:49.000 --> 03:51.000 Let's be real. 03:51.000 --> 03:56.000 Design systems at their core should be kind of boring. 03:56.000 --> 03:59.000 And that's a good thing. 03:59.000 --> 04:00.000 Why? 04:00.000 --> 04:04.000 Well, because then we can lock all the foundational decisions. 04:04.000 --> 04:06.000 Let's keep reinventing the wheel. 04:06.000 --> 04:17.000 All that reserved energy can go towards those beautiful aha moments, and all the spark innovation and ensure our products meet up with our diverse users. 04:17.000 --> 04:31.000 Plus, a solid design system keeps everything consistent across design files, product environments, and allow us to make updates quickly and seamlessly from a single source. 04:31.000 --> 04:33.000 Design systems. 04:33.000 --> 04:35.000 Every part needs a strong connector. 04:35.000 --> 04:39.000 Kind of like bolts that hold the structure together like a house. 04:39.000 --> 04:46.000 These bolts are components that keep the user experience consistent and reliable across platforms. 04:46.000 --> 04:49.000 At Thunderbird, these aren't just ordinary bolts. 04:49.000 --> 04:51.000 They're Thunderbolts. 04:51.000 --> 04:56.000 Adding the strength and power of a lightning strike into every interaction. 04:56.000 --> 05:04.000 By connecting our cross-platform design system, we're creating a solid, adaptable foundation ready for future growth. 05:04.000 --> 05:11.000 Starting with design principles are essential because they serve as the foundation for every decision made within the system. 05:11.000 --> 05:19.000 Our design principles prioritize creating a user-centered experience that is intuitive, inclusive, and respectful. 05:19.000 --> 05:29.000 We focus on familiarity, simplicity, and personalization all while empowering diverse users with accessibility and customization. 05:29.000 --> 05:38.000 By emphasizing privacy, collaboration, and craftmanship, we aim to deliver elegant, secure, and seamless interactions across platforms. 05:38.000 --> 05:42.000 So here are the principles that we came up with that shape or approach. 05:42.000 --> 05:47.000 I won't read everything, but consistent familiarity, this ensures that everything's familiar. 05:47.000 --> 05:50.000 It's simple, it's effortless. 05:50.000 --> 05:56.000 Inclusive freedom, we want our products to be adaptable, customizable, and accessible. 05:56.000 --> 06:01.000 Privacy companion, our products are your trusted partner and privacy. 06:01.000 --> 06:04.000 We want to humanize human collaboration. 06:04.000 --> 06:09.000 We make collaboration, doing what you need to do easier, and human, right? 06:09.000 --> 06:13.000 Not, you know, as if you're interacting with somebody. 06:13.000 --> 06:18.000 Craft, we always want things to be sleek and seamless. 06:18.000 --> 06:21.000 So what comes next? 06:21.000 --> 06:25.000 When I joined the team last year, I knew I had to do an audit. 06:25.000 --> 06:30.000 Both to become familiar with the product and to use my fresh eyes to spot inconsistency, 06:30.000 --> 06:35.000 and those sad face user experiences that might be present. 06:35.000 --> 06:41.000 Without diving too deep, I initially discovered 28 shades of blue. 06:41.000 --> 06:46.000 And that's without touching on even more colors, icons, textiles, and spacing. 06:46.000 --> 06:48.000 Spacing? 06:48.000 --> 06:51.000 Let's just say that it's silent chaos in every design. 06:51.000 --> 06:58.000 Clearly, we needed to establish some foundations before tackling the worst place to start a design system, the button. 06:58.000 --> 07:01.000 So, I don't know if you can help me that, but yeah. 07:01.000 --> 07:06.000 Today, Thunderbird still has 28 shades of blue, and they're all hard-coded. 07:06.000 --> 07:09.000 So, color is hard. 07:09.000 --> 07:11.000 That's really hard. 07:11.000 --> 07:19.000 After lengthy mulling and explorations, I eventually created a light and dark palette for Thunderbird brand and introduced color variables. 07:19.000 --> 07:27.000 Instead of relying on color styles, which would only add unnecessary complexity to an already intricate product, 07:27.000 --> 07:30.000 I opted for a simpler approach. 07:30.000 --> 07:38.000 The focus was on minimal variables, aligned with specific use cases, like surface elevation, primary colors, supporting colors, 07:38.000 --> 07:43.000 like success, warning, critical, text and icon colors, and then some accent colors. 07:43.000 --> 07:53.000 For contrast, we focused on AAA accessibility where we could, and gave into the limits of dark mode, ensuring AA accessibility. 07:53.000 --> 07:56.000 It's kind of exhausting, right? 07:56.000 --> 08:02.000 It's nice up here at the tip of the iceberg, but we all know design systems run deep, real deep. 08:02.000 --> 08:11.000 So, the rest of the foundation where it came along smoothly does help anatomy, typography styles, iconography, and spacing values. 08:11.000 --> 08:14.000 We're still figuring those ones out how to use. 08:14.000 --> 08:19.000 Still a work in progress, or alpha might be more familiar to some. 08:19.000 --> 08:32.000 To build our component library, we let projects drive what's to be included in that shared library. 08:32.000 --> 08:34.000 So, no putting the cart before the horse. 08:34.000 --> 08:38.000 Everything's realistic, contextual, and thoroughly vetted. 08:38.000 --> 08:41.000 Complexity, we need to sport desktop. 08:41.000 --> 08:47.000 We need to sport Android, there's also web, all both in light and dark modes, so it's a lot. 08:48.000 --> 09:00.000 The goal is to create consistent visual language that ensures familiarity across all touch points, and making switching devices effortless, and seemingly adapt to your context. 09:00.000 --> 09:11.000 When we approach Thunderbird for Android using material three as a foundation, it allowed us to move quickly with a predefined design system that we could customize as we needed. 09:11.000 --> 09:19.000 You may notice a gap between desktop and Android today, but rest assured, they'll come closer together. 09:19.000 --> 09:29.000 Material three is powerful, but it's heavily influenced by Google's style, making it harder to customize and add unique branding for cross platform use. 09:29.000 --> 09:36.000 It also comes with challenges like uniformity and performance overhead. 09:36.000 --> 09:50.000 As we look ahead to building Thunderbird for iOS, Apple's human interface guidelines also present exciting opportunities and challenges, shaping how we adapt Thunderbird's design system to this whole new platform. 09:50.000 --> 09:53.000 It's going to be a swift journey. 09:53.000 --> 09:55.000 Okay, a few of you laughed. 09:55.000 --> 09:57.000 You got it. 09:57.000 --> 10:00.000 It's like pause with my jokes. 10:00.000 --> 10:08.000 Okay, so to tackle this and to ensure consistency across all experiences, we're working through a six phase process to build our design system. 10:08.000 --> 10:10.000 Here's how it all comes together. 10:10.000 --> 10:14.000 Design, right? We start with sticky notes everywhere. 10:14.000 --> 10:18.000 This is very hard to read, but I'm going to describe it. 10:18.000 --> 10:22.000 So phase one, we start with discovery and auditing. 10:22.000 --> 10:29.000 So first we identify the components in each project, reviewing styles, to see a foundational elements like color, typography, 10:29.000 --> 10:32.000 or brown guidelines, need updates. 10:32.000 --> 10:37.000 Then we create an inventory in each project file, evaluated against key criteria. 10:37.000 --> 10:41.000 Does it look consistent? Can it be reused in at least two contexts? 10:41.000 --> 10:44.000 Does it involve minimal user interaction? 10:44.000 --> 10:49.000 From there we add tasks to our notion boards so we can track of what's next. 10:49.000 --> 10:52.000 Then in phase two, purple thing. 10:52.000 --> 10:58.000 This is where the fun starts. We focus on designing flexible, reusable components and variations. 10:58.000 --> 11:02.000 For all different use cases, think of buttons in their various states. 11:02.000 --> 11:10.000 Along the way, we define and document styles like color, typography, and spacing making sure that it's aligned. 11:10.000 --> 11:15.000 And then we make sure accessibility states front and center with standards like WayCag. 11:15.000 --> 11:20.000 Once everything is ready, we publish the components and styles for a shared library in Figma. 11:20.000 --> 11:26.000 And that's your Pablo's here, but we're aiming to transition to Penn Pot in the future, 11:26.000 --> 11:30.000 just to make sure that we stay aligned with our values. 11:30.000 --> 11:32.000 Thank you for your. 11:32.000 --> 11:36.000 So phase three, this is front and preparation. 11:36.000 --> 11:43.000 Here we get into the needy grid of front and work, creating our updating CSS variables and prepping variables for Android. 11:43.000 --> 11:49.000 We also prepare design documentation to guide designers and use like usage instructions. 11:49.000 --> 11:55.000 We export assets for development and flag components as ready for implementation. 11:56.000 --> 12:02.000 In phase four, we're at development. This is where the components come to life. 12:02.000 --> 12:09.000 Developers build, implement, and integrate the mentor projects, often replacing or updating similar existing items. 12:09.000 --> 12:17.000 Clear documentation supports this phase, ensuring the components are used consistently and easy to maintain. 12:17.000 --> 12:19.000 Martin, where'd you go? 12:19.000 --> 12:25.000 There he is. Martin, where'd you go? He likes to refer. He's a staff software engineer for desktop. 12:25.000 --> 12:32.000 And he likes to refer to this phase as make the thing, use the thing, document the thing, right? 12:32.000 --> 12:38.000 Okay. Documentation. This is the time that we tie it all together. 12:38.000 --> 12:44.000 We implement components in a centralized library, like Storybook or Wolf Jetpack Compose, yep. 12:44.000 --> 12:47.000 So it's easy to reuse across projects. 12:48.000 --> 12:56.000 We also create friendly, comprehensive documentation that includes design principles, component usage, code examples and best practices. 12:56.000 --> 13:03.000 A version control system helps us manage updates and communicate changes, making sure the whole team stays in sync. 13:03.000 --> 13:07.000 Last phase, governance and maintenance. 13:07.000 --> 13:11.000 So this phase is all about the design system running smoothly. 13:11.000 --> 13:16.000 We have a governance model with clear roles and responsibilities to manage and involve the system. 13:16.000 --> 13:22.000 We use help us keep up to date with new project needs, user feedback and tech advancements. 13:22.000 --> 13:29.000 We also engage with the community encouraging feedback and contribution to keep it relevant and effective. 13:29.000 --> 13:32.000 So this is our full lovely team. 13:32.000 --> 13:41.000 At Thunderbird, we're a small team of employees, lucky to have an amazing and dedicated community that generously puts their time and energy into making our products better. 13:41.000 --> 13:48.000 Historically, most of our contributors have been developers and many of them have tackled UX UI challenges with remarkable care. 13:48.000 --> 13:54.000 But here's the thing, where are all the designers? 13:54.000 --> 14:01.000 We'd love to see more designers joining us, especially to help shape and grow bolt Thunderbird's design system. 14:01.000 --> 14:06.000 We know that contributing as a designer to open source projects like Thunderbird can feel daunting at first. 14:06.000 --> 14:13.000 Barriers like developer-focused workflows, limited onboarding, lack of design tools can get in the way. 14:13.000 --> 14:20.000 But the good news is the door is wide open for designers to bring their unique talents to the table. 14:20.000 --> 14:24.000 I'm more making it. We're going to make that easier. 14:24.000 --> 14:30.000 At Thunderbird, we believe in the power of free and open tools to create a healthier, more accessible tech ecosystem. 14:30.000 --> 14:36.000 Values that resonate deeply with designers contributing to open source. 14:36.000 --> 14:44.000 By embracing these values and addressing common barriers, Thunderbird is working to create space where designers can feel contribute. 14:44.000 --> 14:50.000 Compared to contribute, whether you're improving a button, refining a layout or helping to take bolt to the next level, 14:50.000 --> 14:56.000 your efforts can help shape a cohesive and beautiful experience for Thunderbird users everywhere. 14:56.000 --> 15:03.000 Later this year, we're aiming to launch community files in Figma and Penn Pot featuring core UI elements from bolt. 15:03.000 --> 15:09.000 These files are all about empowering our growing design community to learn, collaborate, and create together. 15:09.000 --> 15:19.000 By sharing these resources, we're making it easier to keep designs consistent, scalable, and ready for collaboration across Thunderbird's open source ecosystem. 15:19.000 --> 15:24.000 As we wrap up, I would like to know how would you like to contribute to Thunderbird. 15:24.000 --> 15:34.000 Whether it's creating user research plans, conducting heuristic analysis, offering insights and guidance, improving accessibility through research and design, 15:34.000 --> 15:41.000 making components or patterns, your contributions can enhance design system for the design system for Thunderbird's ecosystem, 15:41.000 --> 15:48.000 specifically to help shape bolts design system for a more seamless and inclusive user experience. 15:48.000 --> 15:56.000 Before we flip this script for your questions and feedback, I have a little gift for you. 15:56.000 --> 16:01.000 Have you ever wondered where our Thunderbird rock calls home? 16:01.000 --> 16:11.000 Last year, we teamed up with an illustrator from Vancouver BC in Canada to bring rocks world to life, and what you see on the screen is a result. 16:11.000 --> 16:20.000 I'd love for you to take a piece of Thunderbird with you, so you can just scan the QR code and download this delightful wallpaper to use on your favorite device. 16:20.000 --> 16:23.000 I'll come back to the slide in two seconds. 16:23.000 --> 16:26.000 Just to say thank you for listening. 16:26.000 --> 16:28.000 And a few times. 16:36.000 --> 16:40.000 So back there if you need the QR code, but yeah, I think do we have time for questions? 16:40.000 --> 16:43.000 Okay, good. 16:43.000 --> 16:46.000 Okay, good, perfect. 16:46.000 --> 16:48.000 Excellent. 16:48.000 --> 16:50.000 Oh, I'll do that. 16:50.000 --> 16:52.000 Yes, I'm not getting used everywhere. 16:52.000 --> 16:53.000 Hi. 16:53.000 --> 16:54.000 Oh, hi. 16:54.000 --> 16:55.000 We're talking earlier. 16:55.000 --> 16:56.000 Hello again. 16:56.000 --> 17:00.000 So you talked about this big design overhaul. 17:00.000 --> 17:02.000 Well, this continual design overhaul. 17:03.000 --> 17:11.000 You also mentioned how a lot of developers in the past have tried to tackle a lot of UX and UI students. 17:11.000 --> 17:14.000 Did you recover any unexpected pushback on change? 17:14.000 --> 17:15.000 Did you type the implement? 17:15.000 --> 17:21.000 I'm curious how smoothly a lot of the changes went that you tried to push for. 17:21.000 --> 17:23.000 Who likes change? 17:23.000 --> 17:26.000 I have a, I have a persona ever user is called. 17:26.000 --> 17:28.000 Oh, my god, change. 17:28.000 --> 17:30.000 Oh, sorry. 17:30.000 --> 17:31.000 I can repeat the question. 17:31.000 --> 17:32.000 I'm so sorry. 17:32.000 --> 17:35.000 Yeah, so did we experience any pushback when we sort of to modernize the UI? 17:35.000 --> 17:36.000 Yeah, we did. 17:36.000 --> 17:37.000 For sure. 17:37.000 --> 17:39.000 That's what Alejandro talked about last year when he was here. 17:39.000 --> 17:40.000 For sure. 17:40.000 --> 17:44.000 There's definitely some people, especially New Year's or users too, that were like, 17:44.000 --> 17:48.000 Wow, finally, you know, much more easy to use, sense interface. 17:48.000 --> 17:52.000 But, you know, our trusted users are over the last 20 years. 17:52.000 --> 17:53.000 You know, they still like that. 17:53.000 --> 17:55.000 Like the way it was, you know. 17:55.000 --> 17:59.000 So yeah, slowly bringing some of them over and finding that new world. 17:59.000 --> 18:05.000 But, I don't know, for me, I know that when I was looking at the tool when I was, 18:05.000 --> 18:10.000 like last year, I was really digging into it and I was like, wow, kind of feel like I'm in the 90s. 18:10.000 --> 18:11.000 That's cool. 18:11.000 --> 18:13.000 There's folders and folders and folders and folders. 18:13.000 --> 18:14.000 And of course, there's a designer. 18:14.000 --> 18:18.000 I'm like, think we can clear up some redundancy and make some things easier. 18:18.000 --> 18:20.000 So I think we're making good progress there. 18:20.000 --> 18:22.000 Yeah, so slowly bringing people along. 18:22.000 --> 18:27.000 We have, I mean, down at the table, we've had so many people thanking us for the changes that we've made. 18:27.000 --> 18:29.000 So yeah, yeah, yeah. 18:29.000 --> 18:34.000 And then, you know, being able to, in your context to be able to, you know, 18:34.000 --> 18:39.000 check your email's on desktop, organize yourself, calendar tasks, those kinds of things coming. 18:39.000 --> 18:43.000 And then be able to move into your mobile phone wherever you are to check them as well, 18:43.000 --> 18:46.000 and have it all work the same as a bonus. 18:46.000 --> 18:48.000 So yeah, can I answer it? 18:48.000 --> 18:49.000 Yeah? Okay. 18:49.000 --> 18:51.000 Anyone else? 18:53.000 --> 18:54.000 Oh, yes. 18:55.000 --> 18:59.000 So I'm a user-excuse designer that works for the design system. 18:59.000 --> 19:05.000 And one of the problems that I encounter sometimes the design system is too rigid. 19:05.000 --> 19:10.000 As well, design, when future use case that was not up here, 19:10.000 --> 19:12.000 when it's first three times. 19:12.000 --> 19:16.000 So how would you make sure that the design system is scalable to future problems? 19:16.000 --> 19:19.000 Well, we don't know ever know what's coming in the future. 19:19.000 --> 19:20.000 Oh, yes, sorry. 19:21.000 --> 19:23.000 I need that reminder, thank you. 19:23.000 --> 19:24.000 I promised I would do it too. 19:24.000 --> 19:28.000 So how do we ensure that a design system keeps adapting as we change, 19:28.000 --> 19:31.000 as our needs change, as the product changes? 19:31.000 --> 19:34.000 This is harder when you have a centralized team, 19:34.000 --> 19:36.000 or you want a centralized team? 19:36.000 --> 19:39.000 Yeah, so I've been in this before, 19:39.000 --> 19:42.000 where there's a disconnect between what's happening with the product, 19:42.000 --> 19:45.000 maybe even adjacent user research this happening, 19:45.000 --> 19:48.000 and then there's a whole system that feeds back in. 19:48.000 --> 19:52.000 So design systems need to evolve and change and grow. 19:52.000 --> 19:56.000 It's not something that you can build and set aside and say, 19:56.000 --> 19:58.000 here it is, just keep going and keep working. 19:58.000 --> 20:00.000 You know, we always have to come back and re-evaluate it. 20:00.000 --> 20:02.000 We need to bring key people from the teams together 20:02.000 --> 20:05.000 that are looking at it from all the different angles. 20:05.000 --> 20:08.000 And so it has to evolve, and then there's adoption. 20:08.000 --> 20:11.000 No matter how big your company is, 20:11.000 --> 20:13.000 I used to work with a team of 700. 20:13.000 --> 20:17.000 So yeah, sometimes it's like, what do you, why did you break? 20:17.000 --> 20:19.000 Why did you detach that component? 20:19.000 --> 20:20.000 Can we talk about that? 20:20.000 --> 20:21.000 What do you need? 20:21.000 --> 20:22.000 Why are you doing that? 20:22.000 --> 20:25.000 And sometimes it's sure the component needs to change, 20:25.000 --> 20:27.000 or there's something as a user experience designer, 20:27.000 --> 20:29.000 there's probably a different solve. 20:29.000 --> 20:32.000 So why did you disable the button? 20:32.000 --> 20:37.000 So yeah, yeah, so allow for change and allow for flexibility. 20:37.000 --> 20:40.000 And actually the other thing to that point is, 20:40.000 --> 20:43.000 now having your design system so big that you can move it, 20:43.000 --> 20:44.000 right? 20:44.000 --> 20:46.000 It should stay simple, it should be the reusable things. 20:46.000 --> 20:49.000 Sometimes we end up with things in there that maybe we're not using, 20:49.000 --> 20:51.000 or have a one-time use, and it's like, 20:51.000 --> 20:53.000 should this be in the global design system, 20:53.000 --> 20:54.000 or does it need to live somewhere else? 20:54.000 --> 20:59.000 So keep it small, yeah, agile, yeah. 20:59.000 --> 21:01.000 Anyone else? 21:01.000 --> 21:02.000 Oh, yes. 21:02.000 --> 21:04.000 You talk about this new world. 21:04.000 --> 21:05.000 You. 21:05.000 --> 21:06.000 You come over here. 21:06.000 --> 21:08.000 Oh, this rocks land. 21:08.000 --> 21:09.000 You talk about this new group. 21:09.000 --> 21:10.000 You come over here. 21:10.000 --> 21:11.000 When you have. 21:11.000 --> 21:12.000 Oh, great. 21:12.000 --> 21:13.000 Oh, good. 21:13.000 --> 21:14.000 The group, the cards view. 21:14.000 --> 21:16.000 The cards view that we're looking at in the face? 21:16.000 --> 21:17.000 Yes. 21:17.000 --> 21:20.000 The issue where the oldest medicine is filmed, 21:20.000 --> 21:23.000 and you have to photo it out to see the newest medicine. 21:23.000 --> 21:24.000 Yes. 21:24.000 --> 21:29.000 So sometimes I actually forgot to see a medicine at home 21:29.000 --> 21:31.000 because this is an old medicine film. 21:31.000 --> 21:32.000 Yeah. 21:32.000 --> 21:33.000 Yeah, totally. 21:33.000 --> 21:35.000 And then, yeah. 21:35.000 --> 21:37.000 So the question is that in our threaded, 21:37.000 --> 21:39.000 when you're looking at your emails, 21:39.000 --> 21:41.000 so it's a threaded conversation view, 21:41.000 --> 21:42.000 and it shows the oldest one, 21:42.000 --> 21:44.000 and you have to open it to see the most recent one. 21:44.000 --> 21:46.000 I experienced this daily too. 21:46.000 --> 21:47.000 We're working on that. 21:47.000 --> 21:48.000 Yeah. 21:48.000 --> 21:52.000 Well, you'll see some customization and some improvements 21:52.000 --> 21:54.000 to threaded view for sure. 21:54.000 --> 21:55.000 Yeah. 21:55.000 --> 21:59.000 You'll be able to do a sending or descending for sure. 21:59.000 --> 22:01.000 Yeah, and there's a button that says, hey, 22:01.000 --> 22:04.000 there's some little visual cues like something's new. 22:04.000 --> 22:05.000 There's a star. 22:05.000 --> 22:06.000 You know, the button turns blue, 22:06.000 --> 22:08.000 and you know that there's some other ones. 22:08.000 --> 22:09.000 They're kind of hard to see, 22:09.000 --> 22:11.000 but yeah, you want to really be alerted. 22:12.000 --> 22:14.000 That, you know, we don't want you to miss your emails, 22:14.000 --> 22:15.000 and the most important, 22:15.000 --> 22:17.000 especially over apply, right? 22:17.000 --> 22:19.000 So we've been working on that. 22:19.000 --> 22:20.000 There's some things coming soon. 22:20.000 --> 22:23.000 So make sure you update and follow along. 22:23.000 --> 22:24.000 Please. 22:24.000 --> 22:25.000 Yeah. 22:25.000 --> 22:26.000 Thank you. 22:26.000 --> 22:27.000 Thank you. 22:27.000 --> 22:29.000 Do you want to really want to ask questions? 22:29.000 --> 22:30.000 Anyone else? 22:30.000 --> 22:31.000 Yeah. 22:31.000 --> 22:32.000 Anyone else? 22:32.000 --> 22:33.000 Yeah. 22:33.000 --> 22:35.000 Did anyone ask about the, 22:35.000 --> 22:37.000 I think source design processes that 22:38.000 --> 22:40.000 can you give us these folders or like, 22:40.000 --> 22:43.000 little weeks and things that you've got found? 22:43.000 --> 22:44.000 Well, yeah. 22:44.000 --> 22:46.000 So any open source design you want to contribute. 22:46.000 --> 22:47.000 I want you to contribute. 22:47.000 --> 22:48.000 I don't want to just see code. 22:48.000 --> 22:50.000 I would love for someone to say, 22:50.000 --> 22:52.000 hey, I was looking at this and like give me a visual, 22:52.000 --> 22:54.000 you know, sketch. 22:54.000 --> 22:56.000 Let's not, I love napkins sketches. 22:56.000 --> 22:57.000 If you send me a napkins sketch, 22:57.000 --> 22:59.000 I will not be hurt. 22:59.000 --> 23:00.000 I love them. 23:00.000 --> 23:02.000 Yeah. 23:02.000 --> 23:03.000 Good question. 23:03.000 --> 23:06.000 It's a little loose for design contribution right now. 23:07.000 --> 23:09.000 Like I'm up to suggestions. 23:09.000 --> 23:10.000 What works back. 23:10.000 --> 23:13.000 Currently, I've been just showing things on topic box 23:13.000 --> 23:14.000 and our community. 23:14.000 --> 23:16.000 So you'll see things there. 23:16.000 --> 23:18.000 We're going to, in our blog, 23:18.000 --> 23:20.000 we'll be talking a little bit more design. 23:20.000 --> 23:22.000 I'm open to anyone just emailing me. 23:22.000 --> 23:23.000 That sounds scary. 23:23.000 --> 23:24.000 Yeah. 23:24.000 --> 23:28.000 And once we get these component files out in community 23:28.000 --> 23:31.000 and figman, pen pot, like start working with them 23:31.000 --> 23:34.000 and, you know, we'll figure out where to post them. 23:34.000 --> 23:36.000 Normally, we just have the dev channels that we have right now, 23:36.000 --> 23:37.000 so in a normal things, 23:37.000 --> 23:39.000 but I don't want that to be a barrier. 23:39.000 --> 23:41.000 So what am I saying? 23:41.000 --> 23:42.000 Stay tuned. 23:42.000 --> 23:43.000 It's coming. 23:43.000 --> 23:44.000 Let's talk. 23:44.000 --> 23:45.000 Let's make it work. 23:45.000 --> 23:47.000 If you have an idea, I want to hear it. 23:47.000 --> 23:48.000 Yeah. 23:48.000 --> 23:49.000 Cool. 23:49.000 --> 23:50.000 Thank you all. 23:50.000 --> 23:52.000 Thank you.