- Hi everyone my name is Teddy,
I'm from the University of Calgary.
So this is one of the projects myself,
Dan, and Xing-Dong did last summer around smartwatches.
So kind of taking a step back
and thinking about smartwatches.
So over the last three to four years
there's been a number of smartwatches
that have been released commercially.
So watches from amsung--sorry,
from Samsung, Apple, Google, Microsoft, Fitbit.
Even on sites like Indiegogo or Kickstarter,
there's also a number of smartwatches as well
being made by people.
So jumping from smartwatches to this funny looking image,
I think this image kind of really captures
one of the main problems with smartwatches today.
That is, we wanna be able to do meaningful interactions.
So things like answer an email,
or a text, or navigating a map.
And we can't really do that
because the interaction is very small
on a smartwatch.
So really what we're looking for on a smartwatch,
I think, is a smartphone but on our wrist.
So that's kind of what this is showing here.
So given the fact that the touch screen
is very small on a smartwatch,
it means input is very very awkward.
So here's a couple of examples
with a current smartwatch.
So things like navigating a map,
kind of annoying.
Navigating a huge list of applications,
kinda cumbersome.
Getting a text and being able to reply
requires a secondary device.
So our solution,
or one potential solution,
is to introduce two sort of main things.
The first being a dual display,
and the second being a tangible interaction.
So I'm just going to play you a quick video
to introduce the concept of Doppio
and then I'll jump into how we actually
came up with this concept,
both from a design side and a technical side.
So here you can see I rotate the top
to switch an application,
such as music,
change the song,
switch it back.
Click at a second application underneath,
and last but not least, notifications.
So being able to open an application directly
using an adjacent side.
Then using tangible interactions
to change the mode of an application.
So play this again really quickly,
changing the top,
rotate to change the song.
Using a tangible interaction such as a hinge,
and getting a notification
and opening up the application directly.
So we are kind of influenced by three main work
that have been done before.
So the first is Codex
with the concept of hinging,
two displays for a tablet.
Second being Paddle
and sort of deformability
and changing an application.
And the last but not least is Siftables
sort of the concept of spatial awareness
of smaller displays.
We're also kind of influenced
by things that are available today.
So these are commercially available watches.
So the first two that you see at the top,
these are sort of watches that already hinge,
and the bottom one is a watch that actually
changes the face.
You can switch to a digital or mechanical watch.
So given the fact that we came up with Doppio,
we wanted to first start with a paper prototype
and give this to people to try out.
So here you see an example of our paper prototype
that we used for a study that I'll explain shortly.
So this is basically the size roughly
of an Apple watch,
has magnets underneath and cardboard
and these two basically attach and detach separately.
So as I mentioned our first study
was essentially exploratory,
as we got people to try out the concept
of the dual display watch
and look at existing applications.
Here you can see people trying out our paper prototype.
We also gave them a list of applications
to be kind of inspired by,
how they would use a secondary device
for common things that they already do with a smartphone.
So from our first study there was about
eight main takeaways.
I only have time to talk about two,
so I'll talk about them very quickly.
So the first is the concept
of unified or separate displays.
You can either have both displays
adjacent to each other,
and sort of have one unified input space,
or you can separate them and use them
for different means.
So for example if I had a map,
I could use one hand for input on a secondary display,
and the second display on my wrist
could be used for output.
The second one, which I think is kind of interesting,
is this concept of location and tangibility.
For example, if I had the second screen on the right,
or sorry on the right of my hand,
it's closer to my wrist
because my wrist is more flexible
that means I have more space
for tangible interaction.
However, if it's on the left,
because it's no space to move down,
it's probably better for things like typing.
So from this we generated
about 124 different configurations
with transitions and manipulations
and I'll explain this.
So you can think of a configuration
as a starting state,
so in this case we're starting
with stacked configuration.
I used a transition to go to another state.
So in this case I'm going to stacked hinge,
but the transition is a tilt,
then I'm going to manipulation,
which is the hinge.
So I'm hinging to up or down.
So a few more quick examples.
Slide, so now I'm sliding to the right,
with a peek,
looking at information underneath
on the first display,
or I can slide off directly into
an adjacent configuration to the right.
So obviously there's about 124 of them
and I don't have time to talk
about all of them.
Instead of showing you pictures,
I'll show you a few quick videos
showing these off.
So the first one is the stacked configuration,
so here the top is attached to the base
and I'm essentially rotating the top
in different directions.
Next is the stacked hinge as I showed previously,
so here again I'm on top
and I'm going to hinge to the left.
And again because it's four different sides in a square,
you can do four different sides
in four different directions.
Next is the stacked peek.
So here I'm attached to the top
and I'm peeking to the left or to the right
where I'm looking at information underneath.
Next is the adjacent configuration,
so very very easily being able to move
to the left, to the right,
to the top and the down,
in adjacent configuration.
In this example you see
that I have sort of visual indication
telling you what side that I'm on.
Next is the hinge and pivot manipulation,
so as I showed in the diagram,
being able to hinge or in this case,
the second one,
being able to pivot on the bottom direction.
You'll see a visual indication
telling you how much I've hinged
or pivoted as well.
So here I'm hinging,
and the top sort of gets thicker,
and the bottom kinda gets thinner.
So that's great,
we've had a design space now,
we've given it to users.
That's really cool.
Now what does that actually mean
for people to use these?
Are they actually feasible?
Are they quick?
Can they be actually mapped to applications
that people commonly use?
So that's kinda the focus of our second study,
and for our second study we implemented
a second prototype very similar to the first,
except obviously this has a little more wires
and sensing in it.
So we used magnets to sense which side we're on,
and capacitive sensing is combined.
This second study was more controlled,
so again we measured things like time
and preference for the different interactions.
So what it looks like,
and I'll show you shortly,
is we gave people the option
to move from one configuration to another,
we measured time and speed.
So the person was standing,
and then we had an application running
that basically told them from what start state
to end state they would be in
and had to go to.
So from this we essentially ran
our participants through what we call transition families.
So these are things like peeking,
rotations, and things like that.
It looked like was being able
to go from a stacked position
to a stacked north position,
which means you're just going up,
or starting in the stacked west position
where the top is rotated to the left.
You're going to the right is a peek.
So again as I mentioned we measured
things like time,
so as you can see with peeks,
they're very very quick
and they were preferred by people.
We had over 37 sort of different transitions
and configurations in our study.
So here's kind of a general sense
from the chart,
obviously there's not gonna be enough time
to talk about it.
So talk about three main takeaways
from this study.
First is times by transition family.
So things like rotation and detachments
were very slow because they require
more movement at things like peek.
However, they weren't slow enough
that they were considered to be unfeasible for users.
Next was transition times.
So things like peek were very very fast.
The things like rotation were
very heavily dependent on what side you're on.
So for example, rotation over here
is probably very easy.
If it was to be done over here,
because of the sort of solid part of my wrist,
it's very hard.
Things like preference,
speed kind of essentially was correlated to preference,
so if it was very fast,
that's things that people preferred.
If it was very slow it wasn't as impacted.
So before I jump into the cool part
of the presentation where we actually
show these off,
I'll kinda show you how we actually built this.
So we used magnets,
which essentially did the attachment
to Android smartwatches,
custom 3D printed cases,
and an Arduino that basically merged
all of the sensory information
from all of the different devices.
Okay, so one of the common things
that we do with smartwatches now is notifications.
So here's a few examples of using the Doppio concept
for notifications.
So being able to do a thing like rotate
to the left or to the right
to turn off notifications,
or using a sort of closed state
to kinda mute the notifications entirely.
So play these again,
to left to turn off or on notifications,
and a closed state to mute notifications.
Next is this concept of managing
multiple notifications.
So what happens if two comes up,
how do you manage that?
So here you're gonna see multiple notification
comes up, and I'm going to save one
and discard the other.
So the first one's gonna come up
and the next one's gonna come up.
I'm quickly going to slide down
to look at it and dismiss it.
Next time I'm actually gonna tap
the display and hold it to save it.
So play this again.
The first two are gonna come up,
I slide down to look at it very quickly,
dismiss it,
and I'll tap again to save it.
This is kinda my favorite
just because it's kinda like the Inspector Gadget
Go Go watch.
We're kinda using the second display.
So let's say I get sort of a
private notification email,
I'm using the second display
kind of as a hidden way of looking at information,
not letting people see it.
Now I deem that it's not important
so I can then open the email up directly.
Next is this concept of launching an application
directly.
So earlier I showed you
the text message coming up,
and the requiring a secondary device
to open the application.
So here I'm actually gonna open
the application directly from notification.
I'm just gonna use an adjacent side.
So notification comes up
and I put it to the right.
Next is managing systems and settings,
so being able to use peeks to the left
or to the right
to manage them.
So quick peek to the left to look at the alarm,
quick peek to the right to look at battery life.
Next is managing applications.
So if you use a smartwatch now
you know that you have to basically
download other apps to manage your smartwatch.
So here I'm gonna basically show you
how to use tangible interactions,
things like peeking and hinging to manage
multiple applications and switch between them
very easily.
So now I'm gonna rotate to switch
to a running app.
I have a secondary application
running on the next screen.
I'll tap it to switch.
Now that I see it's on top,
I can rotate back.
So here I'm gonna show you an example
of using shortcuts for applications,
since they're navigating a list,
you can rotate to the left
or to the right to open up an application
very directly.
So I rotate to the left to open up one list,
rotate to the right to open up another list.
If I want to expand my list
I can place it adjacently,
and then open the application directly.
Now I'm gonna jump into kinda the applications
that we have built using some
of the results that we talked about earlier.
The first one is very quick
and it's the weather application.
I'm going to use adjacent sides
to open up different parts of an application.
So I'll show you an example
of weather in one city versus
weather in my city.
So placing it on the bottom would
give me the weather forecast for my city,
and on the top would be weather of the other cities.
Next is the mapping application
that I kinda talked about earlier,
where I'm using one hand for input
and one for dedicated output.
So I can navigate a map with unified display,
or I can detach that display
and use one as input and one as output.
Next I can use really quick peeks,
as I mentioned before,
to do things like increase or decrease volume,
or increase speed,
or decrease speed of a video.
Last one is the photos application.
This one is kind of my favorite
because it's kinda introducing
something I think kind of novel to wearable devices,
and this is the concept of sharing.
So here you're gonna see the person
detach the first display and hand it to me.
Each time she does that
it's going to be a little bit different.
The first time she's gonna navigate
the foot-list of photos,
then she's gonna detach it with a touch.
She then hands it to me.
I'm now able to navigate the photos myself independently.
Now she's going to do the same thing
except when she detaches it,
she's not gonna be able to touch the screen.
Now you notice I won't be able
to actually navigate the information.
So now it's sort of sharing
but it's now private
to the display,
as opposed to public
as earlier.
So far in this talk I kind of explained
to you the design space,
the applications we built and what it meant
in terms of transition times
and families and things like that.
But obviously there's a bit of more work
to be done for Doppio.
Kinda on the design side,
obviously you've seen the prototype already
and how thick it is,
that's obviously something we want
to change for the next time,
so obviously limiting the tech.
Lastly, for the science side,
is the battery life,
was not very good,
because of using WiFi and Bluetooth,
so obviously that's something we will change.
On the design side,
we only really looked at square shapes.
Obviously if we looked at circular ones,
there's probably different interactions
that we could use.
Last but not least is an alternative design.
So an original prototype for Doppio
that we had drawn up,
we wanted a dual-faced, dual-sided top screen,
but obviously we couldn't do that
because of the thickness of the watch.
So that's something we'd like to explore next.
The main takeaways of the work
that I've presented to you today
are first we explore the design space
of a dual display tangible watch.
It's reconfigurable,
and we didn't wanna focus too much
on how thick it was,
it was more about the exploration,
and what it actually meant for users.
Last but not least,
we kind of tried to show how this
would actually enhance smartwatch interactions.
We're not claiming this is the best way of doing it,
but this is one way of doing it
that we think could be effective.
So that's it for me, thank you.
We'll open to questions.
(applause)
- [Alex] Hi, thank you,
- Yeah - I'm Alex Olwal from Google.
It's a really really interesting
creative exploration of the design space.
I was wondering a little bit
if you could comment on,
a lot of these interactions are based on
like all these these hints,
and affordances that you get from
like the tangible prototype,
and I was wondering how much of this
could you achieve with either
using the touch screen to rotate
and like simulate
like the flipping
and all these things,
with graphics?
Or even have like displays that are more attached,
in a more elastic fashion so you don't have
like the movable parts,
like the separate parts,
which is obviously a mechanical challenge.
- Yeah so one of our other designs,
we actually had sort of an elastic band
on the side that was kind of attached,
we weren't doing too much of the hinge
but we kinda,
we felt this was a more interesting way
to approach it.
This is kinda one of the things
that we saw in our first prototype,
when people were actually doing this
more than really worrying
about the graphics or things like that.
- [Alex] Okay, and what do you think
in terms of simulating some of these
just on a display,
but you sort of some of the same similar
gestures or motions
with, you know,
with your fingers on the touch screen,
or with some other types of input control.
So that's something that you looked at,
or planning to look at,
an alternative implementation.
- Yeah I think that'd be something
really cool to explore.
I know for myself I really like
the aspect of being able to move
a physical device around on your wrist,
and I don't know if you'll be able
to do things like detach and give
a photo to someone as well with something like that.
So, but that's a thing we could definitely explore,
and we could if you want to.
- [Alex] Thanks.
(laughs quietly)
- Hi - Hey
- [Daniel] Daniel Gotsch, Human Media Lab,
Queen's University.
I'll followup in the previous question,
and I'll start with another question.
Are you familiar with display scheme?
- Yes.
- So with that in mind,
can you tell me a little bit about
the design rationale,
because a lot of the interaction techniques
that you demonstrated
still rely on sequential navigation techniques
that we have with smartphones.
Did you consider instead what would have been
the benefits of exploring body posture
instead of having to physical manipulate
something that's on your wrist?
Which I would assume poses a little bit
of drawbacks for interactions on the go.
That's one of the benefits of smartwatches.
- Yeah, I mean,
so we, our approach, as I mentioned before,
was to really narrow down existing
smartwatches' approaches,
and the challenge they have,
some things like smaller displays,
and kind of improve on that.
We didn't worry too much about things
like the graphic or typing speed
or things like that,
we just really wanted to focus on the smartwatch,
which is why we kind of worried more about that
than other things like that.
- [Daniel] Thank you.
(faint mumbling)
(applause)