Use whatever tool you prefer, of course, but there are a few underlying assumptions here that I believe are erroneous. Assumption #1: Design documents are cont

Use whatever tool you prefer, of course, but there are a few underlying assumptions here that I believe are erroneous. Assumption #1: Design documents are contained in a file, and that file should be portable. Tools like Figma are closer in nature to SaaS products than they are to native, file-based, raster editing softwares like Photoshop. You don't expect to be able to export your Slack workspace into a file and import it into another tool. You expect to have a means of migrating that data, potentially by exporting that data into a common format (e.g. JSON, CSV), transforming it into a format compatible with the target, and then either importing it using a provided tool or an API. Assumption #2: Design tools all work similarly enough that document structures are largely portable. While UI modalities remain similar enough on the surface, the underlying capabilities that produce the visual are exceedingly different. Look at type, for example—even Sketch and Figma, which are similar conceptually and of the same era, render type so differently that even robust import/migrate tools fail to capture the position of text within a few pixels for even basic, single-line, single-style text. Notions of seamlessly switching between tools disregards the real-world complexity of fonts, color profiles, raster manipulations, version history, comments, plugin-generated metadata, symbols/components, and more. Assumption #3: There's no way to export a Figma document. You can get the entire document structure from Figma via the API. This is the same data the viewer uses to render the document. You do not need to understand the internals of the .fig files.