[IxDA Discuss] Scenarios for multitouch displays?
Will Parker
wparker at channelingdesign.com
Sat Jun 2 15:09:17 PDT 2007
On Jun 1, 2007, at 5:44 PM, Oleh Kovalchuke wrote:
> On 6/1/07, Will Parker <wparker at channelingdesign.com> wrote:
>
> "...one simple-minded requirement would be 'Customer must
> remove the ID device from the table to finalize the payment.' Instead
> of mouse-up, we can think of card-up events."
>
> This is an extension of "spring-loaded" security model.
>
> I was thinking along the same lines: physical objects interacting
> with the table should be equiped with spring-loaded button for
> sharing stuff from the public "folder" in the object (phone,
> camera, whatever...). The device should not be recognized by the
> table unless the user holds the button. This approach could prevent
> some embarassing and imprudent scenarios. The button should be of
> spring-n-lock-loaded variety actually - the lock is for use of
> private table or for use with non-private devices.
Excellent idea! Another variation would be to build a standard set of
lock/unlock gestures into the Surface multi-touch OS. Swirl a secure
device counterclockwise twice and place in the center of rotation to
unlock. To lock, pick up, swirl twice clockwise. Both accompanied by
appropriate standard indicators (TBD) for locked, unlocked, and lock-
change modes.
On the other hand, that would require either building motion sensors
in the device (adding expense), or trusting the multi-touch table to
truthfully indicate it had received an appropriate lock-change gesture.
But hey, at least one mobile device (whose name starts with 'i'
already has the appropriate motion sensors built-in. In that case,
require that the motion sensed by the two devices follows the same
profile in order to enable the change in lock status on the mobile
device.
With either Oleh's good solid idea or my flight of fantasy, we're
still assuming that the person who brings the mobile device to the
table is the legitimate owner. I think a publicly-visible keypad is a
Very Bad Idea for keying in passwords, but we do need _something_ to
authenticate access to secure devices and accounts. Signatures using
a stylus would work, but as Uncle Steve says, who wants a stylus when
you have fingers
Perhaps find a simple way for device owners to register their own
personal lock and unlock gestures? This could be securely stored in
the device itself or remotely in an networked ID repository.
What the multi-touch world needs now is a good standard for
converting a sequence of finger taps into a reliable biometric
signature.
- Will
Will Parker
wparker at ChannelingDesign.com
“I wish developing great products was as easy as writing a check. If
that were the case, then Microsoft would have great products.” -
Steve Jobs
More information about the discuss
mailing list