Matija Nalis

I would just add here that if we opt for **_"regular file + `android share`"_** (instead of **_"URI + QR"_**) we neatly _**avoid all those problems**_ related to data size,...

@smichel17 that being said, it that path is taken, exporting only one preset sounds like a better idea: - it simplifies UI somewhat (no need to add checkboxes for choosing...

(related: https://github.com/streetcomplete/StreetComplete/issues/3034)

@vizsim as a quick workaround in your specific case, if you can't wait for feature to be implemented, it should not be too complex to present instructions to students to:...

@vizsim if you're dealing with higher number of quests, another alternative is forking the project and editing `app/src/main/java/de/westnordost/streetcomplete/quests/QuestsModule.kt` to only have quests that you want. You can even have GitHub...

My comments: - I myself still use ordering functionality and find it very useful. (though I usually do not have a huge number of quests with changed positions, usually about...

That could probably be simplified as "_if the **ending node** of the way has **any tag at all**, skip this quest"_ As for the other suggestions, tags on the way...

Also, how is `Edit description` supposed to work? Once the quest is initially submitted (with or without adding description), the quest would not be asked again, and so option to...

Quest which pops up only on `wheelchair=limited and !wheelchair:description` maybe might be possible, but it wouldn't work for editing existing descriptions (it would fail required _":thinking: No unanswerable quests"_ [quest...

@opk12 Understood, I was just examining other possible options. One should note that [quest guidelines](https://github.com/streetcomplete/StreetComplete/blob/master/QUEST_GUIDELINES.md) do say: - :atom_symbol: Atomic quests: Per quest, only one thing should need to be...