{"id":237,"date":"2009-02-05T22:33:44","date_gmt":"2009-02-06T02:33:44","guid":{"rendered":"http:\/\/designforpeople.ca\/?p=237"},"modified":"2009-02-06T09:52:29","modified_gmt":"2009-02-06T13:52:29","slug":"updated-clock-prototype-sketch","status":"publish","type":"post","link":"http:\/\/designforpeople.ca\/?p=237","title":{"rendered":"Updated clock prototype sketch"},"content":{"rendered":"

\"clock_model1a_02\"<\/p>\n

\"clock_model1a_03\"<\/p>\n

I’m making a few minor updates to the clock design, specifically for the prototype. I’m not as fond of this shape, it’s now 3″ high instead of 2″, not as sleek, but this initial prototype is more about getting everything functional, and will allow more room for error when fitting all the electronics in. Once we have all the components in there, we can see about shrinking it down.<\/p>\n

There are now two knobs instead of one. The one on the top will be for alarm functions, and the one on the back will be for time functions. In many hardware interface designs we see instances where many controls can be accessed from a single point, in this case a knob. The downfall in that approach is that you end up lumping together the more commonly-used functions with the less commonly-used. So for example, if most of the time people just want to adjust the alarm time, but they end up paging through the current time, date, etc…, it becomes more cumbersome than it needs to be.<\/p>\n

With a single rotary encoder, there is no “back” button, so the user cannot page back if they\u00a0accidentally\u00a0skip over the function they want, so they have to click several times to come back to the page they meant to be on. So by having one knob for the alarm, and one for the time, the user will have to do less paging, and they will be less likely to make any mistakes, such as changing the current time.<\/p>\n","protected":false},"excerpt":{"rendered":"

I’m making a few minor updates to the clock design, specifically for the prototype. I’m not as fond of this shape, it’s now 3″ high instead of 2″, not as sleek, but this initial prototype is more about getting everything functional, and will allow more room for error when fitting all the electronics in. Once […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,17,4],"tags":[],"_links":{"self":[{"href":"http:\/\/designforpeople.ca\/index.php?rest_route=\/wp\/v2\/posts\/237"}],"collection":[{"href":"http:\/\/designforpeople.ca\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/designforpeople.ca\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/designforpeople.ca\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/designforpeople.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=237"}],"version-history":[{"count":9,"href":"http:\/\/designforpeople.ca\/index.php?rest_route=\/wp\/v2\/posts\/237\/revisions"}],"predecessor-version":[{"id":248,"href":"http:\/\/designforpeople.ca\/index.php?rest_route=\/wp\/v2\/posts\/237\/revisions\/248"}],"wp:attachment":[{"href":"http:\/\/designforpeople.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/designforpeople.ca\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=237"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/designforpeople.ca\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}