You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One avenue to get Soundscape on more platforms is to turn it into a web app, rather than a native app. There have been a slew of Web APIs that have been added over the years that can do lots of things that weren't possible in a browser before.
This is an appealing approach, because we would have a single codebase for all platforms, in a language (JavaScript) that's familiar to more developers. However, there are a few major hurdles that need to be overcome:
Spatial speech. You can generate text-to-speech audio, and also generate positional audio, but these are separate Web APIs. If the API works by just telling an underlying OS service to emit some speech, it might not be possible to apply the appropriate 3D effects on the resulting audio. Some discussion on the lack of integration of these two services: web audio api connected to speech api WebAudio/web-audio-api#1764
Location tracking. For privacy reasons, Apple blocks location services for web sites when the device is locked. This would interfere with a main usage mode for Soundscape, running with the device in your pocket.
I'm still inclined to have us start a minimal prototype, that can at least get a user's location while the app is active, fetch the appropriate map tiles, and announce nearby places (even if in non-spatial audio).
The text was updated successfully, but these errors were encountered:
I think that's a great idea - as you say, it will help us understand what is do-able, versus the constraints, and see how that balances out. Also, it flags the question that the current models of apps we're familiar with...may not necessarily be what emerges or evolves in the future...
I have some core functionality working in a browser, namely basic callouts based on user position and direction, with sound effects positioned spatially. There's also a testing page that replays a given GPX file. Tested on desktop and iPhone. Links to the live demo here: https://github.com/soundscape-community/soundscape-web-client
Collaborations and contributions welcome, no Xcode required :)
One avenue to get Soundscape on more platforms is to turn it into a web app, rather than a native app. There have been a slew of Web APIs that have been added over the years that can do lots of things that weren't possible in a browser before.
This is an appealing approach, because we would have a single codebase for all platforms, in a language (JavaScript) that's familiar to more developers. However, there are a few major hurdles that need to be overcome:
I'm still inclined to have us start a minimal prototype, that can at least get a user's location while the app is active, fetch the appropriate map tiles, and announce nearby places (even if in non-spatial audio).
The text was updated successfully, but these errors were encountered: