Follow-up from Issue #8:
(Some of?) the error messages presented to users are rather cryptic/off point, and the app can get to plain HTTP 500 when parsing "incorrect" data.
It might be worth reworking the error messages/app flow so it provides more helpful information.
Login to comment on this ticket.