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

Move towards being a single activity app #1277

Open
veyndan opened this issue Oct 9, 2019 · 0 comments
Open

Move towards being a single activity app #1277

veyndan opened this issue Oct 9, 2019 · 0 comments

Comments

@veyndan
Copy link
Collaborator

veyndan commented Oct 9, 2019

Simplifying the lifecycle of the app to just be a single activity should help to significantly mitigate the prevalence of random crashes due to the entanglement of the fragment and activity lifecycles. The use of a single activity is recommended by Google, and the code should be migrated to use a single activity and multiple fragments.

Obviously, migrating the whole app in one fell swoop to a single activity would be insanely difficult. I'm envisioning that we slowly migrate over until we eventually have migrated to a single activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant