Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$15
per month per editor
OpenText Vibe
Score 6.0 out of 10
N/A
OpenText Vibe (formerly Micro Focus Vibe) is a web-based team collaboration platform developed by Novell, and was initially released by Novell in June 2008 under the name of Novell Teaming. Novell's acquisition by Micro Focus was completed in April 2015.
A solo developer or small team that wants to integrate development, feature planning and ui design in a single app can find a lot of value in using Figma, since the FigJam whiteboard and UI editor are in the same app. Business plans and software features can be mapped out on FigJam and then implemented in the UI editor, that way there is reduced context switching and teams can operate smoothly without having to toggle between multiple apps.
I think Micro Focus Vibe is very well suited for organizations that work in a team collaboration front and have to share documents. I think this really shines in organizations that have a standard set of information that gets lost in the sauce because of the sheer amount of people in an organization. In this case, the Wiki is very helpful in this setting. I wouldn't quite recommend this site for video production houses unless you are patient enough to correlate your needs to the many many features available through Vibe...because it all boils down to patience.
As a visual designer, I spend 90% of my working time in Figma. So, as a design tool, Figma is mature and feature-rich. It covers all the basic needs and provides extras, such as simple prototyping and the ability to use external plugins.
Collaboration: It’s very easy to work together on the same file in Figma. You can easily brainstorm together or use Figma as a shared screen.
Smartness of components: Figma provides many adaptability options for components that allow building very flexible and scalable layouts.
Novell Vibe connects GroupWise mail with Vibe natively which means you can access Vibe from within the mail product.
Once forms and workflows are set up, the access structure on who sees what or not is very effective.
You can use Novell Vibe as your main intranet with everything from wiki's, blogging and more fully automated and still in synch with your internal organisational structure.
After playing with it for a while i found that through jsp it is highly configurable.
Access control - it wasn't apparent to me at first that a project was shared with everyone in the company vs just people i choose to share it with. I think the inverse should be the default.
Sometimes it struggles to import old sketch files - no clue how to make this better, but its frustrating
The most pressing improvement is in printing. In speaking with Novell techs Vibe was designed as a web tool, no paper necessary. However in the real world our folks love their paper printouts. Vibe utilizes views for various functions. A print view that's easily configured would be an awesome upgrade.
Customized in JSP. Vibe is completely customized using JSP. I don't know it. I'm not a programmer. I can work things out, but programming isn't my forte.
It meets our current business needs and provides the scalability we need for future growth. It can be installed on Windows or Linux (Our alpha install was on Linux. Our beta was on Windows. We went with Windows). There are additional features, and application integrations, that we haven't taken advantage as of yet due to the lack of current business needs.
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.
At this moment it still looks you need to do a lot to be able to use it and to be honest that time should be used for work not for configuring a communication tool for the business. Yes I understand that it takes time to learn something to use in the organisation , but with this tool I see the help desk having to answer a lot of questions on how to use it or once someone has done something how to undo it.
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.
Much more intuitive, Adobe XD fails to keep up with the newest market changes thus it did not let us stay on top of the technology. The big plus of Figma is that the majority of our clients worked with it, whereas it was not the case with Adobe XD. You can get similar results working with both, but the process will be different in Figmas favour
The main alternatives were Sharepoint or creating a custom Drupal install. Sharepoint was too expensive and didn't fit into our Novell environment. The Drupal solution we found was beyond our technical ability.
