Android testing

[steinbro]

Platform-specific behavior to verify:

1. Accuracy and update frequency of location and orientation
2. Are the default TTS voice and rate reasonable? Are the available options appropriate?
3. When the screen is locked, or when the browser is in the background:
   a. Does audio continue to play?
   b. Does location and orientation get updated

Some iOS-specific tweaks/hacks have been necessary, such as getting Web Audio to work while the mute switch is enabled, and requiring a user interaction (button click) before audio will play. Does Android have any of its own restrictions that need to be addressed? It's possible using something like Howler.js would fix some of these platform-specific quirks, at least with respect to audio.

[sebastianovide]

Following this advice, I am using this ticket to provide Android test feedback.

Notes

• I don't have an iPhone, so I'm not very familiar with how the original Soundscape works.
• I went outdoors to get better reception.
• The GPS accuracy was about 10 meters.
• Tested using the link provided: https://soundscape-community.github.io/soundscape-web-client.

Feedback

• The initial talk speed was very fast. I had to click on the − button.
• When selecting a beacon 50 meters away, it didn't give me a spatial feeling while rotating the phone (see spatial audio not spatial: either left or right  #22).
• It would be great (I know... somebody needs to have time to do it...) to have the server and front end under a single server so that I could test it with a free ngrok account (it allows a single server). Perhaps it could be dockerized so that testers could run everything with a single command line.

[sebastianovide]

ok, here is PR to put the static pages and the proxy on the same URL (#23)

[steinbro]

Re: speech rate, this may be the same as was reported in #18.