I'm working on an application where a user can submit an important document that contains information we need from them. The information contains details such as - event name, event location, duration, etc. I think there are around 20+ fields, depending on the user's preferences; not all of them are required.
What would be the best UX for the user?
A. Simply be able to upload this document in PDF format
B. In addition to being able to upload the PDF document, ask the user to fill out a form that includes fields like event name, location, etc. Most of the items can already be found in the document.
The idea here is for our own staff to not have to manually copy and paste data from the document into our system.
I think idea (A) is great from a user-standpoint. That means that as a user, I don't have to do any of the work. Think about Expensify and being able to scan receipts vs having to manually input each expense.
The downside of (A) though is that it may not be scalable long-term because at some point, our staff won't be able to handle all of this manually. I'm worried about users being spoiled - ie, giving them the easiest solution to their problem during the initial roll out, then asking them to fill out a form in the eventual future.
But that said, this feature is an alpha release, so we don't know if this is actually going to get traction or not. Solution (A) will also save Engineering time by building something simpler.
But with this approach, are we moving backwards?
Think again about Expensify - what if they rolled out their scanning functionality first before the ability to manually input individual expenses?