FluidSurveys was a survey and form building option. SurveyMonkey discontinued the product, it reached end of life (EOL) December 2017.
N/A
zeroheight
Score8 out of 10
N/A
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be easily shared across teams.
For surveys, and for centralized info-gathering, FluidSurveys provides an excellent solution. There are other programs out there which provide a wider range of solutions (i.e., they can be used for surveying AND comprehensive online engagement, rather than just a data-gathering type of consultation); however, for programming and implementing surveys, FluidSurveys has an effective variety of strengths and options that make it optimal for users who are focused specifically on surveys.
For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
User-friendly. For the majority of the general and basic tools you can use with FluidSurveys to build surveys are simple to use and intuitive. When certain issues come up, the service is quick (chat room) and effective.
Anonymity: the software has the reputation of being safer in terms of safeguarding private information the respondents share by answering surveys (this is mainly due to the fact that the servers are in Canada). Thus, indirectly, they increase response rates.
Extensive possibilities: FluidSurveys offers a plethora of possibilities and options that really renders the experience interesting in terms of micro-managing each details of the surveys you are sending out there. When the invitation leaves by email, it is exactly how you want it.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Note: I am responding to this question as a user of the system and not a representative of my organization.
On a personal level/as a user only, I would definitely continue to use FluidSurveys.On a personal level/as a user only, I would definitely continue to use FluidSurveys.
I think the average person can very quickly pick up on the basics of the system: they would have no problems programming and launching a basic survey. Organizations may benefit from having people of different backgrounds getting their hands dirty in the system: at a minimum, both web programmers and opinion research advisors should be solicited for input or help.
Although I do not have much experience with Survey Monkey, the only two reasons why I choose FluidSurveys is that clients demand it (privacy and anonymity) and because managing multiple surveys at a time is easier. As for ODK Collect, I think it is a valuable alternative to FluidSurveys if you have time to learn the coding (not very complicated). ODK is a little less user friendly and you cannot address small details as you can with FluidSurveys (e.g.: formatting).
I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
increased quality, as less misunderstandings or communication problems occur
increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
