You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: