I have a question about how to use Adobe XD to maintain a large, versioned UI kit that changes over time, within a "walled garden" environment.
Here's some background about our specific environment that will help you understand the context for my question:
We're looking at using Adobe XD for designers to create high-fidelity prototypes that emulate the appearance of these software components. (I'm relatively new to managing this team and am adding support for designers that has never been implemented in the past.) We're new to Adobe XD and we really like what we're seeing so far.
I see that we can create a UI kit with component assets in XD that mirror our software components, that designers can then use in Adobe XD to create prototypes specific to their product. But I'm concerned with how this UI kit will be able to evolve over time to reflect changes to the software components that it mirrors: namely, additions of new components and changes to existing component visuals. I can't seem to find a strategy that will work for this.
So… are any of my assumptions above wrong? If not, do you have any suggestions for how we can accomplish what we need, given the following constraints?
Thank you very much in advance. All feedback is welcome!
Copy link to clipboard
Hi Jim -
I'm a Product Manager on the Adobe XD team primarily focused on Design Systems and would definitely love to help you out.
Thanks a lot for reaching out for explaining how you want to create, share and evolve UI Kit. As you mentioned there are multiple ways each with known limitations that we're working on addressing.
Do you mind me scheduling a call with you to dig deeper into your flow so that I could recommend the best path forward?
Hi Sherif, yes that would be great. We would really appreciate that.
Also Sherif, this is my first post here, so please let me know if I need to initiate that contact or if you'll be contacting me at the email address in my account. Thank you!