Abstract can be super powerful and can replace Zeplin entirely but, also in my case, it's usually just me or maybe 2 designers in total collab-ing in a single abstract project.

It'd be super nice If I can ditch Abstract altogether for native sketch version controlling.

Mattew O'Connor, I'm pretty certain Dexter W is referring to the standard 'git workflow'. Just google the last two words.

Interestingly seldom us designers will follow that or any standardized branching format and we'll just create branches and sub-branches as we seem fit. We usually wing it in Abstract, don't we?

Hi Matthew, somehow I had missed this message. My flow works like this:

I work closely with product managers and designers to iterate different designs through commits. Exploratory work stays in that phase. We work in short iterative cycles.

Developers and other stakeholders who are mainly focused on the deliverables are only are trained to look at Master designs for production work, which means they don’t need to fuss with all our messy creative work behind the scenes in the commit cycle.

I have all my designs validated through the commit phase with the active stakeholders who shape the product, and then when we’re ready with designs that we have thought through, we push those changes to the Master file.

This is not the perfect workflow, but one I found works pretty well.