Mobile functionality about trusted-setup-frontend HOT 5 CLOSED

Hey Paul @wackerow! I just merged the wackerow/responsiveness branch, does it close this issue?

from trusted-setup-frontend.

@NicoSerranoP Not yet, but it checks one of them off =)

from trusted-setup-frontend.

Curious to hear input on this but for now I'd propose we cut mobile support from an initial production release. Seems like there's enough things to work on to make this app production-ready for desktop across various browsers.

Does anyone have strong conviction that people will actually be using this from their phones? Or is that more of a nice-to-have?

I suggest we strongly consider shipping with just a desktop app, then see how many people try to actually perform the ceremony on their phone. e.g. perhaps we style the homepage for mobile, then measure how many people on mobile devices click "begin".
Maybe to start we push folks to desktop like on the Staking Launchpad:

from trusted-setup-frontend.

The page currently displays a page like this for mobile devices (a for mobile device agents is performed, and users are then routed to /mobile which is a component similar to above.

PR #63 introduced one possibility to handle this differently, but enabling certain paths to be viewed on mobile, but the button to start is disabled (and directly going to the ceremony URL paths will kick them back):

If we decide to not go with supporting mobile for the actual ceremony, I propose this as an alternative so users visiting on mobile can still access the landing, faq and records pages, and also gain access to the footer links if they like (vs being hit with a wall)

from trusted-setup-frontend.

For a number of factors, it sounds like included mobile devices in the ceremony is not going to work out. As such I've updated the original post, removing todo's related to enabling mobile devices. Also pulled a couple items out as optional.
Hiding the languages on mobile could be a simple win, but not necessarily critical. Open to discussion, but in the meantime I'm going to call this issue complete.

from trusted-setup-frontend.