How LEGO can inspire us to build better UI Libraries
summary
GetYourGuide moves an FAQ into a generics-based accordion component written in SwiftUI so the same element migrates across screens; code switches from concrete text+chevron to header/body generics, reducing duplicated rigid components. Team of ~10 iOS engineers finds an accessibility bug (header exposed as static text because of onTapGesture) and fixes it by using Button; RTL issues get caught with an RTL preview modifier and icons flipped via XCAssets. Snapshot tests run with snapshot testing via Points Free, adding ~20–30% dev time but yielding reusable, testable library components that work.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:17From pirate ship to LEGO mindset
- 7:13Composition as LEGO blocks
- 11:12Reusable building blocks
- 12:19Localization in UI libraries
- 14:03Accessibility first
- 17:36Documentation and naming
- 18:40Testing UI components
- 20:03Moral and summary
related talks
34mPlaying Nice with UX and QA
38mAccessibility That Engineers Actually Love to Build ❤️
31mNo Bad Legos: A Toy Box For Everybody
27mBuilding a Maintainable UI with Storybook
18mMaking the Things That Help Others Do Their Thing
25mThe Lego Approach: Leveraging Reusability for a Seamless...
35mHabits for building a scalable UI
37mLet your design evolve, adopt a Design System!