Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$10
per month
Figma
Score 9.1 out of 10
N/A
Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
For a larger organization Atlassian Confluence is the best tool we used. We found that since we were a smaller organization it wasn't worth it for us as much as using Google Drive and keeping on top of it. We ended up going back to using Google Drive but only because we …
Figma has more features than Zeplin or Axure. Unlike Zeplin it allows to create and share dynamic prototypes. Unlike Axure it gives tools to create detailed designs.
We migrated from Sketch to Figma and appreciated the design system when selecting Figma. We also liked the increased collaboration it would enable. We've found both to be incredibly helpful in practice and are very happy with our decision. Figma is intuitive and committed to …
I will be specific here - With Adobe XD it was very difficult to prototype, it was also very complicated to learn. With Sketch - We had to use InVision for prototype and share and there were limited feature were available compared to Figma.
I was not the one who selected Figma and it is certainly missing some features of photoshop that I'd like to have but its a great all in one software for design and collaboration and its very easy to learn and get new members on board.
The detailing and extent of designs that are possible in Figma are unparalleled. Screen mirroring is one of the most used features as the others do not offer this. In terms of load time, responsiveness, lag etc. there is a marginal improvement. Figma works better even when the …
I've been using Figma for the past 4 years so I'm not on top of the most recent versions of the other tools but we chose Figma as it allowed our distributed team of designers who are not just in different cities but different regions and timezones to collaborate better and stay …
ChatGPTFigma surpasses Miro by offering a comprehensive design experience, allowing not only collaborative brainstorming but also the creation of realistic wireframes and prototypes. Its design-centric approach enhances visual representation, making Figma a versatile tool that …
Figma blows their competition out of the water. Clearly #1 for me.
Sketch was too slow to get to the cloud even thought they were doing some really awesome things. They also didn't figure out collaboration, version control, and PC/Mac …
It has a comment option on the page, where you can tag other teammates tagging them. it sends the mail notification. Comment at the page end is pretty good for referring to other stakeholders and future references of the topic on the page. Creating the highlights of the discussions, and meeting held points with highlighted tagging. Easy shortcuts such as to add a date just type "//". The interface is cool and has easy shortcuts for quick page making.
Figma is very well suited for software design. I've used it for several years for all kinds of apps, from small companies to multinational corporations. The infinite whiteboard is fantastic and provides the free workspace I need, just like having a big design studio in real life. The ability to collaborate in real-time with other team members is great and enhances communication tremendously. Conversely, Figma is not great at doing jobs in print or anything that you would normally do in Photoshop or Illustrator. And that's fine. Those apps are made for a different purpose than Figma.
Navigation. Similar to other Atlassian products, users have complained that aspects of Confluence are difficult to learn right away[.]
An issue that users can face when using Confluence is attempting to edit a document while someone else is editing. Although users can access the document and save it, they are unable to see the changes happening in [real-time] that other users are implementing until they refresh their page. Some users have also noted that this can result in loss of edits.
Another drawback of using Confluence is its specific organizational structure. All information is stored within one page or project, although the page is able to be broken up into sections, some users do not prefer this style. Users can use the ‘page tree’ on each page to organize the different elements of each project.
Tappable overlaid layers - bugs on fixed components, such as an app navigation footer in a prototype
Swapping a component but retaining inputted copy or imagery.
Performance on prototypes to work better in UserZoom - having to delete hidden layers manually, optimize images, and streamline the file, in general, is time-consuming
Folder structures - larger teams need multiple layers of folder structure to help find things.
Branch performance - we need better, more user-friendly solutions to get designs to merge better.
Branch performance - branching with the option to choose which pages you want in the branch without deleting each page you don't need.
Default sharing options need improvement.
Responsive ratios' in prototyping without having to recreate pages.
Better collaboration with Jira to bring in links in the design mode not just dev mode.
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
Figma is a pretty cool tool in many areas. My team almost uses it on daily basis, such as, brainstorming on product/design topics, discussing prototypes created by designers. We even use it for retrospectives, which is super convenient and naturally keeps records of what the team discusses every month. Furthermore, I do see the potential of the product - currently we mainly use it for design topics, but it seems it is also a good fit for tech diagrams, which we probably will explore further in the future.
Confluence can - and in my personal opinion, it will - be a bit hard to use in the first moment. Atlassian is a great company and is eager to help you with any question you have, though. The interface seems to be a bit clumsy at first but the customization options are enough to make it easier and simpler. In general, Confluence is easy to use when you understand what each section does, but this can take a while.
It's so simple to use! I have no background in UI design but basic designing and I was able to learn this software Figma within 3-5 days. There are tons of tutorials available on Youtube from so many popular YouTubers in the space, you can just go through them and start designing.
Pages load very quickly, which makes it useful for quickly obtaining information. The search functionality is also very quick and is able to parse through all of the documents to provide the most relevant results for the query. Other information based software gets bogged down, but so far Atlassian Confluence maintains its performance.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
I haven't used their support lately but in the past, they had a chat that I used often. They often responded in a few hours and were able to give a satisfactory solution. I would imagine it's less personal now but the community has expanded drastically so there are more resources out there to self serve with a bit of Google magic.
In-person training has its own benefits - 1. It helps in resolving queries then and there during the training. 2. I find classroom or in-person training more interactive. 3. Classroom or in-person training could be more practical in nature where participants can have an hands on experience with tools and clarify their doubts with the trainer.
Online training has its own merits and demerits - 1. Sometimes we may face issues with connectivity or the training content 2. The way training is being delivered becomes very important because not everyone is comfortable taking online training and learning by themselves. 3. With the advancement of technology online training has become popular but there is a segment of people who still prefer class-room training over online one.
We used to use Google Drive to store all of our documentation, but it is disconnected from our every day working environment and it was easy to lose documents and become disorganized within the broad drive environment. [Atlassian] Confluence has kept us more organized and its tight coupling with Jira has made documents more accessible and more likely to be kept up to date.
Figma blows these out the park. Adobe's system is very different, and I think this shows in their attempted acquisition of Figma. I've not used Sketch or Invision, but their lack of market presence says a lot—designers like using the best tools. Axure is definitely more comprehensive in prototype testing but very hard to adapt to use—the hotkeys aren't even the same!
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.
Seamless integration of designs into Jira have helped double the level of accuracy during development. Interactive access to preview prototypes, flows and mockups has made a huge difference for us.
When components are updated in ways that changes the copy or architecture, it breaks all of its instances creating a massive source of anxiety for everyone on the team. The fact that we are uncertain whether our updates will retain text overrides forces us to triple check each time, decreasing our operational efficiency.
When high-fidelity prototypes are built to showcase new concepts, their ability to appear almost identical to our production site makes it much easier for stakeholders to get involved in decision making therefore allowing us to make more well rounded decisions.
