Integration of content in non-browser applications

1. A computer-implemented method comprising:

rendering application content and a link to web content on a user interface of a non-browser application executable by a mobile computing device;

sending, by the non-browser application, a pre-intent request to preload the web content in a browser application executable by the mobile computing device, the pre-intent request including information for determining the web content to be preloaded, the information including at least one of the application content viewed by a user of the non-browser application or input entered by the user in the non-browser application;

sending, by the non-browser application, an intent request to an application programming interface (API) of the browser application in response to an indication that the link has been selected, the pre-intent request or the intent request including a customization parameter to customize a browser tab of the browser application; and

rendering a customized browser tab of the browser application within the user interface of the non-browser application in accordance with the customization parameter such that the application content is replaced with the web content within the customized browser tab,

wherein the customized browser tab is associated with a browser assist layer configured to provide the non-browser application access to one or more features of the browser application.

2. The computer-implemented method of claim 1 , wherein the customization parameter defines a transition animation feature for transitioning from the application content to the customized browser tab within the user interface of the non-browser application.

3. The computer-implemented method of claim 1 , wherein the pre-intent request is sent to the API of the browser application prior to receipt of the indication that the link has been selected.

4. The computer-implemented method of claim 1 , wherein the customization parameter defines an aesthetic element on the customized browser tab.

5. The computer-implemented method of claim 1 , wherein the customization parameter defines a custom user interface (UI) element for an action associated with the non-browser application, the custom UI element being included within a menu associated with the browser application.

6. The computer-implemented method of claim 1 , wherein the one or more features of the browser application include a browser cookie jar, a browsing history, and a language translation service.

7. The computer-implemented method of claim 1 , further comprising:

rendering a security state icon in the customized browser tab within the user interface of the non-browser application.

8. A non-transitory computer readable medium having instructions stored thereon, the instructions, when executed by at least one processor of a mobile computing device, cause the mobile computing device to:

render application content and a link to web content on a user interface of a non-browser application executable by the mobile computing device;

send, by the non-browser application, a pre-intent request to preload the web content in a browser application executable by the mobile computing device, the pre-intent request including information for determining the web content to be preloaded, the information including at least one of the application content viewed by a user of the non-browser application or input entered by the user in the non-browser application;

send, by the non-browser application, an intent request to an application programming interface (API) of the browser application in response to an indication that the link has been selected, the pre-intent request or the intent request including a customization parameter to customize a browser tab of the browser application; and

render a customized browser tab of the browser application within the user interface of the non-browser application in accordance with the customization parameter such that the application content is replaced with the web content within the customized browser tab,

wherein the customized browser tab is associated with a browser assist layer configured to provide the non-browser application access to one or more features of the browser application.

9. The non-transitory computer readable medium of claim 8 , wherein the customization parameter defines a transition animation feature for transitioning from the application content to the customized browser tab within the user interface of the non-browser application.

10. The non-transitory computer readable medium of claim 8 , wherein the pre-intent request is sent to the API of the browser application prior to receipt of the indication that the link has been selected.

11. The non-transitory computer readable medium of claim 8 , wherein the customization parameter defines an aesthetic element on the customized browser tab.

12. The non-transitory computer readable medium of claim 8 , wherein the customization parameter defines a custom user interface (UI) element for an action associated with the non-browser application, the custom UI element being included within a menu associated with the browser application.

13. The non-transitory computer readable medium of claim 8 , wherein the one or more features of the browser application include a browser cookie jar, a browsing history, and a language translation service.

14. The non-transitory computer readable medium of claim 8 , wherein the instructions include instructions that when executed by the at least one processor cause the mobile computing device to:

render a security state icon in the customized browser tab within the user interface of the non-browser application.

15. An apparatus comprising:

at least one processor; and

a non-transitory computer readable medium including executable instructions stored thereon, the instructions, when executed by at least one processor cause the at least one processor to:

render application content and a link to web content on a user interface of a non-browser application executable by a mobile computing device;

send a pre-intent request to preload the web content in a browser application executable by the mobile computing device, the pre-intent request including information for determining the web content to be preloaded, the information including at least one of the application content viewed by a user of the non-browser application or input entered by the user in the non-browser application;

send an intent request to an application programming interface (API) of the browser application in response to an indication that the link has been selected, the pre-intent request or the intent request including a customization parameter to customize a browser tab of the browser application; and

render a customized browser tab of the browser application within the user interface of the non-browser application in accordance with the customization parameter such that the application content is replaced with the web content within the customized browser tab,

wherein the customized browser tab is associated with a browser assist layer configured to provide the non-browser application access to one or more features of the browser application.

16. The apparatus of claim 15 , wherein the features of the browser application include a browser cookie jar, a browsing history, and a language translation service.

17. The apparatus of claim 15 , wherein the instructions include instructions that when executed by the at least one processor cause the at least one processor to:

render a security state icon in the customized browser tab within the user interface of the non-browser application.

18. A computer-implemented method comprising:

rendering application content and a link to web content on a user interface of a non-browser application executable by a mobile computing device;

sending, by the non-browser application, a pre-intent request to preload the web content in a browser application executable by the mobile computing device, the pre-intent request including information for determining the web content to be preloaded, the information including at least one of the application content viewed by a user of the non-browser application or input entered by the user in the non-browser application;

sending, by the non-browser application, an intent request to an application programming interface (API) of the browser application in response to an indication that the link has been selected, the pre-intent request or the intent request including a customization parameter to customize a browser tab of the browser application; and

rendering a customized browser tab of the browser application within the user interface of the non-browser application in accordance with the customization parameter such that the application content is replaced with the web content within the customized browser tab,

wherein the customization parameter defines a custom user interface (UI) element for an action associated with the non-browser application, the custom UI element being included within a menu associated with the browser application.