Fitness tracker application requirements and architecture

The following list shows the high-level requirements of the fitness tracker application:

1. When the application starts for the first time, it should get the following authorizations from the user:
   1. To read their live fitness data with all the read scopes, using the Sensor API.
   2. To record their fitness data with all the read scopes, using Recording API.
   3. To read their fitness history data with all the read scopes, using History API.
2. The application should list all the available data sources for live data capture using the Sensors API.
3. The application should capture live data from available data sources. It should also allow adding and removing listeners using the Sensors API.
4. The application should list all the active subscriptions with their data types using the Recording API.
5. The application should allow adding and removing of subscriptions for a particular data type using the Recording API.
6. The application should show the history of available...