This topic was discussed in several rounds lately. There was no final conclusion from the team yet on how to handle different devices in the Sandbox but there were proposals and thoughts that found encouragement.
Generally, it can be said after reviewing first drafts of the more complex application parts, that it would be extremely difficult to provide good user experiences on small devices due to the high amount of information we need to show at a time. Without this contextual information the main purpose of explaining Govstack in a practical manner can not be fulfilled. Additionally, there is a necessity to demonstrate the UIs of our main use cases on desktop devices which also counterarguments a Sandbox fully optimised for mobile devices.
Ruling out building the scenarios/use cases full responsive leaves us with the questions:
What to do with users accessing the sandbox on mobile devices that don’t have access to desktop (ad-hoc or at all)?
How to handle responsiveness in other application parts of the Sandbox?
Data
We can’t tell for sure how high the percentage of mobile users would be on initial contact with Govstack and its Sandbox. We can’t also tell for sure how many of those users would consider revisiting it on another device if they would be told to do so because of a possibly better experience. We can only assume that at least half of new users would access Govstack on their Mobile device. Therefore it’s critical to find a
What to do with users accessing the sandbox on mobile devices that don’t have access to desktop (ad-hoc or at all)?
Option | Description | Effort | UX | Confidence | Comment | |
|---|---|---|---|---|---|---|
A |
| |||||
B |
| |||||
C | Full responsive except for use case scenarios |
| ||||
D | Sandbox Mobile Teaser | The issue is bigger. There are three obstacles for the scenario “someone quickly checks GovStack while visiting a presentation”: 1. Login 2. Deployment Time (possibly) 3. Mobile friendliness. Before accessing the sandbox, the user gets to choose between: The Sandbox Mobile Teaser is a fully responsive but light click through which does not require login or deployment. It shows just a few screens of the USCT use case (later on a second use case to be added) from citizen and civil servant and the BB involvment/Interaction. And help. At the end, it prompts to enter e-mail for desktop access. If a persons access the Desktop version, through e.g. a direct link, the user gets a notification that it can only be viewed in desktop. Link to mobile teaser. | Jonas Bergmeier Could be feasible, on the other hand it might be a better option to follow option C and have a mobile scenario in place or mark desktop scenarios as DESKTOP ONLY Jonas Bergmeier Currently it looks like there would be no deployment needed for new users accessing the web version. Of course this is still depending on the way the BBs are fledging out in the coming weeks. Jonas Bergmeier I would like to take this proposal up to share the thought on having a short demo video on the landing page, quickly demonstrating what’s going on in the sandbox. |
0 Comments