Bubblewrap is a Command Line Interface (CLI) that helps developers to create a Project for an Android application that launches an existing Progressive Web App (PWAs) using a Trusted Web Activity.
Apache License 2.0
2.36k
stars
161
forks
source link
Improving Update Mechanism Handling in LauncherActivity - Force and Optional Update #857
Feature Request: Improved Update Mechanism Handling in LauncherActivity
Is your feature request related to a problem? Please describe.
I implemented a force update and optional update mechanism in LauncherActivity. However, when I press the back button and navigate back to the app, the optional update (which is an activity) goes behind the LauncherActivity. This causes a poor user experience as users do not see the optional update prompt correctly.
Describe the solution you'd like
I would like a solution to handle this issue effectively. Specifically, I need a splash activity in the codebase to manage the update flows better. Alternatively, guidance on how to implement this functionality within the current structure would be appreciated. The solution should ensure that the optional update activity is properly managed and presented to the user, even when navigating back to the app using the back button.
Additional context
Here are some specific details about the current implementation:
The LauncherActivity initiates both force and optional updates.
When the back button is pressed, the optional update activity is pushed behind the LauncherActivity, making it invisible to the user.
Feature Request: Improved Update Mechanism Handling in LauncherActivity
Is your feature request related to a problem? Please describe. I implemented a force update and optional update mechanism in
LauncherActivity. However, when I press the back button and navigate back to the app, the optional update (which is an activity) goes behind theLauncherActivity. This causes a poor user experience as users do not see the optional update prompt correctly.Describe the solution you'd like I would like a solution to handle this issue effectively. Specifically, I need a splash activity in the codebase to manage the update flows better. Alternatively, guidance on how to implement this functionality within the current structure would be appreciated. The solution should ensure that the optional update activity is properly managed and presented to the user, even when navigating back to the app using the back button.
Additional context Here are some specific details about the current implementation:
LauncherActivityinitiates both force and optional updates.LauncherActivity, making it invisible to the user.