FluidSurveys (Discontinued) vs. Lightning Tools Lightning Forms

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.

Overall, there are many use cases for which Lightning Forms provides a slick, easy to develop and extremely useful solution. Request forms that need to be actioned and inspection forms are the scenarios that we have used them for so far, which have seen a lot of success. We have decided that other scenarios that are perhaps more sensitive, for instance forms that may contain special category data relating to our customers, are less appropriate given the permissions/licensing constraints of both SharePoint and Lightning Forms.

• 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.

• Simple user interface - users of the forms intuitively aware of how/where to input information. This is in part due to being able to show or hide different questions or areas of the form, and making them required or not, based on previous answers.
• Low/simple code - building complex forms with automation and multiple dependencies or lookups is relatively easy once you get started. You have the power of JavaScript to use and do some quite clever things if you can get to grips with it - a lot of solutions are only a Google away.
• As it is based on SharePoint, it integrates perfectly with the rest of the M365 suite. Things like PowerAutomate enhance its functionality even further.

• There should be more flexibility and customizability with regard to survey design (e.g. background, fonts...)

• The styling of the form can sometimes be slightly awkward to use depending on what you're looking to do. For instance, if I was looking to highlight fields that users have missed (left empty), I would need to set up a validation for that question and then set a style for that particular field for when it is invalid. When you have a large and complex form with lots of dependencies, this is awkward.
• Support for complex and niche issues is slightly lacking in my experience. I submitted a helpdesk ticket for help with a strange issue I couldn't figure out, which took several weeks to get a response to. Because it is niche, it's more difficult to find an answer by searching the internet. Luckily, knowing there is likely to always be a fix if you find the right place/use the right formula, I manage to resolve the issue with some trial and error.
• It is disappointing that Lightning Forms does not integrate with the MS Lists app. Having the ability to access the form through the list app would add in a lot of useful functionality, including a better experience for users when taking photos to add as attachments.

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.

It is very user friendly both to me who is building the content (with little background knowledge of coding etc., other than what I have picked up from using products like PowerAutomate, PowerBI, a bit of html etc.) and to end users of varying levels of IT proficiency. This has been extremely important as we have used the forms to make relatively large process changes, and need to have our users on board and seeing that it is actually easier than it was before.

Some support has been okay, but in one instance of a fairly complex problem, the support team were not able to provide me with a fix within a few weeks, before I was able to find a workaround myself.

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).

We were using Microsoft Forms, SharePoint Lists and PowerAutomate to attempt to do much of what we are currently doing. Functionality is very limited in comparison. The ability to make questions required based on previous answers was a massive improvement from normal SharePoint List forms and has greatly improved the quality of data. Also just the very visual display and customisation is much better.

• Confidentiality of data is a big concern for our company, and we feel more secure working with a Canadian company. Our clients feel more secure, too.

• We changed the process by which site colleagues report repairs on behalf of customers. Instead of emailing them into a shared inbox, they now report them using a lightning form. We have seen a great improvement in the time taken for our team to log the repair issue from the time is arrives with them.
• We anticipate that streamlining our void property reletting process by using a SharePoint kanban board view with lightning forms (providing a single platform for all things void) will reduce avoidable days vacant and therefore reduce our void loss.