End of Survey / Redirection / Mobile App /

[Kodzhabashev]

In GitLab by @nicolas.scheurer on Jan 9, 2024, 17:26

Some observations:

• If a survey has finished and contains a special End of Survey (EoS) message that is not part of the actual questions, the EoS message will only appear very briefly and then a refresh will occur and the once_per_schedule or once_per_user alert will be triggered and the EoS text was not human readable at all.

• This applies to surveys on the mobile app that are rendered as modals.

• The way modals work in the mobile app makes the frequently implemented concept of a homepage, where the active surveys are linked using condition-based buttons, very difficult to realise with SurveyJS. This is because the survey is displayed as a modal and when the survey is finished, the content of the homepage is not yet updated.

• For mobile, one cannot use an EoS message in the SurveyJS Builder either, because the only way to exit the survey is to use the hardware back button, but then the state of the homepage is not correct.

[Kodzhabashev]

In GitLab by @nicolas.scheurer on Jan 11, 2024, 15:22

So the question is:

• [ ] How can the group-membership-based Experiment Flow, which is based on Form Actions, be implemented with SurveyJS in a user-friendly way (Home page -> Button to survey -> Complete the survey -> See a thank you message -> Have an updated home page)?

[Kodzhabashev]

In GitLab by @Kodzhabashev on Jan 11, 2024, 15:30

See a thank you message should happen on the modal? Then if you use close modal on finish this message will not be seen.

1) I can add a timer option, when the modal to be closed? But again are we sure that the message will be able to read the thank you message or not for that time.

2) Do not use a thank you message but use a new page and put a description text for thanks you and then the user on complete will end the survey and close it. But if there actions waiting for the end of the survey and the user do not finish it and click back then the actions will not be triggered.

For the refresh, when you use redirect on the survey, it refreshes that page and redirect the user to that page. If the redirection is the same page from where you opened the modal then it will refresh it only and as you are already there no redirection will happen.

[Kodzhabashev]

In GitLab by @nicolas.scheurer on Jan 17, 2024, 14:41

I don't think the timer is the best solution for this.

The workaround in one project is now that the surveys are embedded in a page that does not appear as a modal on mobile, but is embedded in a tab. At the end of the survey, the user is redirected to the same page.

As a result of a finished-triggered job, the user is in a new group and therefore sees new content (the thank you message) on the same page where the survey was previously displayed.

However, this prevents for example the usage of the "Show the Survey Complete page" in the "Survey Complete" tab in SurveyJS Builder. As this Complete page would flicker away...

---

I see a bigger challenge here, which is that on mobile, pages that do not have a tab are displayed as modal.

This issue here can actually be considered locked due to the described workaround.

The question is, will you have the opportunity to change the presentation of the pages in the mobile application (other than modals)? Another example in this direction: If there are too many tabs on the first level, it becomes cluttered.