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.
N/A
UXPin
Score 7.9 out of 10
N/A
UXPin is a UX design platform with wireframing, prototyping and interactive mockup features.
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.
UXPin is an excellent resource for creating website and app flows and to better help our clients understand how their websites and apps will function. It also gives them a visual reference and some real-life application. It can be difficult for clients to truly understand how a website or an app flows from one page or screen to another via a phone call or web conference. UXPin helps us to illustrate these flows in a hands-on, visual format. UXPin also helps our clients understand the purpose of a sitemap. We used to send our clients a sitemap in an outline format. While many understood that the top-level items on the outline were the main navigation of their website and other items were child pages, several did not. We have found that using UXPin to show the main level navigation, how in-page navigation and child pages (drop-down menus from the main navigation) work has been an integral step in getting approval on sitemaps.
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.
Smart elements are super nice because they allow me to create complicated features that will appear on every page. When the client wants to change something it is very easy to do so in one place.
Working on grid is important to me. Having the ability to change and manipulate that grid in UXPin is just what I need.
There are tons of add on features like Font Awesome icons and prebuilt stuff that not only looks great, but also just lets me get ideas across fast without committing to what the final design is going to look like.
I love the ability to edit things if I want. I can control several details, but it's not too overwhelming. They include various font options from Google fonts as well. You can design as much or as little as you want. The interface doesn't get in the way. It's there if you want it but has a simplicity that is nice.
Having a link on a live webpage is a necessity. As soon as you make changes, they are live. No more worrying about which is the latest version.
I'm a photoshop user so it has a few keyboard commands that are familiar like hold 'alt', click and drag to duplicate is nice!
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.
No search and replace for fonts (missing or just to replace).
Tool is built for design/dev teams but does not integrate content teams in well.
If you are not careful you can get lost in designing interactions when you should be just creating building blocks - don’t over animate!!!
There is currently no “scrub” or click-drag interaction which limits touch capability testing/concepts.
Editing adaptive versions of designs is very time consuming, edits to not ripple through from master viewport size. All updates are manual, even when creating an adaptive version.
When a library item is updated, it can revert changes you have made unknowingly.
Video integration is limited to online video host aggregators such as IMGR, YouTube, and Vimeo.
Not a ton of info for a designer on how to use the expressions effectively.
Prototypes with a lot of interactions can get slow, especially on computers with a lot of security software. It’s best to work with UXPin to figure out what is blocking APIs, and JS.
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.
We'll definitely continue to use UXPin. Right now it provides us with everything we need in order to deliver quality projects to our clients. If at any point in time, UXPin doesn't provide us with what we need, we'll start vetting other software out there that may be similar. My guess is that UXPin will continue to make updates and improvements so we'll likely stick with it for quite some time.
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.
As far as I know, my teams have only had to use the UXPin support once. The experience went really well. We just needed a bit of assistance with using the Documentation feature. UXPin's support was quick and helped my team in a matter of minutes. We will definitely reach out to their support without hesitation in the future.
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.
Adobe XD is so much more than UXPin, with Adobe Cloud you can easily share designs as well. We used Adobe XD before changing to UXPin. At first UXPin seems so advanced and helpful, but don't get fooled. You're heavily limited in the long run, and after all the training and implementation of UXPin (both app-wise for IT but also training designers etc) it is not worth your time.
Saving money by using one tool for lo-fi wireframing, high fidelity wireframing, prototyping, and user testing, rather than four separate tools.
The ability to create and use team libraries enables us to create visually consistent designs with less effort than creating every single design from scratch, which allows us to save considerable time (and therefore money!)
In-platform collaboration saves our team a lot of time and energy. With everything in one place (wireframes, prototypes, user feedback, collaboration comments), we can all be on the same page about the design workflow and pinpoint discussion points that are based on up-to-date designs.
