Branching out of the UI-verse

Branching is such a great concept. Originating from continuous integration among developers, we started seeing it in design tools such as Abstract and Figma. <h1>Branching</h1> Here’s how branching works: There could be multiple designers working on a core flow. Rather than relying on autosave, branching allows each designer to safely work on new screens without making any alterations to the main or existing files. When ready, changes to the work can then be merged upon review. This can be very helpful if there is some maintenance to the design library or if a particular part of the flow is worth discussing, testing, or performing QA. All as an extension before merging back into the main stem. (For more information, check out <a href="https://www.figma.com/best-practices/branching-in-figma/" rel="noopener ugc nofollow" target="_blank">Figma’s documentation</a> on branching.) But that’s what we may want to hear as UX designers. As a way of working in the current product teams, we are accustomed to the language of our fellow developers. Yet the term “branch” holds a lot more meaning. <blockquote> To the anthropologist, a branch will mean a conceptual subdivision of a family, subject, or group of languages. To the manager of a large organization, a branch will mean a division or office of a large business or organization, operating locally or having a particular function. </blockquote> <a href="https://uxdesign.cc/branching-out-of-the-ui-verse-f34c0f2e6638">Visit Now</a>