W3C home > Mailing lists > Public > public-web-mobile@w3.org > February 2014

RE: Interest in Screen wake lock API?

From: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
Date: Fri, 7 Feb 2014 18:30:01 +0100
To: Natasha Rooney <nrooney@gsma.com>, Dominique Hazael-Massieux <dom@w3.org>, "public-web-mobile@w3.org" <public-web-mobile@w3.org>
Message-ID: <239D7A53E5B17B4BB20795A7977613A401E2DC56136D@CROEXCFWP04.gemalto.com>
Hi all,
Additional use case may be, taping your mobile for nfc payment or nfc ticketing confirmation, without having to unlock your screen.
Virginie
gemalto

-----Original Message-----
From: Natasha Rooney [mailto:nrooney@gsma.com]
Sent: jeudi 6 février 2014 18:11
To: Dominique Hazael-Massieux; public-web-mobile@w3.org
Subject: Re: Interest in Screen wake lock API?

On 05/02/2014 10:58, "Dominique Hazael-Massieux" <dom@w3.org> wrote:


>Hi,
>
>Someone just posted a proposed API to manage the "standby" mode of
>mobile devices, keeping them from e.g. locking / turning the screen off:
>http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0001.htm
>l
>
>Beyond the specific API proposal, the spec lists a number of simple use
>cases, which seem reasonable to me:
>> Long running websites
>> A user visiting a website that contains an embedded HTML5 video that
>> does not play in full screen on the device or a long running visual
>> animation. This video , or animation, may be longer than the device¹s
>> current standby timeout value.
>> The web application may adjust the device standby timeout to provide
>> a better experience
>>
>> Games that don¹t require direct touch or peripheral input A user may
>> engage in a web driven game that uses a sensor input on a device. For
>> example, a jump game driven by an accelerometer where the user must
>> tilt the device to play the game. Again, the duration of gameplay may
>> exceed that of the device standby timeout value.
>> >
>> Navigation
>> A user may wish to utilize a web application containing map feat ures
>> while operating a vehicle. The device may enter standby due to
>> prolonged periods of inactivity.
>
>In addition, both Firefox(OS?) and Chrome Apps propose a similar API:
>https://developer.mozilla.org/en-US/docs/Web/API/Navigator.requestWakeL
>ock https://developer.chrome.com/extensions/power.html
>
>I'm interested to hear what the group thinks of the usefulness of
>getting work started on such an API (for in-browser usage), and in
>particular, if implementors would likely implement and ship such an API
>in their browser.
>
>Dom
>
>


I actually think this is a great idea! This must be a MAJOR UX no-no when it comes to users watching content or working with content. My use case is looking at a recipe and having two hands covered in cake mix and then the device screen going off and I have no idea what to do next because I can¹t see the recipe anymore! Further than this, some people might watch videos and like to read comments (for example) at the same time.

Does anyone else think that this kind of API would be useful?

Thanks! Natasha

This email and its attachments are intended for the above named only and may be confidential. If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this email or call +44 207 356 0600 and highlight the error.


This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus
Received on Friday, 7 February 2014 17:30:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:59:29 UTC