College board owns this process, and it’s their job to make sure the setup works correctly for all students, including those who might not all be technically inclined.
College board owns this process, and it’s their job to make sure the setup works correctly for all students, including those who might not all be technically inclined.
From what I've heard in articles and other sources, uploading directly from the iPhone works fine. The issue is only when students try to upload an HEIF file from a computer, instead of directly from an iPhone, which requires:
1. The student has an iPhone, which they use to take a picture of their work.
2. The student chooses not to upload directly from their iPhone, and instead wants to use their computer (presumably they're already logged in there).
3. The student's computer is a Mac, and they choose to use AirDrop (or another method that doesn't do conversion) to transfer the file instead of email (or another method that does convert to JPG).
4. The student is using Chrome/Firefox or another browser that doesn't do automatic conversion to JPG.
I would argue that this qualifies as an edge case. Presumably, CollegeBoard did their due diligence testing the basic single-device flows, but didn't cover multi-device flows, or just missed possibilities like AirDrop instead of email for transferring images.
I agree that they should have done a better job informing students; there probably should be more info on the upload page itself.
If you stay in the "regular" apple workflow everything is fine: iphone camera -> icloud/photos (airdrop/photos) -> safari. If you deviate at certain points though the workflow breaks down. Whose fault is that?
You seriously over-estimate the "tech-savviness" of the average student and that really is part of the issue I'm pointing out here.
Source: I work in tech for higher ed.