waleedAhmad1 / google-glass-api

Automatically exported from code.google.com/p/google-glass-api
0 stars 0 forks source link

Set LiveCard to non-sticky #421

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I would like to request a property for LiveCards that would disable their 
default "sticky" behavior. In other words, I would like to be able to configure 
if Glass can wake to this LiveCard. e.g.:

   liveCard.setSticky(false).

See also Issue 407.

What steps will reproduce the problem?
1. Start an app with a LiveCard
2. Navigate to the LiveCard
3. Allow Glass to Sleep, or put it to sleep
4. Wake the device 

What is the expected output? What do you see instead?

I would like the ability to have the user returned to the "home card" (clock) 
instead of my LiveCard. Currently, the user will be returned to my LiveCard.

What version of the product are you using? On what operating system?

XE12, 2nd explorer's edition of Glass

Original issue reported on code.google.com by johnofau...@gmail.com on 24 Feb 2014 at 3:28

GoogleCodeExporter commented 9 years ago
Hello,

Thanks for the feature request! Could you provide us with some example 
use-cases so that we can properly design such an API?

Best,
Alain

Original comment by ala...@google.com on 24 Feb 2014 at 6:42

GoogleCodeExporter commented 9 years ago
Thanks Alain. One example might be a fancy weather app. The app would create a 
live card, but it wouldn't make sense to have the user returned to the weather 
card when waking glass.

Weather checking isn't an ongoing activity like biking, at least for most 
folks. Our user will check the rain chances for the next hour, put glass back 
to sleep, and start a bike ride.

Now the user is sliding down a steep hill at an amazing speed. Maybe 45 MPH. A 
personal record!

Things are getting dicey. The user grips his handlebars so tightly that both 
hands are numb. And then the user remembers that he forgot to start a bike ride 
on Glass. Darn! When the user does the magic head flip at 46 MPH, the last 
thing the user wants to see is the fancy weather app. The user needs the home 
screen because one hand can't control that handlebar at 46.5 MPH! No, the only 
chance our user has at 47 MPH is a voice command, and a giant yellow moving van 
just blocked the road at the bottom of the hill, so it's now or never!

And so some sort of configuration like:

   sunsetLiveCard = timelineManager.createLiveCard(FaNCY_WEATHER_LIVE_CARD_ID);
   sunsetLiveCard.setSticky(false); //return the user to the home screen on sleep

would prevent weather apps from tempting an insane biker to steer with one hand 
in order to use the Glass trackpad.

Another, less exciting example: a timer for an online Auction. It could be a 
live card showing a real-time countdown for the time left to buy a sweet Storm 
Trooper costume in nearly new condition. While there are days and hours left on 
all the auctions, there isn't any real reason to keep this card sticky. The 
user might want to occasionally check -- oh yeah, I'm sniping that tomorrow, 
with Storm Trooper-like precision.

But when there is only ten minutes left to make a bid, now it makes sense to 
make the live card sticky. For the next ten minutes, the user wants nothing 
between him and the countdown to owning that shiny plastic armor.

Cheers,

--John

Original comment by johnofau...@gmail.com on 25 Feb 2014 at 1:02

GoogleCodeExporter commented 9 years ago

Original comment by ala...@google.com on 25 Feb 2014 at 1:16