Integrate Browser-/Touch-Version

[jessebenjamin]

The goal is that both versions are hosted at the MfN.

• [x] create workable flag that distinguished btw serving browser- and touch-versions
• [x] test robustness of method

[mx-e]

there is no way to reliably distinguish between displays with/without touch support in browser for multiple browsers / platforms

the standard approach would be to implement handlers for both event types. however, we serve a completely different app (layout, components) to the touch displays you would not for example want to display the touchscreen version of the app on a Surface Tablet, just because it supports touch, even if the distinction could be made.

one could use a /touch url extension to manually switch between versions this would however be publicly usable

[mx-e]

how do we go ahead ?

[wittenator]

In my opinion it is not too bad, that it is publicly available. The only question is whether we implement the router split logic in react or in Nginx

[mx-e]

to implement it in react would result in a more maintainable code base. However, depending on how much legacy code would need to be improved to handle the level of flexibility required, it might not be worth the effort. I'll get back to you on this, after taking a look at the current diff (few days, few other tickets ahead)

For now do @jessebenjamin @ckinkeldey agree on using a url extension as a flag ?

[wittenator]

Agree on the maintainability 👍

[jessebenjamin]

yes url-extension