IMO I like to think of a good mobile design as one you could operate with 'ski gloves' on.
Your controls to increment the forms are more of a worry - they are tiny and would be tough to operate on a small touch screen. As long as the elements, controls, font-size, etc. are large enough for a small touch-screen view port, then you should be good to go. If you go 2 wide, and manage bring your real-time results 'on-screen'/'above the fold' (thus avoiding the need to scroll), my view is that the usability would be improved. N On Sat, Jul 20, 2013 at 1:33 PM, Joshua Gough <[email protected]> wrote: > Hello, > > I'm using Bootstrap to build a new UI for an open source project, and I'm > trying to make it responsive. > > Here's what I have so far: > > http://www.responsinator.com/?url=run.plnkr.co%2FAUNKd97DKLAAraaQ%2F > > Source: http://plnkr.co/edit/RtQfldGpAUVsEgIHnMhf?p=preview > > In responsinator, it seems like I could get away with still have two input > fields side by side, like in the full size view. > > But, would doing that be contrary to best practices for a responsive > design? > > This 'two by two table' is a very common tool for the users of this, so I > don't necessarily want to make it look alien like this if it could still be > reliable on a smaller screen. > > This is the original tool: > http://www.openepi.com/v37/TwobyTwo/TwobyTwo.htm > > Thank you, > Josh > > > -- > You received this message because you are subscribed to the Google Groups > "twitter-bootstrap" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "twitter-bootstrap" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
