New MobileComponents Time and Date Picker

[Thomas Pfeiffer]

On Sunday 24 March 2013 18:57:44 Michael Bohlender wrote:
> If indeed it can only be recognized as long as it moves, we cannot use it
> as a
> 
> > standard component. What if there is only a date picker, or a time picker
> > which does not reflect the current time and therefore does not move?
> > We should test if it offers the affordance even while static. If it
> > doesn't, we
> > have to choose a different design.
> 
> i forgot:  It will also move if you press an arrow.

Sure, but users have to recognize at least the arrow buttons as interactive. 
and that's something you can test easily with a static prototype. Of course 
since you have it implemented, you can test that with users ;)