+- FindingFive Discussion Forum (http://discuss.findingfive.com)
+-- Forum: Announcements (http://discuss.findingfive.com/forumdisplay.php?fid=7)
+--- Forum: New Study Grammar Features (http://discuss.findingfive.com/forumdisplay.php?fid=9)
+--- Thread: Major Study Grammar Update 9/13 (/showthread.php?tid=146)
Major Study Grammar Update 9/13 - Ting - 09-10-2021
Dear Researchers,
The FindingFive Study Grammar is updated on Monday, September 13, 2021 to include the following new features, bugfixes, and other changes.
New Features
- FindingFive studies will now run on Android mobile browsers! Yep - that's right: you can now design your study just once and it'll run on desktops, laptops, Android phones, and Android tablets! iPhone and iPad support will be introduced in early 2022 as well.
Not only the studies themselves can run on small screens now, most participant-facing pages (including signin, study list, single study details page) are also optimized for mobile devices. As a result, if a participant gets a link to your study, they can complete the entire participation process on a mobile device.
Researchers will still need to design studies on a desktop or laptop, but you'll be able to preview the study on mobile devices now as well.
- Improved pseudorandom stimulus pattern: It is now possible to assign multiple values to a custom stimulus attribute and perform
pseudorandomization on the trial template(s) containing stimuli with this custom attribute.
- Hide the "Press X" hint in a choice response: It is now possible to hide such a hint, which is normally displayed below the buttons, by adding "hint": false to a choice response.
- Always show the "Response Received" confirmation at the end of a trial: It is now possible to always show this message, which by default only shows up when FindingFive is syncing participant data to the server. To manually turn this on, add "response_receipt": true to the corresponding trial templates.
- In some cases, the keypress response did not accept key presses that are defined in a whitelist. This has now been fixed.
- No other notable changes in this update