Make the portal work effectively on small screen sizes #82
Description
Is anybody currently crying out to use the diabetes portal on their smart phone? Probably not. That said, it's probably better if we think about this issue sooner rather than later, since it will have an impact on some of our design choices. It's not a huge change, and most of the nitty-gritty CSS work is handled by bootstrap anyway. There are decisions to make however (it's not at all trivial to figure out what information should appear when you only have 200 or 300 pixels to work with), and if we do it sooner than we won't have to go back and retrofit multiple screens later on.
Note that this sort of work is especially relevant when we consider attacking new data sets (such as data for schizophrenia or 28k). Once we pay the price for doing this (a few days, I would guess, or even less for a rough cut), then subsequent projects using the same code base will be able to appear on a phone without modification, and that's another mark indicating the professionalism of the software engineering we're doing.