New answers tagged visual-design
You should really see if you can compress down your feature set. Some companies seem to love having a huge feature matrix, but this can make things confusing (see "the paradox of choice"). Don't be set on the idea of checkboxes, either. That works well for a feature that is completely unavailable in lower tiers, but many things are offered at different ...
I think this is a design question where the overall content and intent of the design needs to be assessed and understood first. By content I am referring to the actual differences between the plans (or tiers) that you are going to display. There would be very little point in showing the information in a table if all three tiers offered very similar ...
JIRA uses the '3h 15m' style notation which works for me. Oh the other hand, I used a timesheet system in which time was entered in 15 minute blocks. I found having to enter times as a decimal values like 3.25 was non-intutive way of expressing a duration of 3h 15m. On the example given, couple of things are not clear: What is the granularity? Minutes?, ...
ISO 8601 Duration As mentioned in the answer by Crissov, the ISO 8601 standard defines a textual representation of a span of time in this format: PnYnMnDTnHnMnS, called Durations. In this format, the P marks the beginning. The T separates the days portion from the time (fractional day) portion, and is omitted for whole days. Examples: P1D = One whole ...
It seems to me that confusion occurs because there are 2 low-order places with both methods. You could take all the data to fixed 3 decimal places (or 1 decimal place) of an hour, using a decimal point, and rounded before display. Remember to keep the data accurate by doing the maths in integer minutes internally, so minor floating-point errors can't occur ...
One other solution could be to show the seconds as well. Since seconds will be changing quickly it will be clear that the times are continually changing. I don't recommend this solution but from the perspective of clarity, it works.
You can also show the minutes with a smaller font. On stopwatches, this is done for the seconds or milliseconds. download bmml source – Wireframes created with Balsamiq Mockups
The international standard ISO 8601 would suggest P04:00 or P4H. Its part on periods, durations or time spans and repetitions, though, is hardly ever followed – and you aren’t using its date format in the first place. JFTR Please note that 4h00 is not unambiguous, since some people tend to write clock times that way. 4h00m or 4h00min would be better. ...
Another possibility would be to add a "prime" mark at the end, as is sometimes (often in race times) used. Minutes and seconds would look like 4′33″, so a single prime is minutes, so use 1:30′ for an hour and a half.
You could use decimals. So for example: 90 minutes would be 1.5 hours instead of 1:30 3 hours and 45 minutes would be 3.75 instead of 3:45 This format is highly scannable and makes it easier to sum the values in your head.
A plus sign is sometimes prefixed to the time format indicate offset. It can also imply duration. For example: +4:00 +10:00 +4:00 +6:00 +0:00 +6:00
You are right to ask this question. It really depends on who your users are. In labor-intensive environments, users are often very familiar with the HH:MM notation for duration, so it's OK to use that format. But, I agree that even for those environments easy to get it confused with time. Is there a better way? Let's start with the existing solution. ...
Top 50 recent answers are included