Hot answers tagged

5

You can show clickable text on your info-box, I think that will help user to understand the clickable thing more clearly. something like this-


2

Actually information box is used to display info asserts, so making it click able will not be a good idea. Alternative to it, you can still use information box, but allow use to trigger street view through click interaction. Make sure button size on application are optimal enough. What is the optimum button size of touch screen applications? Please see, ...


2

Taking continuity into acount I would go with something like this:


1

I would suggest to put them all in a single bar, like this one. A fab component is for the primary action related to your screen. None of these actions seem to be "primary". You could also separate the + and - buttons from the 2 others, and keep the i and the ruler as fab.


1

In an enterprise webapp we are developing we make the distinction between: modals: can only be closed through very deliberate action, because closing would break some flow or may cause data loss. These have no X button, cannot be closed by clicking outside modal. Most do have a separate "abort" button, making it more explicit that closing may result in ...


1

A general comment (but one that doesn't fit well in the comment section with links etc before anyone gets on their high horse) is that inequality symbols >, <, >=, <= get introduced in maths syllabuses a lot earlier than interval notations so I'd expect more people to understand >TIE - 55 than (TIE -55] and >55 - 67 than (55 - 67] - I remember using >, ...



Only top voted, non community-wiki answers of a minimum length are eligible