Skip to content
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

Organize fragments based on user navigation patterns in journey graph #1213

Closed
abhaysood opened this issue Sep 9, 2024 · 1 comment
Closed
Assignees
Labels
feature-request request for new feature

Comments

@abhaysood
Copy link
Contributor

abhaysood commented Sep 9, 2024

Problem

Journey graph does not reflect navigation pattern of users for single Activity apps which only contain Fragments or ones which heavily rely on Fragments.

Solution

Fragments in journey graph should reflect typical user navigation pattern similar to activities.

Alternatives

If this cannot be constructed automatically based on lifecycle events, we could consider adding manual events (like navigation or screen view events to aid in constructing the graph).

Tasks

  1. Use parent fragment to build journey graph
    BackendAdd fragments in journey graphs #1231
    Androidfeat(android): add parent fragment to fragment lifecycle events #1262
  2. Add screen view event
    Add screen view event #1263
  3. Auto instrument androidx-navigation:fragment library to send screen view events
    Auto instrument androidx-navigation:fragment  #1264
@abhaysood abhaysood added the feature-request request for new feature label Sep 9, 2024
@abhaysood abhaysood added backend backend related and removed backend backend related labels Sep 9, 2024
@abhaysood abhaysood self-assigned this Sep 9, 2024
@abhaysood abhaysood moved this to In Progress in Measure Roadmap Sep 9, 2024
@abhaysood
Copy link
Contributor Author

abhaysood commented Sep 18, 2024

Update Summary

We've been exploring ways to infer the navigation graph using fragment lifecycle events, but the results weren't as reliable as we'd hoped. Instead of shipping something unpredictable, we've decided to take a different approach. We'll automate what we're confident about and give developers more control over the rest of the graph using custom events.
Here's our plan moving forward:

We think this approach will give us more accurate results while keeping things flexible for developers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request request for new feature
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant