Launching a product? Building UI? Designing an app? Iconshelf has icons for every step of your workflow 💡 Visit → iconshelf.com #Startups #BuildInPublic #UIUX #DesignLibrary

How to reverse-engineer private binaries using MachOSwiftSection 🛠 The open-source MachOSwiftSection tool by MxIris is the key to reverse-engineering the interfaces from these binaries. I downloaded the tool from the swift-interface branch, and ran the build script. The documentation is super clear (screenshot #1). Let’s give this a try, and dump AlarmKit (screenshot #2). Wow, it straight up just dumped the entire interface of AlarmKit. First try. That’s unbelievable. We can get the slightly neater, Tweetable version by outputting the interface to a .swift file: ./swift-section/Products/swift-section interface --output-path AlarmKit.swift /Library/Developer/CoreSimulator/Volumes/iOS_23A343/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS\ 26.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/AlarmKit.framework/AlarmKit This outputs a proper Swift interface containing all the internal Swift types (screenshot #3). How does this tool work? It walks the __swift5_* metadata sections in the Mach-O binary and reads ABI-defined descriptors in the binary to resolve types, protocols, and conformances. It runs a custom demangler to decode the resulting symbol names to reconstruct a regular Swift-y interface. This works because the Swift ABI exactly specifies the structure and memory layout of these object code descriptors, for example, a ProtocolDescriptor always follows the exact same format when compiled into binary. By running the tool on the DesignLibrary private framework, we can spot the original Liquid Glass configuration that inspired this article (screenshot #4). I thought going through this exercise would make it seem less magic, but frankly I’m more convinced than ever that he’s a god. Let me be clear: this does not reverse-engineer the actual source code from the binary, it just reconstructs the interface using type metadata. But this alone still gives us a ton of fascinating info. ./swift-section/Products/swift-section interface dump /Library/Developer/CoreSimulator/Volumes/iOS_23A343/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS\ 26.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/AlarmKit.framework/AlarmKit Join my blog for free and master iOS with 10 minutes a week 🚀 join.jacobstechtavern.com

Probably some are in SwiftUI, while others are based on the new rendering system they use for many components—I mean RenderBox, of course. As far as I know, LiquidGlass isn’t related to RenderBox; it uses a QuartzCore DesignLibrary combo.

It doesn't. Let's take an NSButton. When your app wants one: - AppKit places an NSHostingView into the view hierarchy - AppKit asks DesignLibrary to provide the SwiftUI view of the button - the hosting view (AppKit) lays out that SwiftUI view An analogy I can think of is like SwiftUI being a universal scripting language that AppKit and UIKit can interpret. SwiftUI has its own processing, but the actual final output will be drawn by AppKit. The design team could change around the controls in DesignLibrary.framework separately, without interfacing with AppKit or UIKit directly.

It's probably a mess overall right now, but this seems like an effort at reducing work as it evolves. Until now, when they introduced or redesigned a control, I imagine they had to make and match the UI in all of the frameworks. If they would use SwiftUI for controls, they could have one shared framework with UIs ready to go (DesignLibrary), and they would only have to worry about the logic and API of the control itself into AppKit, UIKit, TVUIKit etc..

Bonus fun fact: This concept may have started out on visionOS. The "design library" for visionOS is StopwatchSupport.framework. Much like DesignLibrary.framework in 26, it also contains a bunch of design-related code for the visionOS visual style specifically, some extra visionOS-specific controls. They're so similar, even the source code file name references and control structs their properties are named identically. It also has a bunch of SwiftUI exports, just like DesignLibrary. visionOS uses UIKit, but it also has an extra library (libMRUIKitSupport.dylib), which, as part of initialization, applies the visionOS visual style. When libMRUIKitSupport.dylib is present, during initialization of apps, it calls out to StopwatchSupport's SWSApplyVisualStyles function. As part of this style application, it modifies and replaces UIKit controls and their styles at runtime. I can't exactly tell, but it also looks like some (less) of the controls end up being hosted through SwiftUI. All of this reminds me of a WWDC quote that said ~"we strongly recommend you use SwiftUI for visionOS" or something along those lines. :)

I already had the feeling something like this was going on much earlier, but I stopped thinking about it when I saw the UIKit hierarchy with no mentions of SwiftUI. After looking at it again now, looks like there was something to it after all. DesignLibrary.framework is: - cross-platform (as in, exists on macOS, iOS, visionOS, tvOS...) - directly contains Solarium (Liquid Glass) parts, including glass properties and definitions - is written entirely in Swift - doesn't import AppKit or UIKit - has no AppKit/UIKit-specific code, only ones specific to platform The DesignLibrary framework also exports a bunch of symbols that have the signature SwiftUI function name mangling. These could be the SwiftUI views that macOS AppKit ends up hosting, but they may also be generally used by SwiftUI as well. It would be interesting to see whether UIKit also hosts SwiftUI with some controls.

More technical details: Solarium controls have their own structs in DesignLibrary, so UIKit/AppKit/SwiftUI probably make use of these to represent the controls. AppKit seems to resort to hosting the visuals of some control views with SwiftUI entirely. UIKit looks like it actually draws the controls on its own and makes use of these specifications from DesignLibrary under the hood, as it even has proxy structs for at least switches and steppers controls. These control structs make use of SwiftUI.Environment heavily, and the stack traces in the previous post also show it being accessed in a pure UIKit app. I wonder if they're actually using SwiftUI here, or just hacking it to work with UIKit🤔 Seems like they put much more effort into UIKit generally.

🌐 DesignLibrary .com 💰 Sold Price : $19,888 ✔ @DNRater Recommended BIN : $18,801 ✔ Godaddy Estimation : $4,887 ✔ Estibot Valuation : $1,100 ✔ InternetX Appraisal : $597 📌 Venue : @Sedo 📆 2025-08-02

Finally... I found the magic hand that sold designlibrary•com for 5 figure. This man is something else when it comes to the world of domaining. I remember listening to him on DNW podcast when his portfolio was 10K . Great people exist in this industry.

Stunning 18th century heraldic silk damask woven with thread of gold. As a result this piece is very weighty and forms part of the original archive collected by Reginald Warner on his Grand Tour of Europe. #gainsboroughweaving #historicaltextiles #archive #designlibrary

And the actual color information is stored at /System/Library/PrivateFrameworks/CoreUI.framework/Resources/DesignLibrary-macOS.bundle/Contents/Resources/macOSRepositories

🚨 Officially moving to Austin this summer, ISO of a cool office space to build the studio/designlibrary

Created Fully Adaptable Typography System in @figma for my upcoming Product. 👉 Join The Waitlist: docs.google.com/forms/d/1nW9… #uidesign #figma #designsystem #designlibrary #figmadesign #digitalproduct

멋진 책방 3. 디자인 책들이 진열된, 디자인된 인테리어가 인상적인, 디자이너들에게 특히 영감을 줄 공간.😅 이 책방은 한옥과 마당과도 어우러져 상당히 로맨틱하당.👍 #서울 #북촌 #현대카드 #DesignLibrary

We're thrilled to announce our brand new Figma Design Library for WindUI! 🎉 Your favorite library is now integrated with Figma, allowing you to design & develop effortlessly! buff.ly/44rN0Jh Looking forward to your feedback!👀 #tailwind #figma #windUI #designlibrary

💥Design Library Mumbai COMING SOON!💥 Indulge in the opulence of Indian couture, as Design Library Mumbai unveils a tapestry of luxury crafted by the India’s top designers. ✨ @HiLifeExhib Plan your visit and embrace the touch of royalty with ornate Jewellery and artistic Accessories.💫 📅Date (s): March 9th & 10th 📍Venue: Four Seasons, Worli, #Mumbai ⏲️Time: 10 AM - 8 PM #designlibrary #designlibrarymumbai #mumbaievents #designercouture #accessories #fourseasons #celebrity #fashionista #jewellery #diamondjewellery #highfashion #mumbai #mumbaitodo #mumbaiwishlist #shopping #shoppingfest #Ragalahari

Latest Drops on Appshots Hello Designers, This week, we've curated a collection of 1000 super sleek, fully tagged iOS screens from NeckGo, @CashApp, Buddy, @Mindllama, and @ShopCider. Check them out now! #Appshots #designinspo #DesignLibrary

Navigating the world of UI design with ease, thanks to my trusty UI reference library! 🎨✨ #UIDesign #DesignInspiration #UIReference #DesignLibrary #CreativeToolkit #DigitalDesign #UserInterface #UXDesign #InspirationStation #DesignResources #UIUX #DesignersToolbox

Latest Drops on Appshots Hello Designers, This week, we've curated a collection of 1000 super sleek, fully tagged iOS screens from MORE, @Lemon8, @Tripadvisor , @structured_app , and @Walmart . Check them out now! #Appshots #designinspo #designthinking #DesignLibrary