Conceptboard is a collaboration software built for teams of any size. Its primary features are project management, team whiteboards, integration into business workflows, and real-time collaboration.
N/A
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.
I like ConceptBoard better than Miro. Miro also offers a similar virtual "whiteboard" but Conceptboard has a better UX and is easier (and more fun) to use.
I've used Figma extensively, and still do, for UX planning and design but have moved away from them for brainstorming. Figma…
Well suited - 1. Whiteboarding, brainstorming, designing, workshops, etc. 2. Templates - Pretty good repository of ready-to-use templates esp for project management, agile, etc. Less appropriate - 1. Anything that requires integration with existing enterprising software - limitations like no integration with Jira, Asana, etc. 2. Embedding anything related to images, videos, etc. The embed is not very smooth, it lags, and sometimes straight out doesn't work 3. Image search - Many competitors provide this feature and hence Conceptboard lacks here
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.
Great user interface that's very intuitive and easy to use. This is an important aspect of collaboration, brainstorming sessions often involve a lot of people coming from different functions who may not be too familiar with these tools
Allows users to see real-time changes and actions done by others from sticky notes/comments down to their cursor movements
Lets users add/attach files and annotate/comment on each directly on the board which skips the hassle of having to look at files using different programs/platforms and referencing on the board
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.
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.
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.
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.
Miro is a superior product with more capabilities and better suited for advanced users. We selected Conceptboard as a short-term solution that was low-cost compared to Miro but allowed users to create boards. Once users are versed in Conceptboard, they are better off using Miro which has more integration, better capabilities, and is overall a more complete product.
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!
I can say that this tool is unique since its impact on our work team has been one of the best we have ever had since it allows us to exchange ideas in one place through boards, which is more fun with the video call function
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.
