wtimme

Sounds like a valid use case. At the moment, an [`Answer`][1] only has a `key` and a `value` property. We could extend the modify the object to have a list...

Good point, thanks for the input! You're correct: At the moment, the answers are rather fixed. The branch is going for an MVP that would allow the answer of simple...

Nice idea, I like it! For the quest system in its current state, we need this information: - **Quest ID:** A `String` that is used to reference the quest's "selected"...

Thanks for the feedback, @bryceco! This looks quite easily doable, thanks for providing the link to the line! I don't have that much experience with that particular API. Are there...

Thanks for the quick response, @westnordost! That's great news. You were correct, creating an own app from scratch requires a lot of effort, which is why I decided to contribute...

Hey Tobias, I was not feeling well yesterday, which is why I decided to stay home and get some rest. I wrote you a message on Slack, since I figured...

Thanks for the input, @bryceco, appreciate it! I am very open for pull requests. In its current state, the app is using classes for the quests, as it makes it...

We _could_ add new classes, but in order for the app to fulfill an actual use case, we should probably first focus on enabling mappers to actually upload their answer,...

Thanks for your concerns! Yes, that looks like the place. From what I can tell, the string seems to be encoded with Base64. `lzw_decode` seems to refer to a compression...

Thanks for the suggestion! I like the idea. As an MVP, we could just display the `QuestListTableViewController` modally the first time the app is started. As an alternative, I think...