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

Make Lynket implement Custom Tab protocol by itself. #74

Open
arunkumar9t2 opened this issue Feb 20, 2018 · 0 comments
Open

Make Lynket implement Custom Tab protocol by itself. #74

arunkumar9t2 opened this issue Feb 20, 2018 · 0 comments

Comments

@arunkumar9t2
Copy link
Owner

arunkumar9t2 commented Feb 20, 2018

Even though Lynket was meant to allow apps to use Custom Tabs by default, it never registered as a Custom Tab provider itself.

Make it implement Custom Tab protocol leads to lot of interesting advances. For example, we could use mayLaunchUrl to preload web site metadata/amp/article etc.

On a more important note, we can even do a pass through like functionality, where we can take the Bundle provided by client app and forward it to desired Custom Tab provider. This is useful for some users who prefer Lynket not take over if the app already implements CCCT.

@arunkumar9t2 arunkumar9t2 added this to Ready for Development in Lynket Development Aug 15, 2018
@arunkumar9t2 arunkumar9t2 changed the title Make Chromer implement Custom Tab protocol by itself. Make Lynket implement Custom Tab protocol by itself. Sep 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Lynket Development
  
Ready for Development
Development

No branches or pull requests

1 participant