Please help us help you and fill where relevant:
Your LimeSurvey version: 6.12
Own server or LimeSurvey hosting: Own
Survey theme/template: Default
==================

Hi everyone!

I am moving a project from Qualtrics to LimeSurvey and I am looking for a specific feature. In Qualtrics, there is a native option to "Allow Mobile Devices Only" (or block computer/desktop access), which prevents students from taking the survey on a laptop or desktop computer.

Example from Qualtrics:

My Question: Does LimeSurvey have a built-in setting (or a recommended plugin) to enforce this "Mobile Only" restriction?

If there is no native setting, what is the current "best practice" JavaScript workaround to detect the device type (User Agent) and screen out non-mobile users?

I am looking for a solution that either:

Prevents the survey from loading on desktop devices entirely.

Or redirects desktop users to a "Screenout" page with a message asking them to switch to a mobile device.

Thank you for your help!

Hi,
you can use javascript to retrieve a lot of informations
Like this


Please, follow this post.
[url] forums.limesurvey.org/forum/can-i-do-thi...vice?start=30#233944 [/url]

Joffm
 
 

jorgesinval wrote:

I am moving a project from Qualtrics to LimeSurvey and I am looking for a specific feature.

Why are you moving a project from Qualtrics to LimeSurvey? It's good to get more posts from users of other survey tools here.
The feature set of Qualtrics is quite different. E.g Survey flow is a lot more work in LimeSurvey than in Qualtrics.

Thanks for the answer, Joffm. However, what I actually need is a way to block specific devices. I have implemented your previous suggestion to capture browser information with a hidden question ( forums.limesurvey.org/forum/can-i-do-thi...ersion-6-12-0#273012 ). Works great, thank you again.

I would like to explore the possibility of blocking the survey for participants using computers (in one scenario) and blocking those using smartphones or tablets (iOS and Android) in another.

Several users at our university are interested in exploring LimeSurvey. Given the high cost of Qualtrics, LimeSurvey appears to meet almost all our requirements. Additionally, the ability to host it on our own servers is a significant advantage for our IT department.

jorgesinval wrote:

I would like to explore the possibility of blocking the survey for participants using computers (in one scenario) and blocking those using smartphones or tablets (iOS and Android) in another.
 

Technically you cannot block devices.You can try to capture information via the http-protocol and javascript and then use that information to redirect survey participants.

The survey flow funtionality of Qualtrics will be hard to mimic in LimeSurvey. The amount of workarounds and scripting will be a complete diffferent user experience. Would be nice to see some feature requests and discussions around implement some kind of flow control into LimeSurvey.

Joffm showed a way to mimic the Meta info feature of Qualtrics.
www.qualtrics.com/support/survey-platfor.../meta-info-question/

To mimic the User Info feature of Qualtrics
www.qualtrics.com/support/website-app-fe...ser-info-conditions/
further hidden questions have to created to extract infos to be matched via scripting to allow hiding or showing questions in certain cenarios.
In Qualtrics one click. In LimeSurvey it can take some work depending on the complexity of the conditions to meet.


If a device has an certain amount on secuity settings enabled the user info captures via http-protocol and JavaScript can be altered. So you cannot be 100% sure about the infos you get from other devices. The useragentstring is of manipulated these days.

To create a surveyflow that differs between mobile devices and computers the screen resolution is a good criteria. An ipad can have a bigger screen resolution than laptops these days.

To have a special question type in LimeSurvey to offer certain device strings would be helpful for survey designers to make the transition to LimeSurvey.
 

Good point. I think my workaround will be to collect the browser information and then close the survey according to the inclusion or exclusion criteria.