Confluence vs Figma

• QUICK How-to Guides that can be generated and share instantly
• One can subscribe to the pages and spaces and receive updates in the feed on their home page
• Automatic Email notifications of new updates in the Confluence area
• The platform integrates easily with other Atlassian platforms including third-party apps thus improving its reliability

Read full review

• Collaboration! we stopped sharing screen in zoom, now we all jump into Figma and magically everything connects and flow way better.
• Memory management! Figma manage all the assets so well, that we sometimes have all project assets in one single file with multiple pages and it loads instantly. Keeping everything in one place, easy to access and to developers or designers complain about they stations running out of ram!
• Sharing!, getting a link to an exact pixel is magical, discussion can now have way more context than what it had before.
• Auto-layouts! Although is not new in the ecosystem, Figma does a pretty awesome job with molecules and particles, so you can create better design systems that can stretch to any screen, making it a design once for all devices!

Read full review

• Some of the components can be a little clunky to use and configure on pages.
• I've run into a few issues where edited pages refuse to publish and work is either lost or time wasted copying and pasting to a new document that will publish.

Read full review

• Some of the auto-layout features seem to have bugs every so often.
• The account management between different Figma spaces doesn't seem super intuitive.
• When navigating to the same work space on different devices, the file name view is not remembered (as that may be a device-specific preference that is not tied to an account preference).

Read full review

• We've gone from folders and folders of Word documents and PDFs into a single system with a search feature to bring all of our data together and trackable
• While onboarding took a bit longer for the company (to switch from a Word document centric mindset - to a web-based one), overall the company has embraced the features and power of Confluence within the working stack
• However, as costs continue to climb for the Atlassian product, we are forced to continue our evaluation of the product - with replacing it a remote possibility if it begins to outprice its usefulness to us.

Read full review

• Lots of saved time and energy by being able to have feedback loops in the same program that stores the designs. We don’t have to use multiple programs to have a conversation about a single design.
• Being able to have feedback loops within the program also saves on subscriptions to programs designed to solicit feedback, such as Zeplin or InVision.
• It took significant time to onboard designers who were primarily familiar with the interface of Adobe programs to Figma. Because we primarily use Adobe programs, this took a lot of time that we could have spent creating and iterating.

Read full review