Overcomplicated solution to a simple problem
I agree that attendance in classes is typically complex (sign in sheets, roll call, etc), and a simple QR code is a good alternative, however, a whole application surrounding this is a complex solution.
I, as a student, would much rather scan a QR code that took me to a website where I could then enter my name or other identifying information – the time saved by removing the need to re-enter this information does not outweigh the impact of downloading an app.
Additionally, the current interface is rather confusing (I know it’s brand new, and some jankness is expected): it seems UIKit is hardly being used. There are hardly any confirmations to show that a CWID/name/etc are accepted, you simply close the page with the ‘X’ - an action typically associated with cancelling a process. It looks like the interface was designed with something trying to replicate material design which, although somewhat native on Android, is extremely unexpected and hard to do well in an iOS context – Apple has created HID guidelines for a good reason.
Finally, a few simple nitpicks: class codes should not be case sensitive, particularly as the large title bar on the instructor’s screen forces the code uppercase, creating the possibility for students to be confused when the code they see is not accepted. Secondly, a solution which does not require giving out a student’s CWID to an unknown, non-university affiliated party concerns me and likely other security-minded students. This may be cynical, however, it is sensitive information which many are not comfortable simply handing out.
I look forward to seeing how this app improves and grows over the semester – once again, it is a good solution to this issue, I just feel it is quite overcomplicated given the core of its solution.
I, as a student, would much rather scan a QR code that took me to a website where I could then enter my name or other identifying information – the time saved by removing the need to re-enter this information does not outweigh the impact of downloading an app.
Additionally, the current interface is rather confusing (I know it’s brand new, and some jankness is expected): it seems UIKit is hardly being used. There are hardly any confirmations to show that a CWID/name/etc are accepted, you simply close the page with the ‘X’ - an action typically associated with cancelling a process. It looks like the interface was designed with something trying to replicate material design which, although somewhat native on Android, is extremely unexpected and hard to do well in an iOS context – Apple has created HID guidelines for a good reason.
Finally, a few simple nitpicks: class codes should not be case sensitive, particularly as the large title bar on the instructor’s screen forces the code uppercase, creating the possibility for students to be confused when the code they see is not accepted. Secondly, a solution which does not require giving out a student’s CWID to an unknown, non-university affiliated party concerns me and likely other security-minded students. This may be cynical, however, it is sensitive information which many are not comfortable simply handing out.
I look forward to seeing how this app improves and grows over the semester – once again, it is a good solution to this issue, I just feel it is quite overcomplicated given the core of its solution.
Show less
