If you planned to also target the mobile users here are some great tips you may want to follow:
- First it’s the survey length. Don’t plan for more than 10 questions, who will stay on mobile anyways?
- Keep the question texts clear and short, no long answers and just a few options
- Use only basic question types, single, multi, open ends.
<meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no, width=device-width">
<meta name="apple-touch-fullscreen" content="YES"/>
I was checking the other day what’s new in Confirmit 16.
Going through the new available Flex extensions, one in particular caught my attention, it’s the “Questions extension”, and seems to have a lot of potential.
If it’s true you can use it to define new question types and make them available as new question types in the then that’s something I was begging for good years now…
Nicely done, and by the way, the name Flex is most of the time confused with the well known Adobe Flex and I had to always explain that there’s no connection between one and the other, even though, you may have a Flex Confirmit extension built in Flex(Adobe) 😉
I bet you have now lots of custom scripts, functions, validations etc. you may have stored in a survey, a survey template or a library (I can’t really see the reason for a “library” besides the different project type)
What worries me and maybe you is that everyone can alter them once they are dragged in a project, and not only…
The alternative is to create your own function libraries.
Here are some pros: You have control so nobody else can change their behavior, they are already loaded, so ready to use, no worries to include folders with libraries of functions in a project.
The usage is transparent for the user, just let them know the class and the available methods like custom.3Dgridvalidation()
I won’t focus now on explaining how to build one, Confirmit has a good documentation for this “Custom Code Library” you can get from their extranet site.