Offline App | Best practices
When we are using the offline application, there may be some drawbacks. That is why we present you a list of best practices and common mistakes to be able to maximize its operation.
Best Practices
- It is important to have a stable Internet connection while the responses are synchronized. (The data is synchronized response by response and not in bulk, however, the current response can be compromised if there is no stable connection.
- Keep the application updated with the latest version.
- Test the survey before launch and share feedback provided to end users.
- Synchronize the responses in the field at the end of the day.
- Have a version of the device's operating system: iOS (9.0 or higher) and Android (8 or higher), at least 4GB of RAM and at least 32GB of storage. (Remember that everything is saved in the memory of the device and is removed when synchronizing correctly)
- Do not use the system variable "custom1" to store information, as the device key is automatically stored in it.
- Never uninstall the application as this will cause the loss of responses stored locally on the device
- Do the necessary tests before going to the field. Simulate all possible scenarios to correct if necessary before reaching production.
- Ask your pollster to obtain a screenshot with the response values (dashboard) before synchronizing the responses, this will help them to check that the local information matches the information that is in the cloud.
- Do not use questionnaires greater than 100 questions
Common usage mistakes
- Multiple questions on the same page. We recommend adding a page break for each question to have an optimal speed during the survey. This is due to the fact that each "next" button executes the necessary functions for each question; When we do not use the jumps, all the functions for each question will be loaded into this button, which may cause situations in the operation. Maximum of 3 questions per sheet (per jump).
- Add unsupported logic in offline app since not all questions and logic work in our mobile application. Later we will indicate which ones you can use.
- Use the Stopwatch type question when using the kiosk mode. This question cannot be used if we use kiosk mode, because the kiosk has a functionality with a countdown timer that restarts the survey at the end.
- Modify the survey when they are already receiving responses. Within QP all objects (questions, options, surveys) within the database; adding or deleting some data can affect the structure of the database, which would cause loss of information. It is advisable to carry out all the edits and corrections before going out into the field.
Note: All data that is deleted from the platform there is no way to recover it since, for security and privacy reasons, QuestionPro does not make backups or backups of its clients' information.
Manual information export
Manual export / synchronization should be used when for some reason we do not have access to the application or when it does not allow synchronization. An example of this would be when the devices fall and the screen does not work, we can connect it to a computer and extract the data manually.
Question Type Support
Following question types are NOT_SUPPORTED in the offline app:
Basic Question Types
Advanced Question Types
- Pricing Analysis
- Image/Multimedia
- TubePulse
- Heatmap
- TextHighlighter
- Ordering
- Choice Models
- Advanced Matrix
- Complex Grid / Flex Matrix
- Health Care
- Homunculus Question
- Verified Signature
- Data Reference
- Logic
- Misc
- Timer
- Communitiy Recruitment
Logic Support
Following logic is supported in the offline app
- Skip logic
- Compound branching
- Show/Hide question
- Show/Hide options
- Dynamic text/comments
- Extraction
- Scoring
- Answer option randomization
- Question randomization
- Simple block randomization
Following logic is NOT_SUPPORTED in the offline app
- Looping
- Quota control
- Javascript logic
- Block randomization within randomization (nested)
Thank you for submitting feedback.