Soundscape-Android

Release notes

0.0.56

This release has many of the main features at least partially implemented. The maps from the cloud cover the whole world which means that the app can be tested anywhere.

We’re releasing the app to:

  1. Enable wider testing and check support across a wider selection of real world devices
  2. Get initial feedback on accuracy of geographical data, both for callouts and in the UI
  3. Get feedback on location/heading and audio beacons
  4. We want to measure map tile consumption and UI performance
  5. GUI accessibility testing. There have been a large number of accessibility improvements made to the GUI.

It’s not yet ready for real use in that it has had very little real world testing. For any issues found, or questions you have, please open an issue on the github page.

Features

Onboarding screens

These are based on the iOS screens and guide the user through language selection, permissions, and beacon style selection.

Home screen with UI map

Unlike iOS, a long press on the map brings up the Location Details screen which is central to the UI. As on iOS that screen allows

Clickable items on the home screen that are implemented are:

Soundscape service

This runs even when the phone is locked. It means that a beacon can be set or a route played and then the phone locked. The audio beacon will continue to sound. The service can be stopped and restarted by entering and exiting Sleep mode. The service is responsible for the audio beacon play out and the audio callouts. The heading logic is similar to iOS which means that when the phone is locked the heading is based on the current direction of travel. If the phone is unlocked - or is locked and held flat in front of the user - then the heading used is the direction that the phone is pointing in.

Some of the options within the Menu have been implemented:

Opening the app

The main way that a user might open the app is by tapping on its icon. However, there are other ways to do it:

Work in progress

Features currently in progress:

Testing guidance

We’re interested in all feedback, but we aren’t visually impaired and so particularly value usability feedback - especially if we fall short compared with the iOS Soundscape app.

A suggested “smoke test” has a list of features to test and how.