Presentation of a full paper @ EICS 2022 The paper is available at https://dl.acm.org/doi/10.1145/3534527

1. SnappView, A Software Development Kit for
Supporting End-user Mobile Interface Review
Xavier de Ryckel, Arthur Sluÿters, Jean Vanderdonckt

2. Context: End-user review of mobile applications
Source: https://polljoy.com/blog/irate-vs-appirater-open-source-rating-prompts-alternatives
iRater pollJoy
Appirater

3. Doing it with SnappView: the creator’s view
• Stage 1. Account Management and Project/SDK Preparation
Four stakeholders: creator, tester,
writer, administrator
Download SDK, create project
Get UUID

4. Doing it with SnappView: the creator’s view
• Stage 1. Account Management
and Project/SDK Preparation
Instrument the application code

5. Doing it with SnappView: the creator’s view
• Stage 2. Application Distribution
and Preparation
Publish on application store or TestFlight

6. 1
Doing it with SnappView: the creator’s view
• Stage 3. Feedback Creation

7. Doing it with SnappView: the creator’s view
• Stage 4. Feedback Handling

8. Evaluation with a real-world app

9. Evaluation with a real-world app

10. Evaluation with a
real-world app

11. Evaluation with a
real-world app

12. Main lessons learnt
• Various types of annotations by stroke gestures

13. Main lessons learnt
• Lack of guidance
Once the screen is frozen, it looks like I can do everything on the screen, but I actually do not
know how to express my review and how this review will be effectively transferred to a
developer who should correctly interpret it and take it into account
I can quickly draw the region of concern, but it is very slow to write the comment, especially by
gestures on screen and I do not know when to stop
It looks like a cool feature and does not give the feeling of entering a critique

14. Limitations, suggestions, and future work
• No stroke gesture recognition
• No predefined types of reviews
• No text recognition
• No interface region designation
• No version management for software evolution
• Should be distributed either through Cocoapods or SwiftPackage Manager
• Low startup time < 100 ms
• Acceptable application size increase should be around 2 MB or maximum 10% of the application
size.