Responsive Desktop Design

[andrewtremblay]

It has always been the intention that this app to be responsive. Mobile is a higher priority, so that's what is currently in wireframes. However, responsive desktops are still important for MVP.

Below is the current state of desktop and mobile (notice the large amounts of whitespace in desktop):

Given how modular react components are, we can make a better desktop eventually (and hopefully quickly, if we reuse a lot of the work done with the mobile designs).

Requirements

• Discuss out the general details of what a desktop design would be:
  • Nothing detailed, just an estimate of how it might differ from the current wireframes (e.g. two columns instead of one, images / text in different places, etc.)
• Once there is a general design, drill deeper and see if it collides with any work already being done for the Mobile wireframes.
• Deliver the edge cases of the new designs to frontend.

Constraints

The fewer deviations there are between mobile and desktop, the less work an additional design pass will take. Therefore, for fastest delivery of the MVP there should be constraints for the initial desktop design;

• That it has no unique components (interactive maps, for example)
• That reuse of current components should be encouraged (legislator rows, for example, could be exactly the same in both mobile and desktop)
• In the case that redesign of components are unavoidable, the new components should not require any new info types not already mentioned in the Info Types spreadsheet. (This would probably be the most significant constraint if the main goal is to avoid work)

[andrewtremblay]

FYI, these constraints and requirements aren't set in stone. Just a starting point to launch discussion.

[andrewtremblay]

New responsive designs are here (with some small changes still needed): https://xd.adobe.com/spec/78ce81ab-d7b7-47c9-5270-0b1d40cf98e3-0eff/