-
-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement request: Notification granularity #60
Labels
Projects
Comments
That sounds very reasonable! I think this would make sense to split between debug notifications and normal notifications. Trips auto-ending would be a normal notification, but tracking start/stop and others would be debug. Thanks for the suggestion! I'm due to push an update to the store soon so I will make sure to include this. Thanks! |
That's awesome timing! Thanks for taking this request... 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Aaron!
I'm wondering if there can be some added granularity to notifications in the Overland app. Specifically, I'm looking to not get notifications whenever tracking stops or starts with geofencing, but absolutely to get notifications for trip auto-ending etc. Do you think that would make sense?
I know about negative in Obj C and Swift, else I'd attempt to send you a pull request.
The text was updated successfully, but these errors were encountered: