How can I differentiate duration vs starting time












18















Let’s say I have a meeting at 06:00 AM that is scheduled to last 8 hours and 15 mins . Are there any guidelines, tips or tricks to display that information in a non-ambiguous way?



If I simply display in the agenda:



06:00 - Meeting (08:15)



It can easily be misunderstood as 8:15 being either the end if meeting or, even worse, ( since we are using multiple timezones in my app) a different time zone time.



The example is obviously made up, in the real app I have a lot of starting times and a lot of durations to express in a relatively small amount of space on the same page. Simply converting to text (8 hours and 15 minutes) is not an option as it will not fit. I have space for maybe max 10 chars per item.



So how so you display a timespan in a way that is different from a datetime?



Later edit: and just to make the question harder. How about expressing time-to-go, as in the meeting is in 2 hours and 53 minutes. I need an accurate display, and most timers/chrono applications that use countdowns (eg. phone alarm apps) infuriatingly use the same 00:00 display for duration










share|improve this question









New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    Could be useful to follow ISO 8601 guidelines as representation of dates and times is an international standard. These standards apply to the data formats but it could also inform the UX design, aligning with their logic. en.wikipedia.org/wiki/ISO_8601#Durations

    – Anton Mircea
    yesterday








  • 2





    @AntonMircea: ISO durations and intervals are much less widely known and used than ISO dates and times. Some users may recognize them, but I doubt you'd get to 100% without a lot of hand-holding.

    – Kevin
    20 hours ago











  • ux.stackexchange.com/questions/75362/… , ux.stackexchange.com/questions/31168/… , ux.stackexchange.com/questions/80846/time-stamps-vs-duration , ...

    – jamesdlin
    17 hours ago











  • can u use icons?

    – xul
    14 hours ago
















18















Let’s say I have a meeting at 06:00 AM that is scheduled to last 8 hours and 15 mins . Are there any guidelines, tips or tricks to display that information in a non-ambiguous way?



If I simply display in the agenda:



06:00 - Meeting (08:15)



It can easily be misunderstood as 8:15 being either the end if meeting or, even worse, ( since we are using multiple timezones in my app) a different time zone time.



The example is obviously made up, in the real app I have a lot of starting times and a lot of durations to express in a relatively small amount of space on the same page. Simply converting to text (8 hours and 15 minutes) is not an option as it will not fit. I have space for maybe max 10 chars per item.



So how so you display a timespan in a way that is different from a datetime?



Later edit: and just to make the question harder. How about expressing time-to-go, as in the meeting is in 2 hours and 53 minutes. I need an accurate display, and most timers/chrono applications that use countdowns (eg. phone alarm apps) infuriatingly use the same 00:00 display for duration










share|improve this question









New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    Could be useful to follow ISO 8601 guidelines as representation of dates and times is an international standard. These standards apply to the data formats but it could also inform the UX design, aligning with their logic. en.wikipedia.org/wiki/ISO_8601#Durations

    – Anton Mircea
    yesterday








  • 2





    @AntonMircea: ISO durations and intervals are much less widely known and used than ISO dates and times. Some users may recognize them, but I doubt you'd get to 100% without a lot of hand-holding.

    – Kevin
    20 hours ago











  • ux.stackexchange.com/questions/75362/… , ux.stackexchange.com/questions/31168/… , ux.stackexchange.com/questions/80846/time-stamps-vs-duration , ...

    – jamesdlin
    17 hours ago











  • can u use icons?

    – xul
    14 hours ago














18












18








18


2






Let’s say I have a meeting at 06:00 AM that is scheduled to last 8 hours and 15 mins . Are there any guidelines, tips or tricks to display that information in a non-ambiguous way?



If I simply display in the agenda:



06:00 - Meeting (08:15)



It can easily be misunderstood as 8:15 being either the end if meeting or, even worse, ( since we are using multiple timezones in my app) a different time zone time.



The example is obviously made up, in the real app I have a lot of starting times and a lot of durations to express in a relatively small amount of space on the same page. Simply converting to text (8 hours and 15 minutes) is not an option as it will not fit. I have space for maybe max 10 chars per item.



So how so you display a timespan in a way that is different from a datetime?



Later edit: and just to make the question harder. How about expressing time-to-go, as in the meeting is in 2 hours and 53 minutes. I need an accurate display, and most timers/chrono applications that use countdowns (eg. phone alarm apps) infuriatingly use the same 00:00 display for duration










share|improve this question









New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Let’s say I have a meeting at 06:00 AM that is scheduled to last 8 hours and 15 mins . Are there any guidelines, tips or tricks to display that information in a non-ambiguous way?



If I simply display in the agenda:



06:00 - Meeting (08:15)



It can easily be misunderstood as 8:15 being either the end if meeting or, even worse, ( since we are using multiple timezones in my app) a different time zone time.



The example is obviously made up, in the real app I have a lot of starting times and a lot of durations to express in a relatively small amount of space on the same page. Simply converting to text (8 hours and 15 minutes) is not an option as it will not fit. I have space for maybe max 10 chars per item.



So how so you display a timespan in a way that is different from a datetime?



Later edit: and just to make the question harder. How about expressing time-to-go, as in the meeting is in 2 hours and 53 minutes. I need an accurate display, and most timers/chrono applications that use countdowns (eg. phone alarm apps) infuriatingly use the same 00:00 display for duration







user-expectation timeline






share|improve this question









New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited yesterday









Mike M

9,33611828




9,33611828






New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked yesterday









Radu094Radu094

1916




1916




New contributor




Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Radu094 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    Could be useful to follow ISO 8601 guidelines as representation of dates and times is an international standard. These standards apply to the data formats but it could also inform the UX design, aligning with their logic. en.wikipedia.org/wiki/ISO_8601#Durations

    – Anton Mircea
    yesterday








  • 2





    @AntonMircea: ISO durations and intervals are much less widely known and used than ISO dates and times. Some users may recognize them, but I doubt you'd get to 100% without a lot of hand-holding.

    – Kevin
    20 hours ago











  • ux.stackexchange.com/questions/75362/… , ux.stackexchange.com/questions/31168/… , ux.stackexchange.com/questions/80846/time-stamps-vs-duration , ...

    – jamesdlin
    17 hours ago











  • can u use icons?

    – xul
    14 hours ago














  • 1





    Could be useful to follow ISO 8601 guidelines as representation of dates and times is an international standard. These standards apply to the data formats but it could also inform the UX design, aligning with their logic. en.wikipedia.org/wiki/ISO_8601#Durations

    – Anton Mircea
    yesterday








  • 2





    @AntonMircea: ISO durations and intervals are much less widely known and used than ISO dates and times. Some users may recognize them, but I doubt you'd get to 100% without a lot of hand-holding.

    – Kevin
    20 hours ago











  • ux.stackexchange.com/questions/75362/… , ux.stackexchange.com/questions/31168/… , ux.stackexchange.com/questions/80846/time-stamps-vs-duration , ...

    – jamesdlin
    17 hours ago











  • can u use icons?

    – xul
    14 hours ago








1




1





Could be useful to follow ISO 8601 guidelines as representation of dates and times is an international standard. These standards apply to the data formats but it could also inform the UX design, aligning with their logic. en.wikipedia.org/wiki/ISO_8601#Durations

– Anton Mircea
yesterday







Could be useful to follow ISO 8601 guidelines as representation of dates and times is an international standard. These standards apply to the data formats but it could also inform the UX design, aligning with their logic. en.wikipedia.org/wiki/ISO_8601#Durations

– Anton Mircea
yesterday






2




2





@AntonMircea: ISO durations and intervals are much less widely known and used than ISO dates and times. Some users may recognize them, but I doubt you'd get to 100% without a lot of hand-holding.

– Kevin
20 hours ago





@AntonMircea: ISO durations and intervals are much less widely known and used than ISO dates and times. Some users may recognize them, but I doubt you'd get to 100% without a lot of hand-holding.

– Kevin
20 hours ago













ux.stackexchange.com/questions/75362/… , ux.stackexchange.com/questions/31168/… , ux.stackexchange.com/questions/80846/time-stamps-vs-duration , ...

– jamesdlin
17 hours ago





ux.stackexchange.com/questions/75362/… , ux.stackexchange.com/questions/31168/… , ux.stackexchange.com/questions/80846/time-stamps-vs-duration , ...

– jamesdlin
17 hours ago













can u use icons?

– xul
14 hours ago





can u use icons?

– xul
14 hours ago










6 Answers
6






active

oldest

votes


















36














Format distinction needed



08:15 is typically identified as clock format, not duration.



You could just write (8h) or (8¼h) for duration (see list of fraction unicode chars).



Here is how Google do it:



A screenshot of google calendar showing durations as 1h



Duration or endtime?



Another question you should ask is:




Which is more important for users - duration or end time?




If a meeting starts at 06:00 and lasts for 7.5 hours - it takes a bit of mental arithmetic to figure out when it ends (and it is fair to assume users might want to know that as well).



If you only display either duration or end time, there's going to be arithmetic done anyhow.



Perhaps you should just use (start-end):



06:00-14:30



instead?






share|improve this answer


























  • Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

    – Radu094
    yesterday











  • There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

    – Izhaki
    yesterday






  • 4





    @Radu094 Try 8' 15'' or 8m 15s

    – Bakuriu
    yesterday











  • @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

    – maxathousand
    8 hours ago








  • 2





    @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

    – NickA
    7 hours ago





















9














I see there a debate whether the finish time or duration should be displayed and in fact it's not what the OP is asking for. They decided to go for the duration.



So first of all I suggest making it disambiguous by explicitly stating that the bracketed value is time span:




06:00 - Meeting (for 8:15)




It still looks weird, I'll come back to it later on.



If we were to state the finish time of the meeting, I'd suggest:




06:00 - Meeting (until 14:15)




We already agreed that 06:00 (hours-colon-minutes) notation is regarded as time of day and does not need any explanation unless a clear distinction between 12 and 24 hours format is expected. The former is indicated by a.m./p.m. suffix, the latter can be indicated by adding a leading zero when applicable (thus 06:00 is 6:00 a.m. while 18:00 is 6:00 p.m.)



Now the time span - I propose using one of the following notations (in the order of preference):




8h15'

8h 15m

8¼ h

8.25 h




The first two are widely recognisable since the angular units (' for minutes and " for seconds) are often used on sport watches. The choice will depend on how much space is available.

The third one limits the granularity to a quarter of an hour since common fractions of 1/12 (5 minutes) or 1/6 (10 minutes) are not that intuitive. The former doesn't come up as a single Unicode character and the latter would be ⅙, ⅓, ½, ⅔ and ⅚ for 10, 20, 30, 40 and 50 minutes respectively.

The last notation is computational-friendly but becomes ambiguous when depicting a quarter of an hour (8.25h may by some be seen as 8 hours and 25 minutes) and totally unintuitive and illegible when 5- or 10- minutes intervals come up (0.08(3)h and 0.1(6)h respectively, or 0.08333333h and 0.16666667h).



I therefore recommend you chose between the first two. In such case your notation for the agenda appointment would be:




06:00 - Meeting (for 8h15')




or




06:00 - Meeting (for 8h 15m)







share|improve this answer





















  • 2





    "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

    – Roger Lipscombe
    12 hours ago











  • @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

    – Mike
    11 hours ago






  • 1





    Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

    – Roger Lipscombe
    10 hours ago













  • Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

    – piegames
    7 hours ago



















5














I agree with a previous comment that formatting would make the distinction clear.



08:00 - reads as 8 o'clock (time)



8hrs - reads as 8 hours (duration)



====



I would, by all means, NOT follow ISO 8601's guidelines because "P3Y6M4DT12H30M5S" is one of the most confusing strings I've ever seen! As UX designers, we HAVE to come up with a better way to present duration! ;)






share|improve this answer








New contributor




Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 3





    I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

    – Delioth
    yesterday











  • P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

    – Polygnome
    yesterday



















4














6:00 - 14:15 (8hs) - Meeting. (Starts in 2 hours).



The user can easily infer the duration of the meeting from the give time, but you can also display it after the hours. Try not to put descriptions or labels, they will only distract.






share|improve this answer








New contributor




Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




























    1














    Could you not simply just say:



    -Meeting (starts; 06:00, ends; 14:15, duration; 8.25 hrs)



    Says everything and there's no way to get confused, or are there some other constraints you haven't specified? Like max length of memo?






    share|improve this answer










    New contributor




    aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















    • Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

      – Radu094
      15 hours ago











    • -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

      – aidan
      10 hours ago













    • Rather wordy but it is clear.

      – The Nate
      1 hour ago



















    0














    What about using dur. ?



    06:00 - 8:15 (dur. 2h25) - Meeting






    share|improve this answer








    New contributor




    Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
















    • 1





      Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

      – CompuChip
      8 hours ago











    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "102"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });






    Radu094 is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f123921%2fhow-can-i-differentiate-duration-vs-starting-time%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    6 Answers
    6






    active

    oldest

    votes








    6 Answers
    6






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    36














    Format distinction needed



    08:15 is typically identified as clock format, not duration.



    You could just write (8h) or (8¼h) for duration (see list of fraction unicode chars).



    Here is how Google do it:



    A screenshot of google calendar showing durations as 1h



    Duration or endtime?



    Another question you should ask is:




    Which is more important for users - duration or end time?




    If a meeting starts at 06:00 and lasts for 7.5 hours - it takes a bit of mental arithmetic to figure out when it ends (and it is fair to assume users might want to know that as well).



    If you only display either duration or end time, there's going to be arithmetic done anyhow.



    Perhaps you should just use (start-end):



    06:00-14:30



    instead?






    share|improve this answer


























    • Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

      – Radu094
      yesterday











    • There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

      – Izhaki
      yesterday






    • 4





      @Radu094 Try 8' 15'' or 8m 15s

      – Bakuriu
      yesterday











    • @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

      – maxathousand
      8 hours ago








    • 2





      @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

      – NickA
      7 hours ago


















    36














    Format distinction needed



    08:15 is typically identified as clock format, not duration.



    You could just write (8h) or (8¼h) for duration (see list of fraction unicode chars).



    Here is how Google do it:



    A screenshot of google calendar showing durations as 1h



    Duration or endtime?



    Another question you should ask is:




    Which is more important for users - duration or end time?




    If a meeting starts at 06:00 and lasts for 7.5 hours - it takes a bit of mental arithmetic to figure out when it ends (and it is fair to assume users might want to know that as well).



    If you only display either duration or end time, there's going to be arithmetic done anyhow.



    Perhaps you should just use (start-end):



    06:00-14:30



    instead?






    share|improve this answer


























    • Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

      – Radu094
      yesterday











    • There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

      – Izhaki
      yesterday






    • 4





      @Radu094 Try 8' 15'' or 8m 15s

      – Bakuriu
      yesterday











    • @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

      – maxathousand
      8 hours ago








    • 2





      @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

      – NickA
      7 hours ago
















    36












    36








    36







    Format distinction needed



    08:15 is typically identified as clock format, not duration.



    You could just write (8h) or (8¼h) for duration (see list of fraction unicode chars).



    Here is how Google do it:



    A screenshot of google calendar showing durations as 1h



    Duration or endtime?



    Another question you should ask is:




    Which is more important for users - duration or end time?




    If a meeting starts at 06:00 and lasts for 7.5 hours - it takes a bit of mental arithmetic to figure out when it ends (and it is fair to assume users might want to know that as well).



    If you only display either duration or end time, there's going to be arithmetic done anyhow.



    Perhaps you should just use (start-end):



    06:00-14:30



    instead?






    share|improve this answer















    Format distinction needed



    08:15 is typically identified as clock format, not duration.



    You could just write (8h) or (8¼h) for duration (see list of fraction unicode chars).



    Here is how Google do it:



    A screenshot of google calendar showing durations as 1h



    Duration or endtime?



    Another question you should ask is:




    Which is more important for users - duration or end time?




    If a meeting starts at 06:00 and lasts for 7.5 hours - it takes a bit of mental arithmetic to figure out when it ends (and it is fair to assume users might want to know that as well).



    If you only display either duration or end time, there's going to be arithmetic done anyhow.



    Perhaps you should just use (start-end):



    06:00-14:30



    instead?







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited yesterday

























    answered yesterday









    IzhakiIzhaki

    28.4k45188




    28.4k45188













    • Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

      – Radu094
      yesterday











    • There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

      – Izhaki
      yesterday






    • 4





      @Radu094 Try 8' 15'' or 8m 15s

      – Bakuriu
      yesterday











    • @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

      – maxathousand
      8 hours ago








    • 2





      @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

      – NickA
      7 hours ago





















    • Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

      – Radu094
      yesterday











    • There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

      – Izhaki
      yesterday






    • 4





      @Radu094 Try 8' 15'' or 8m 15s

      – Bakuriu
      yesterday











    • @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

      – maxathousand
      8 hours ago








    • 2





      @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

      – NickA
      7 hours ago



















    Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

    – Radu094
    yesterday





    Oh, I def. need duration as that is an important quality for these events, afecting other params. Anyway, so is there any agreed format for duration? Something not involving “ : “ separator ?

    – Radu094
    yesterday













    There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

    – Izhaki
    yesterday





    There is hardly such thing as agreed formats in UX - there are conventions and context-dependent factors. I've added how google do it - seems reasonable way to me.

    – Izhaki
    yesterday




    4




    4





    @Radu094 Try 8' 15'' or 8m 15s

    – Bakuriu
    yesterday





    @Radu094 Try 8' 15'' or 8m 15s

    – Bakuriu
    yesterday













    @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

    – maxathousand
    8 hours ago







    @Bakuriu In the US, a single- and double-tic usually abbreviates feet and inches (e.g. 5' 11" means 5 feet 11 inches).

    – maxathousand
    8 hours ago






    2




    2





    @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

    – NickA
    7 hours ago







    @maxathousand They're also used for minutes and seconds, but in the context of angles, as they refer to minutes and seconds of an arc rather than minutes and seconds of time. And as someone from the UK (who use feet and inches to measure height), you're not the only one who sees ' and " to indicate feet and inches :)

    – NickA
    7 hours ago















    9














    I see there a debate whether the finish time or duration should be displayed and in fact it's not what the OP is asking for. They decided to go for the duration.



    So first of all I suggest making it disambiguous by explicitly stating that the bracketed value is time span:




    06:00 - Meeting (for 8:15)




    It still looks weird, I'll come back to it later on.



    If we were to state the finish time of the meeting, I'd suggest:




    06:00 - Meeting (until 14:15)




    We already agreed that 06:00 (hours-colon-minutes) notation is regarded as time of day and does not need any explanation unless a clear distinction between 12 and 24 hours format is expected. The former is indicated by a.m./p.m. suffix, the latter can be indicated by adding a leading zero when applicable (thus 06:00 is 6:00 a.m. while 18:00 is 6:00 p.m.)



    Now the time span - I propose using one of the following notations (in the order of preference):




    8h15'

    8h 15m

    8¼ h

    8.25 h




    The first two are widely recognisable since the angular units (' for minutes and " for seconds) are often used on sport watches. The choice will depend on how much space is available.

    The third one limits the granularity to a quarter of an hour since common fractions of 1/12 (5 minutes) or 1/6 (10 minutes) are not that intuitive. The former doesn't come up as a single Unicode character and the latter would be ⅙, ⅓, ½, ⅔ and ⅚ for 10, 20, 30, 40 and 50 minutes respectively.

    The last notation is computational-friendly but becomes ambiguous when depicting a quarter of an hour (8.25h may by some be seen as 8 hours and 25 minutes) and totally unintuitive and illegible when 5- or 10- minutes intervals come up (0.08(3)h and 0.1(6)h respectively, or 0.08333333h and 0.16666667h).



    I therefore recommend you chose between the first two. In such case your notation for the agenda appointment would be:




    06:00 - Meeting (for 8h15')




    or




    06:00 - Meeting (for 8h 15m)







    share|improve this answer





















    • 2





      "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

      – Roger Lipscombe
      12 hours ago











    • @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

      – Mike
      11 hours ago






    • 1





      Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

      – Roger Lipscombe
      10 hours ago













    • Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

      – piegames
      7 hours ago
















    9














    I see there a debate whether the finish time or duration should be displayed and in fact it's not what the OP is asking for. They decided to go for the duration.



    So first of all I suggest making it disambiguous by explicitly stating that the bracketed value is time span:




    06:00 - Meeting (for 8:15)




    It still looks weird, I'll come back to it later on.



    If we were to state the finish time of the meeting, I'd suggest:




    06:00 - Meeting (until 14:15)




    We already agreed that 06:00 (hours-colon-minutes) notation is regarded as time of day and does not need any explanation unless a clear distinction between 12 and 24 hours format is expected. The former is indicated by a.m./p.m. suffix, the latter can be indicated by adding a leading zero when applicable (thus 06:00 is 6:00 a.m. while 18:00 is 6:00 p.m.)



    Now the time span - I propose using one of the following notations (in the order of preference):




    8h15'

    8h 15m

    8¼ h

    8.25 h




    The first two are widely recognisable since the angular units (' for minutes and " for seconds) are often used on sport watches. The choice will depend on how much space is available.

    The third one limits the granularity to a quarter of an hour since common fractions of 1/12 (5 minutes) or 1/6 (10 minutes) are not that intuitive. The former doesn't come up as a single Unicode character and the latter would be ⅙, ⅓, ½, ⅔ and ⅚ for 10, 20, 30, 40 and 50 minutes respectively.

    The last notation is computational-friendly but becomes ambiguous when depicting a quarter of an hour (8.25h may by some be seen as 8 hours and 25 minutes) and totally unintuitive and illegible when 5- or 10- minutes intervals come up (0.08(3)h and 0.1(6)h respectively, or 0.08333333h and 0.16666667h).



    I therefore recommend you chose between the first two. In such case your notation for the agenda appointment would be:




    06:00 - Meeting (for 8h15')




    or




    06:00 - Meeting (for 8h 15m)







    share|improve this answer





















    • 2





      "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

      – Roger Lipscombe
      12 hours ago











    • @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

      – Mike
      11 hours ago






    • 1





      Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

      – Roger Lipscombe
      10 hours ago













    • Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

      – piegames
      7 hours ago














    9












    9








    9







    I see there a debate whether the finish time or duration should be displayed and in fact it's not what the OP is asking for. They decided to go for the duration.



    So first of all I suggest making it disambiguous by explicitly stating that the bracketed value is time span:




    06:00 - Meeting (for 8:15)




    It still looks weird, I'll come back to it later on.



    If we were to state the finish time of the meeting, I'd suggest:




    06:00 - Meeting (until 14:15)




    We already agreed that 06:00 (hours-colon-minutes) notation is regarded as time of day and does not need any explanation unless a clear distinction between 12 and 24 hours format is expected. The former is indicated by a.m./p.m. suffix, the latter can be indicated by adding a leading zero when applicable (thus 06:00 is 6:00 a.m. while 18:00 is 6:00 p.m.)



    Now the time span - I propose using one of the following notations (in the order of preference):




    8h15'

    8h 15m

    8¼ h

    8.25 h




    The first two are widely recognisable since the angular units (' for minutes and " for seconds) are often used on sport watches. The choice will depend on how much space is available.

    The third one limits the granularity to a quarter of an hour since common fractions of 1/12 (5 minutes) or 1/6 (10 minutes) are not that intuitive. The former doesn't come up as a single Unicode character and the latter would be ⅙, ⅓, ½, ⅔ and ⅚ for 10, 20, 30, 40 and 50 minutes respectively.

    The last notation is computational-friendly but becomes ambiguous when depicting a quarter of an hour (8.25h may by some be seen as 8 hours and 25 minutes) and totally unintuitive and illegible when 5- or 10- minutes intervals come up (0.08(3)h and 0.1(6)h respectively, or 0.08333333h and 0.16666667h).



    I therefore recommend you chose between the first two. In such case your notation for the agenda appointment would be:




    06:00 - Meeting (for 8h15')




    or




    06:00 - Meeting (for 8h 15m)







    share|improve this answer















    I see there a debate whether the finish time or duration should be displayed and in fact it's not what the OP is asking for. They decided to go for the duration.



    So first of all I suggest making it disambiguous by explicitly stating that the bracketed value is time span:




    06:00 - Meeting (for 8:15)




    It still looks weird, I'll come back to it later on.



    If we were to state the finish time of the meeting, I'd suggest:




    06:00 - Meeting (until 14:15)




    We already agreed that 06:00 (hours-colon-minutes) notation is regarded as time of day and does not need any explanation unless a clear distinction between 12 and 24 hours format is expected. The former is indicated by a.m./p.m. suffix, the latter can be indicated by adding a leading zero when applicable (thus 06:00 is 6:00 a.m. while 18:00 is 6:00 p.m.)



    Now the time span - I propose using one of the following notations (in the order of preference):




    8h15'

    8h 15m

    8¼ h

    8.25 h




    The first two are widely recognisable since the angular units (' for minutes and " for seconds) are often used on sport watches. The choice will depend on how much space is available.

    The third one limits the granularity to a quarter of an hour since common fractions of 1/12 (5 minutes) or 1/6 (10 minutes) are not that intuitive. The former doesn't come up as a single Unicode character and the latter would be ⅙, ⅓, ½, ⅔ and ⅚ for 10, 20, 30, 40 and 50 minutes respectively.

    The last notation is computational-friendly but becomes ambiguous when depicting a quarter of an hour (8.25h may by some be seen as 8 hours and 25 minutes) and totally unintuitive and illegible when 5- or 10- minutes intervals come up (0.08(3)h and 0.1(6)h respectively, or 0.08333333h and 0.16666667h).



    I therefore recommend you chose between the first two. In such case your notation for the agenda appointment would be:




    06:00 - Meeting (for 8h15')




    or




    06:00 - Meeting (for 8h 15m)








    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 8 hours ago

























    answered yesterday









    MikeMike

    2,8441726




    2,8441726








    • 2





      "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

      – Roger Lipscombe
      12 hours ago











    • @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

      – Mike
      11 hours ago






    • 1





      Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

      – Roger Lipscombe
      10 hours ago













    • Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

      – piegames
      7 hours ago














    • 2





      "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

      – Roger Lipscombe
      12 hours ago











    • @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

      – Mike
      11 hours ago






    • 1





      Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

      – Roger Lipscombe
      10 hours ago













    • Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

      – piegames
      7 hours ago








    2




    2





    "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

    – Roger Lipscombe
    12 hours ago





    "8 for 8:30" is (was? it might be dated; might be UK only) commonly used for organising dinner -- turn up from 8pm for drinks, dinner is served at 8:30pm. For me, it doesn't look like a duration. You admit that it looks weird, though, so...

    – Roger Lipscombe
    12 hours ago













    @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

    – Mike
    11 hours ago





    @RogerLipscombe - have you read the complete answer of mine? The "06:00 for 8:15" was about for and not about 8:15. The time span notation is explained later on.

    – Mike
    11 hours ago




    1




    1





    Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

    – Roger Lipscombe
    10 hours ago







    Yes I read it; I'm trying to explain another reason why for (with what looks like a timestamp) sounds weird.

    – Roger Lipscombe
    10 hours ago















    Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

    – piegames
    7 hours ago





    Another problem might be that not all languages have such fine distinction between for and until (or even words for both). Translating this might be hard.

    – piegames
    7 hours ago











    5














    I agree with a previous comment that formatting would make the distinction clear.



    08:00 - reads as 8 o'clock (time)



    8hrs - reads as 8 hours (duration)



    ====



    I would, by all means, NOT follow ISO 8601's guidelines because "P3Y6M4DT12H30M5S" is one of the most confusing strings I've ever seen! As UX designers, we HAVE to come up with a better way to present duration! ;)






    share|improve this answer








    New contributor




    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
















    • 3





      I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

      – Delioth
      yesterday











    • P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

      – Polygnome
      yesterday
















    5














    I agree with a previous comment that formatting would make the distinction clear.



    08:00 - reads as 8 o'clock (time)



    8hrs - reads as 8 hours (duration)



    ====



    I would, by all means, NOT follow ISO 8601's guidelines because "P3Y6M4DT12H30M5S" is one of the most confusing strings I've ever seen! As UX designers, we HAVE to come up with a better way to present duration! ;)






    share|improve this answer








    New contributor




    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
















    • 3





      I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

      – Delioth
      yesterday











    • P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

      – Polygnome
      yesterday














    5












    5








    5







    I agree with a previous comment that formatting would make the distinction clear.



    08:00 - reads as 8 o'clock (time)



    8hrs - reads as 8 hours (duration)



    ====



    I would, by all means, NOT follow ISO 8601's guidelines because "P3Y6M4DT12H30M5S" is one of the most confusing strings I've ever seen! As UX designers, we HAVE to come up with a better way to present duration! ;)






    share|improve this answer








    New contributor




    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.










    I agree with a previous comment that formatting would make the distinction clear.



    08:00 - reads as 8 o'clock (time)



    8hrs - reads as 8 hours (duration)



    ====



    I would, by all means, NOT follow ISO 8601's guidelines because "P3Y6M4DT12H30M5S" is one of the most confusing strings I've ever seen! As UX designers, we HAVE to come up with a better way to present duration! ;)







    share|improve this answer








    New contributor




    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.









    share|improve this answer



    share|improve this answer






    New contributor




    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.









    answered yesterday









    Daisey TraynhamDaisey Traynham

    513




    513




    New contributor




    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





    New contributor





    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






    Daisey Traynham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.








    • 3





      I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

      – Delioth
      yesterday











    • P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

      – Polygnome
      yesterday














    • 3





      I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

      – Delioth
      yesterday











    • P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

      – Polygnome
      yesterday








    3




    3





    I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

    – Delioth
    yesterday





    I mean, the full ISO 8601 guidelines are for completely unambiguous durations, mostly without regards to context. They also note that you can get rid of empty elements. To note 8 hours and 15 minutes, "PT8H15M" is a valid duration in ISO 8601. For UX, it'd be perfectly valid to just chop off the PT since that part will just confuse users, but "8H15M" seems pretty intuitive.

    – Delioth
    yesterday













    P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

    – Polygnome
    yesterday





    P3Y6M4DT12H30M5S can also be written as P0003-06-04T12:30:05, which is far more readable.

    – Polygnome
    yesterday











    4














    6:00 - 14:15 (8hs) - Meeting. (Starts in 2 hours).



    The user can easily infer the duration of the meeting from the give time, but you can also display it after the hours. Try not to put descriptions or labels, they will only distract.






    share|improve this answer








    New contributor




    Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      4














      6:00 - 14:15 (8hs) - Meeting. (Starts in 2 hours).



      The user can easily infer the duration of the meeting from the give time, but you can also display it after the hours. Try not to put descriptions or labels, they will only distract.






      share|improve this answer








      New contributor




      Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        4












        4








        4







        6:00 - 14:15 (8hs) - Meeting. (Starts in 2 hours).



        The user can easily infer the duration of the meeting from the give time, but you can also display it after the hours. Try not to put descriptions or labels, they will only distract.






        share|improve this answer








        New contributor




        Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        6:00 - 14:15 (8hs) - Meeting. (Starts in 2 hours).



        The user can easily infer the duration of the meeting from the give time, but you can also display it after the hours. Try not to put descriptions or labels, they will only distract.







        share|improve this answer








        New contributor




        Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 20 hours ago









        Juan Carlos Eduardo Romaina AcJuan Carlos Eduardo Romaina Ac

        1412




        1412




        New contributor




        Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Juan Carlos Eduardo Romaina Ac is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.























            1














            Could you not simply just say:



            -Meeting (starts; 06:00, ends; 14:15, duration; 8.25 hrs)



            Says everything and there's no way to get confused, or are there some other constraints you haven't specified? Like max length of memo?






            share|improve this answer










            New contributor




            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





















            • Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

              – Radu094
              15 hours ago











            • -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

              – aidan
              10 hours ago













            • Rather wordy but it is clear.

              – The Nate
              1 hour ago
















            1














            Could you not simply just say:



            -Meeting (starts; 06:00, ends; 14:15, duration; 8.25 hrs)



            Says everything and there's no way to get confused, or are there some other constraints you haven't specified? Like max length of memo?






            share|improve this answer










            New contributor




            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





















            • Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

              – Radu094
              15 hours ago











            • -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

              – aidan
              10 hours ago













            • Rather wordy but it is clear.

              – The Nate
              1 hour ago














            1












            1








            1







            Could you not simply just say:



            -Meeting (starts; 06:00, ends; 14:15, duration; 8.25 hrs)



            Says everything and there's no way to get confused, or are there some other constraints you haven't specified? Like max length of memo?






            share|improve this answer










            New contributor




            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.










            Could you not simply just say:



            -Meeting (starts; 06:00, ends; 14:15, duration; 8.25 hrs)



            Says everything and there's no way to get confused, or are there some other constraints you haven't specified? Like max length of memo?







            share|improve this answer










            New contributor




            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            share|improve this answer



            share|improve this answer








            edited 14 hours ago









            JohnGB

            61.9k20164277




            61.9k20164277






            New contributor




            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            answered 23 hours ago









            aidanaidan

            111




            111




            New contributor




            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





            New contributor





            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






            aidan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.













            • Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

              – Radu094
              15 hours ago











            • -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

              – aidan
              10 hours ago













            • Rather wordy but it is clear.

              – The Nate
              1 hour ago



















            • Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

              – Radu094
              15 hours ago











            • -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

              – aidan
              10 hours ago













            • Rather wordy but it is clear.

              – The Nate
              1 hour ago

















            Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

            – Radu094
            15 hours ago





            Yeah, I have limited space (lots of events on the page) arround 10 characters for time and about the same for interval

            – Radu094
            15 hours ago













            -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

            – aidan
            10 hours ago







            -maybe have like a key at the top of the page? so you could just have this? M(s:0600,e:1415,d:8.25)

            – aidan
            10 hours ago















            Rather wordy but it is clear.

            – The Nate
            1 hour ago





            Rather wordy but it is clear.

            – The Nate
            1 hour ago











            0














            What about using dur. ?



            06:00 - 8:15 (dur. 2h25) - Meeting






            share|improve this answer








            New contributor




            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.
















            • 1





              Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

              – CompuChip
              8 hours ago
















            0














            What about using dur. ?



            06:00 - 8:15 (dur. 2h25) - Meeting






            share|improve this answer








            New contributor




            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.
















            • 1





              Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

              – CompuChip
              8 hours ago














            0












            0








            0







            What about using dur. ?



            06:00 - 8:15 (dur. 2h25) - Meeting






            share|improve this answer








            New contributor




            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.










            What about using dur. ?



            06:00 - 8:15 (dur. 2h25) - Meeting







            share|improve this answer








            New contributor




            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            share|improve this answer



            share|improve this answer






            New contributor




            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            answered 12 hours ago









            Alexandre G.Alexandre G.

            101




            101




            New contributor




            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





            New contributor





            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






            Alexandre G. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.








            • 1





              Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

              – CompuChip
              8 hours ago














            • 1





              Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

              – CompuChip
              8 hours ago








            1




            1





            Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

            – CompuChip
            8 hours ago





            Good suggestion! Although I would probably choose 'lasts' (lasts 2h25).

            – CompuChip
            8 hours ago










            Radu094 is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Radu094 is a new contributor. Be nice, and check out our Code of Conduct.













            Radu094 is a new contributor. Be nice, and check out our Code of Conduct.












            Radu094 is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to User Experience Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f123921%2fhow-can-i-differentiate-duration-vs-starting-time%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to label and detect the document text images

            Vallis Paradisi

            Tabula Rosettana