Anton-V-K
commented
9 months ago I guess, introducing profiles support will require a lot of refactoring. I would consider the approach based on a customizable widget to start the tracking service with user-provided parameters. Possible list of parameters to customize via the widget:
- Location accuracy
- Frequency
- Distance
- Angle
And it would be handy to support customizable look (icon, color, etc.) for such widgets.
I use the client for different purposes, like riding my bike, snowboarding, driving or tracking a flight. All purposes require different settings when to store a position (duration/distance) to create an accurate recording without wasting database space.
It would be great if the client would support a set of 5-10 predefined and custom nameable profiles which can selected just before starting recording. The name of the profile should be visible also as a reminder which parameter set is active.
No alternatives, the current setup leads sometimes to wrong parameters because they are only shown when selecting them for a change and thus a too detailed or too less detailed recording.