-
Notifications
You must be signed in to change notification settings - Fork 68
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
Add preload
, mayLaunchUrl
, preFetch
, warmUp
apis.
#210
Comments
Thank you for your proposal regarding optimization options for I agree that providing these optimization features could enhance the user experience by improving the performance of Custom Tabs.
I plan to start implementing the following optimization features in the plugin:
Since the Please note that because these features are implemented differently on each platform, |
Thanks for taking the suggestion I will wait for these implementations. |
I have released the first version supporting performance optimization features, 2.2.0-dev.1. Please feel free to provide feedback. |
Thanks for adding these features. I will now use it is in my app. |
As part of the optimization for CustomTabs these methods are needed for pre-optimizations for the custom-tabs.
preload
: Load the url in a custom-tab in advance through this method so that when cutom tab is opened it is more faster to load webpage.mayLaunchUrl
: Can check and pre-establish connections likeDNS
,TLS
,TCP
etc. and what are needed by browser.preFetch
: Load the webpage in advance like anhttp.get
request so that some static content and dns, tls, tcp are cached .warmUp
: To open the browser in advance for custom tabs.As we need CustomTabs because we want to customize and improve the URL launching experience or else we can use the normal
url_launcher
so for the further optimization and better url opening experience these methods are required.Please share your thoughts.
The text was updated successfully, but these errors were encountered: