Mobile functionality

[wackerow]

Description

The current interface stops users from mobile devices from experiencing the website at all. Part of this is due to concerns over hardware performance, and potential browser session timeouts on mobile.

If it is decided to not allow contributions from mobile, I think we could still generate some wins by at least enabling the core of the site for mobile users, which is to include an additional FAQ page (#55) and View contributions page (#56). This will allow a mobile user to at least learn a bit about what is going on, even if they are unable to contribute directly from their mobile device.

If we end up not restricting mobile devices from participating, we need to consider easier ways for user to input entropy, as it would currently involve tapping quite a bit. This may also include small updates to the copy explaining that step.

Objectives

• Remove mobile device redirect from all pages, and only redirect mobile users if they try to go to a path of any contribution step. Remove mobile route, redirect mobile to root [#58] #63
• Improve mobile responsive design to make content accessible on all screen sizes Improve mobile responsive design [#58] #59

Optional items to consider:

• Consider hamburger menu to include network status, optionally connected address, language selector, FAQ, and view contributions links
• If language selector kept visible from Header on mobile, consider reducing to only using language short-code, ie "en" instead of "English". Or just hide language name, leaving the globe icon and down chevron.

Also,

• Work out which, if any, devices should be blocked from utilizing the app based on performance of timeout limitations
  If we don't restrict mobile devices: (Update, mobile devices will be restricted)
• Add new method of obtaining entropy from a mobile device
• Update explainer copy for this step (Would need to be translated as well)

[NicoSerranoP]

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

[wackerow]

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

[samajammin]

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:

[wackerow]

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)

[wackerow]

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.