I'm creating a form for a site which requires, as part of the registration, the user to upload a file (a CV/ resume).
I'm looking for suggestions on the best way to handle this, i.e what if they don't have the file on their phone (very likely...)
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
Personally I like the sites which enables functionality based on how complete your profile is. You could for example allow access to a limited portion of the functionality of your application before the registration is complete. This way you can layer your registration process from having just the basic information provided (name, email, password), to having all work-related information stored.
CVs are anyway not static information, so even if a user provides a CV at registration, there is a good chance that you'd like an updated version of that CV in a couple of years time.
I think resume upload from mobile should be optional, BUT, user should be alerted prompted/when s/he logs back in via desktop web to upload resume at that time. Agree with other answer that maybe features should be limited while resume is not uploaded, but I don't see any feasible way that a user will easily be able to upload a resume via mobile web. And you don't want to prevent mobile web registrations either. Your best bet is to allow no resume upload via mobile web, and force user to upload resume next desktop web session. I'm never a fan of forcing a user to do anything, but it seems that this is what the client wants.