SPServices Spring 2011 Survey Results – Part 1: Demographics

I recently did a survey asking the SPServices user community questions about how they used the library, how long they’ve used it, why, for what types of solutions, etc. I read through all of the responses, learned a few things, and promptly forgot to publish the results. There is some interesting information in the responses and over the next few weeks I will do a series of posts on what they told me. While there wasn’t really anything truly eye-opening for *me* (I interact with the SPServices user community on a daily basis), there probably will be for some other people.

Let’s start with the basic demographics. I got 172 total responses, of which 105 were fully completed. (There was a button on the last page which I think a lot of people didn’t click.)

Responses came in from around the world, but by far the most were from the US:

image

image

Most respondents have been using SPServices for at least a few months and their environments are what I would call mid-sized, though there are plenty of large-scale deployments using SPServices as well.

image

image

As expected, the majority of people use SharePoint Designer, but it surprised me to learn that almost a quarter of respondents said that Visual Studio was their primary development tool.

image

More people are using SPServices with SharePoint 2010 than I might have predicted. 71% of respondents said they were working with 2010 versus 98% working with 2007.  I think what this says is that SPServices is still a relevant and useful tool with SharePoint 2010. It also points out that a large portion of the respondents are working with both versions to some degree.

image

Finally for the demographics look at the survey, a quarter of respondents said they had some plan to move to “the cloud”. This can only be good news for the Office365 team, as well as for the relevance and long-term prospects for SPServices, IMO.

image

Next up: How are people using SPServices?

p.s. I used Fluid Surveys for the survey, and I’m impressed with their interface and analytics options. Check them out!

SPServices Survey Now Available

As I mentioned in a prior post, I’ve put together a survey to find out how people are using SPServices, what they like, dislike, wish for, etc. If you’ve ever used SPServices, or even if you are considfering using it, I’d really appreciate it if you could respond to the survey, which is available here.

If you have any issues responding to the survey, please let me know in a comment on this post.

Thanks for Christophe Humbert, Kerri Abraham, Matt Bramer, Josh McCarty, Sadie Van Buren, and Claire Willett for their help in test-driving an early version and contributing valuable questions and feedback.

FluidSurveysBTW, I did a mini-review of the available online survey tools for this, and decided that I liked Fluid Surveys over the other options. I started with Survey Monkey and also looked at Zoomerang, Qualtrics, and a couple others. I easily went past the 10 or 20 questions that each offers for free, and the free versions also don’t let you do things like simple branching, there are limitations on question types, etc. I liked the price point for FluidSurveys ($19/month) as well as their UI.