Home to all the amazing content generated by the Friends of Figma, Portugal community. Here, you will find talks, workshops, live streams, conversations, and much more. Subscribe to get the best content on your inbox.
This was such a shitting on apple docs session. Aside from the only guy there who understood the point of docs. It’s not a marketing page for designers.
Guys. You NEEED TO FOCUS ON HOW ALL PLATFORMS ARE AFFECTED! Jesus Christ. Please do not build apps with only one platform in mind. Mac is an ecosystem. Your “watch” alerts are also being airplayed across all devices instantly. That’s why they actually show them side by side. So you’re not designing in a vacuum. Also you’re telling people “no one reads the docs.” So wtf is the point of the entire video? This feels like a pointless complaining session about text rather than the actual value of the content. This isn’t a UX critique on their docs layout.
The size is not actually different. They use the same resolution per eye distance for lean back and lean forward devices. The interaction is but sizing is identical because they control hardware line. Find me one element that doesn’t work perfectly on both Mac and iOS when supported.
00:00:00 - Designers Andric, Marcelo, and Bruno introduce themselves, discuss upcoming design conferences, and explore Gitlab's design system "Pajamas," sharing anecdotes and inviting feedback. 00:10:00 - Impressions of Gitlab's design system documentation website, emphasizing collaboration, contribution, and user-friendly features. 00:20:00 - Further impressions of Gitlab's design system, including consistency, transparency, and usability for both internal and external users. 00:30:00 - Overview of Gitlab's design system components, documentation, and features like annotations in Figma and deprecation process. 00:40:00 - Discussion on updating deprecated components, evaluating ease of use, and structure, with a focus on component management. 00:50:00 - Debate over documenting design components in Figma vs. external tools like Storybook, and experiences with design platforms. 01:00:00 - Tips on naming and organizing design system components, technical difficulties, and audience participation. 01:10:00 - Further exploration of design system components, including color-coding and customization of buttons, with comparisons to other design libraries. 01:15:00 - Discussion on the importance of design systems for consistency and shared language between designers and developers, promoting upcoming events.
Hi, 8:30 would be cool if you put such links also in the description/comments sections (sadly there's no chat remaining here, if you streamed in youtube of course)
Thank you so much for the amazing breakdown of the apple HI , and to be honest if it wasn't for this video I always found it hard to digest what they have on that website , it's not clear from where should I start anyway , their design website reminds me of the patterns used on Japanese website where you are presented with everything at once , which is overwhelming .
@@fof_portugal to be honest one of the challenges I do face while creating design systems , is deciding what tokens I need , I'm not sure if my question makes any sense , but technically each major design system has its own guidelines about this matter. and while I kinda was able to create tokens for my own design system by reverse engineering and going through a couple of design systems like fluent design I still want a video explaining how to determine them for future projects and thank you in advance .
@@hamzasadouk4741 start from small find a simpliest component and create color tokens for it, try sync it with your dev team. Once you'll sync it you'll have a better idea for the next component
@@ui_uxdesigner1440 Thank you so much for the advice, I was able to figure out some stuff by analyzing already existing systems , the only issue is that I'm guilty of '' compulsive tokens creation'' LOL
Interesting to see how different people tackle the building part 😊 My auto-layout nerd mind was kinda nagging me that using it would have saved a lot of time here 😅
