I've been working on an app now and am nearing the end of my venture. I, like many others, have run into the fact that the use case of background activities is extremely limited and would like to know if there is some way to work around my problem. I'd like to be able to do the following thing:
1. Start an activity/session/start recording a fit file
2. Do some stuff in-app
3. Timer gets started
4. Leave app during timer and do something like adjust music ( pause for example )/change song or volume, read a text message, whatever
5. Come back in one way or another and complete the activity
Is this possible? I don't want to restart the activity during this process because I want one activity posted to Connect at the end. Pausing would also be a non-preferred solution as well because presumably there would be a discontinuity in heart rate data in the fit file but i would be better than nothing. I can't find anywhere in the documentation that really explains what exactly happens when you leave an APP when a fit file is recording.
Also I'd like it to prompt the user to jump back to the timer when it's up, but what I've gathered is that won't work properly if the timer is ever < 5 minutes long.
The main point of my app is being able to ditch the phone during an activity. Music storage and manipulation on the watch is the cornerstone of that goal.
