Skip to content

[Feature request]: Ability to detect traffic incidents being shown #520

@IvelinKrastev

Description

@IvelinKrastev

Is there an existing issue for this?

  • I have searched the existing issues

Use case

In our app, we utilize the Flutter Navigation SDK in conjunction with the Android for Cars App Library templates to provide a navigation experience on Android Auto.

During testing, we observed that when an incident alert (for example, “Congestion ahead”, “Crash reported”, etc) is shown by the host or navigation system on Android Auto, it is rendered underneath our TravelEstimate widget from the SDK. This results in the incident alert being partially or fully hidden, which is a UI correctness and safety concern and may cause Play Store or certification rejection.

Image

Proposal

An event or callback in the Flutter Navigation SDK to allow detection when a navigation alert (incident / congestion / other road hazard) is displayed on the screen. For example: onNavigationAlertShown(AlertInfo alert) and onNavigationAlertDismissed() or similar.

Why is this important

  1. Overlapping UI in the Android Auto environment is a potential driver distraction and compliance risk.
  2. Certification for Android Auto navigation apps requires correct behaviour of alerts and UI cards; if a third-party app’s TravelEstimate or other card overlaps a system alert, this may lead to rejection.
  3. Without the detection or API, it is difficult for app developers to ensure correct layering or behaviour dynamically.

Questions

  1. Does the SDK currently have any mechanism to detect when a navigation alert is shown on Android Auto (or Android for Cars) screen?
  2. If yes, please describe the API / callback signature.
  3. If not, is the feature on the roadmap?
  4. How are “travel incident alerts” shown in the Android for Cars environment? Are they part of the template (e.g., NavigationTemplate) or handled by the host only?
  5. What is the recommended approach from the SDK perspective for avoiding overlap (e.g., hide card, shift card, reduce size, etc.)?

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions