I’d like to bring up the tags again.
Wouldn’t that be a suitable way to determine Item specific behaviour in the app. In the items doc it says “tags can then be used by add-ons to interact with Items in context-sensitive ways”. That quite fits the purpose here if you consider the app an add-on (in a broader sense).
Plus: Tags are domain-specific (let’s call it that for lack of a better idea): If their names are unique and specific enough for the app (e.g. something like “AndroidSitemapCompact” for compact display or “AndroidSitemapSliderSingle” for sliders that shall only send updates when released) they would not have any impact on any other add-ons or rendering engines (BasicUI, iOS-App) and you could easily realise different presentations in the app (without any heuristics) and the user could combine different approaches in one sitemap (e.g. compact multi-switches for my rollershutters and non-compact ones where needed).