-
Notifications
You must be signed in to change notification settings - Fork 6
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
destroy
status of a miniapp expected?
#35
Comments
@espinr Thanks for the comparison analysis Open for discussion: which way we prefer?
|
In the case of quick apps, there is a specific Perhaps we can implement a I also understand that most MiniApp user agents perform this removal once the platform meets some criteria (inactivity and/or allocation of resources in the background). The criteria may vary depending on the implementations, so we could specify that the platform SHOULD/MUST terminate the app's execution based on these criteria (to be determined by the concrete implementation). |
During the privacy review, we are asked to clarify the concept of a mini app "session". Since the answer is related to the lifecycle, I wonder how we can define a session regarding app statuses and events.
The concept of a session I'm referring to is the period starting when the app is loaded (after initialization) and finishing when it is destroyed (cache information is removed).
I did a comparison among the different mini app vendors at w3c/miniapp-manifest#56 .
Could we specify anything to clarify when a app is unloaded?
The text was updated successfully, but these errors were encountered: