ISSUE-2: Mobile / Limited hardware considerations
hardware
Mobile / Limited hardware considerations
- State:
- CLOSED
- Product:
- Use Cases and Requirements
- Raised by:
- Olivier Thereaux
- Opened on:
- 2012-02-10
- Description:
- The need for our audio processing API(s) to function well on mobile of hardware-limited devices is one that has been raised several times since the creation of the working group.
Most recently, James Wei has raised in in a thread about prioritizing features for v1:
http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0215.html
and Samuel Goldszmidt argued that spatialization is one such case where hardware capabilities (not necessarily limitations) is crucial:
http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0218.html
At the moment, the notion of working on a mobile device has been captured in only one use case (HTML5 Game):
http://www.w3.org/2011/audio/wiki/Use_Cases_and_Requirements#UC_2:_HTML5_game_with_audio_effects.2C_music
- Related Actions Items:
- No related actions
- Related emails:
- Audio-ISSUE-2 (hardware): Mobile / Limited hardware considerations [Use Cases and Requirements] (from sysbot+tracker@w3.org on 2012-02-10)
Related notes:
The need for the API to function effectively on various devices, including mobile hardware, has been documented in use cases (including UC2: HTML5 game with audio effects, music and UC10: 10 : Podcast on a flight), in the requirements (mentions of performance in polyphony support, etc) as well as a section on "Performance and Hardware-acceleration friendliness.
The Issue has been "pending review" since the addition of mobile in Use Case 2. Seeing no objection, closing.
Olivier Thereaux, 22 May 2012, 12:22:10Display change log
