Member-only story
The UX design world (and beyond) is buzzing with Adobe’s looming acquisition of Figma, and for most Figma users, it has not been a good buzzing — more like Yellowjackets after you stepped on a hive. But let’s take a deep breath and take a look at some possible positives.
It remains to be seen how autonomous Figma remains, but historically once the ink has dried on the deal, true autonomy is rare for the purchased party. Many articles have been written about Adobe desiccating great products after they buy companies. So the jury is still way out on the future of Figma.
“…Until the transaction closes, each company will continue to operate independently.” https://uxdesign.cc/adobe-is-buying-figma-what-does-that-mean-for-you-ab6cdd2a8c4b
So let’s pretend that all goes well, and Figma just tapped into Adobe’s resources without being purchased. How can they improve their product and community using Adobe’s money and resources?
Figma has an easier path to adoption.
Large companies and enterprises have very complex security and procurement processes, so any company that has an Adobe service agreement in place could easily provide their employees a Figma editor seat. In some cases it can take a year or two to navigate the security requirements and service agreement complexities…
