Update LauncherActivity to work well in "Single Activity TWA" mode The changes are: 1) LauncherActivity should reuse session id in order to route new View intents to existing TWA. 2) Intent flags are not needed, as they are added in http://crrev.com/c/1349653 (and without that CL they don't work anyway). 3) LauncherActivity closes when user returns back to it after closing a TWA. 4) Service connection is kept alive until onDestroy instead of onStop, so that clients can keep communicating with TWA while in background, should they write an extended LauncherActivity. 5) Updated javadocs. Companion CL: http://crrev.com/c/1349653 Bug: 907796 Change-Id: Iadd28a407129757da85932722d691d777e9868fe Reviewed-on: https://chromium-review.googlesource.com/c/1349363 Reviewed-by: Benoit L <lizeb@chromium.org> Reviewed-by: Peter Conn <peconn@chromium.org> Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Pavel Shmakov <pshmakov@chromium.org>
Chrome Custom Tabs provides a way for an application to customize and interact with a Chrome Activity on Android. This makes the web content feel like being a part of the application, while retaining the full functionality and performance of a complete web browser.
Using Custom Tabs should be easy. This repository hosts examples and in-depth documentation. The examples are importable as projects into the Android Studio.
We want to hear your feedback! Please create bugs and start discussions using this template. Please use the template for any issues related to the Custom Tabs APIs, their implementation in Chrome, the examples in this repository, and related functionality of the Android Support Library.
Note: we know that the GitHub issue tracker is great! However, since Custom Tabs is mostly driven by Chrome developers, and we want to keep all bugs in one place, we prefer the Chromium issue tracker at the moment.
We accept contributions to Custom Tabs examples and documentation. Please see our contributor's guide.