Anyone use extended collections to manage 1 design system for for web, iOS and Android?
My concern is that the file gets so big with all the component variations, but the alternate is having 3 different files.
My concern is that the file gets so big with all the component variations, but the alternate is having 3 different files.
I have a boatload of super dry Ash I inherited and want to make a dinner table. Like 12 boards that are 15' wide 6/4 and 10' long. Then 8 more that are 6ft long.
I love this design but don't want something to bash my kees on.
https://www.reddit.com/r/woodworking/comments/1og7uh6/does_the_lift_in_this_table_serve_any_utility/
What's some suggestions from woodworking on table designs?
Here's a version that provides more context and asks focused questions that are likely to get better responses from experienced design system practitioners:
I'm looking for advice from teams that maintain cross-platform design systems in Figma.
We're expanding from a web-only design system to support Web, iOS, and Android, and we're trying to decide on the right library architecture.
Our current thinking is:
I've run this through several AI tools, and they all converge on roughly the same recommendation, but I'm more interested in hearing from teams that have actually lived with this architecture.
A few questions:
I'm especially interested in hearing from enterprise teams maintaining large design systems across multiple platforms.
Got my 4 week reminder to this yolo who threw 315k into SpaceX at 211.
Now down 36%.
So:
Initial investment: $315,000
Current value: ≈ $202,000
Paper loss: ≈ $113,000 (about −35.9%)
As you were...
Has anyone ever built a chat bot that serves as your portfolio? Just load it up with markdown of your portfolio details and info about you and let it answer inquiries.
Science friction