Improve submission navigation in mobile SpeedGrader Upgrades

[paulamiranda]

In the Teacher app, specifically, the only way to navigate student submissions is by swiping the screen left or right, which would take instructors/graders to the next, ungraded submission and the last graded submission, respectively.

To make navigating submissions easier, especially for instructors/graders of large enrollment courses, we ask for the following functionality, which would bring parity between the mobile and desktop SpeedGrader experience:

• A list of student submissions where instructors/graders can select a submission

• Different sort settings

• Written instructions or a more intuitive user interface for how to navigate between submissions. currently, it's not clear that a user will have to swipe the screen and the arrow buttons are somewhat misleading, because they expand/collapse SpeedGrader panels rather than move through the submissions)

Screencast (40s, no audio) showing the lack of submission navigation options in the upgraded SpeedGrader within the Canvas Teacher app on an iPad. 

[YasiAfsharnive]

@paulamiranda Thank you for sharing this detailed feedback and the screencast! We’ve passed your request along to the relevant team for review. We understand how important it is to have efficient navigation options in the Teacher app, especially for large enrollment courses, and we appreciate you outlining the specific functionality that would improve the grading experience. We'll be sure to share any updates as they become available.

[JeffWheeler]

I'm appreciating so many of the improvements, especially in the new grading sidebar, but on the ipad, I'm finding that the application is almost entirely unresponsive to swiping.  I am frequently having to swipe ten or fifteen times to get any response, so my only recourse for getting to the next student is to hit "done" and start over.

[YasiAfsharnive]

@JeffWheeler Thanks for the feedback. Sounds like a bug - I will share this with the mobile team. 

[YasiAfsharnive · Accepted solution]

@JeffWheeler, just confirmed with the team. They are actively working on a fix for this so stay tuned!