{"id":17587,"date":"2019-04-24T10:15:39","date_gmt":"2019-04-24T09:15:39","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=17587"},"modified":"2020-08-27T15:51:54","modified_gmt":"2020-08-27T14:51:54","slug":"integrating-abstract-marvel-create-master-prototype","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/integrating-abstract-marvel-create-master-prototype\/","title":{"rendered":"Integrating Abstract and Marvel to Create a Master Prototype"},"content":{"rendered":"

Last year we launched the Marvel API<\/a>, a new way to build customised workflows, integrations and apps that utilise the designs, users and data on Marvel.<\/p>\n

It led to some brilliant integrations like SmartMockups, Maze and Microsoft Teams<\/a>. We also kicked off Marvel Labs, an internal skunkworks where we experiment with small apps and ideas like Userflows<\/a> and Dashboard <\/a>.<\/p>\n

Being able to quickly spin up these integrations and custom workflows has been massively empowering for the team. In the era of DesignOps, we're constantly searching for ways to bring greater efficiency, productivity and customisation to the design process.<\/p>\n

We\u2019ve recently adopted the awesome Abstract<\/a> into our tools and started to think about ways to integrate it deeper into Marvel.<\/p>\n

If you haven't heard of Abstract, it works as version control for Sketch, allowing designers to work in similar way to how developers work on Github (Master files, branches, push, pull, merge etc<\/a>).<\/p>\n

Designers can upload their Sketch file (Master file) and allow other designers to create multiple versions from it (Branches). Once they are happy, the designer can request to 'merge' their iteration into the Master file.<\/p>\n

This process prevents any unwanted changes and corruption of design files. Whilst at the same time, giving designers the flexibility to experiment and dabble within their own branch, without messing with the Master file and overwriting it by mistake.<\/p>\n