Provisioning partner aware apps on sandboxed operating systems
First Claim
1. A computer implemented method for transforming a generic build of a mobile app made available by a provider into a partner aware mobile app associated with a specific partner of the provider, on a sandboxed mobile operating system on a mobile computing device, the method comprising the steps of:
- navigating to a website of the specific partner, by a mobile browser on the mobile computing device;
receiving, from the website of the specific partner by the mobile browser, a link to a section of a website of the provider concerning the mobile app, the received link further comprising an identifier of the specific partner;
navigating to the section of the website of the provider concerning the mobile app, by the mobile browser;
providing the identifier of the specific partner to the website of the provider, by the mobile browser;
receiving a cookie containing the identifier of the specific partner and a redirect to a section of an app store concerning the mobile app, from the website of the provider by the mobile browser;
storing the cookie containing the identifier of the specific partner on the mobile computing device, by the mobile browser;
navigating to the section of an app store concerning the mobile app, by the mobile browser, responsive to the received redirect;
downloading the generic build of the mobile app, from the app store to the mobile computing device;
the generic build of the mobile app registering itself with the sandboxed mobile operating system as a protocol handler for a provider specific protocol;
launching the website of the provider, by the generic build of the mobile app;
receiving a redirect to the provider specific protocol, from the website of the provider, wherein the redirect further comprises the identifier of the specific partner as a parameter, the identifier of the specific partner having been retrieved from the cookie on the mobile device by the website of the provider;
the generic build of the mobile app executing on the mobile computing device as the registered protocol handler for the provider specific protocol, responsive to the redirect to the provider specific protocol;
reading the identifier of the specific partner from the redirect to the provider specific protocol, by the mobile app; and
using the identifier of the specific partner to provide features specific to the partner, by the mobile app on the sandboxed mobile operating system on the mobile computing device.
5 Assignments
0 Petitions
Accused Products
Abstract
A mobile app is provisioned with an identifier of a specific partner of an app provider, on a sandboxed OS on a mobile device. A link to the app provider'"'"'s website containing the partner ID is received from the partner'"'"'s website. The user navigates to the provider'"'"'s website, which writes a cookie containing the partner ID and redirects to an app store. The app is downloaded to the mobile device, and registers itself with the OS as a protocol handler for a provider specific protocol. The app launches the provider'"'"'s website, which retrieves the partner ID from the cookie, and returns a redirect to the provider specific protocol. The redirect contains the partner ID, and causes the app to execute as the registered protocol handler for the provider specific protocol. The app reads the partner ID from the redirect, and uses it to provide partner specific features.
41 Citations
17 Claims
-
1. A computer implemented method for transforming a generic build of a mobile app made available by a provider into a partner aware mobile app associated with a specific partner of the provider, on a sandboxed mobile operating system on a mobile computing device, the method comprising the steps of:
-
navigating to a website of the specific partner, by a mobile browser on the mobile computing device; receiving, from the website of the specific partner by the mobile browser, a link to a section of a website of the provider concerning the mobile app, the received link further comprising an identifier of the specific partner; navigating to the section of the website of the provider concerning the mobile app, by the mobile browser; providing the identifier of the specific partner to the website of the provider, by the mobile browser; receiving a cookie containing the identifier of the specific partner and a redirect to a section of an app store concerning the mobile app, from the website of the provider by the mobile browser; storing the cookie containing the identifier of the specific partner on the mobile computing device, by the mobile browser; navigating to the section of an app store concerning the mobile app, by the mobile browser, responsive to the received redirect; downloading the generic build of the mobile app, from the app store to the mobile computing device; the generic build of the mobile app registering itself with the sandboxed mobile operating system as a protocol handler for a provider specific protocol; launching the website of the provider, by the generic build of the mobile app; receiving a redirect to the provider specific protocol, from the website of the provider, wherein the redirect further comprises the identifier of the specific partner as a parameter, the identifier of the specific partner having been retrieved from the cookie on the mobile device by the website of the provider; the generic build of the mobile app executing on the mobile computing device as the registered protocol handler for the provider specific protocol, responsive to the redirect to the provider specific protocol; reading the identifier of the specific partner from the redirect to the provider specific protocol, by the mobile app; and using the identifier of the specific partner to provide features specific to the partner, by the mobile app on the sandboxed mobile operating system on the mobile computing device. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. At least one non-transitory computer readable-storage medium for transforming a generic build of a mobile app made available by a provider into a partner aware mobile app associated with a specific partner of the provider, on a sandboxed mobile operating system on a mobile computing device, the at least one non-transitory computer readable-storage medium storing computer executable instructions that, when loaded into computer memory and executed by at least one processor of a computing device, cause the computing device to perform the following steps:
-
navigating to a website of the specific partner, by a mobile browser on the mobile computing device; receiving, from the website of the specific partner by the mobile browser, a link to a section of a website of the provider concerning the mobile app, the received link further comprising an identifier of the specific partner; navigating to the section of the website of the provider concerning the mobile app, by the mobile browser; providing the identifier of the specific partner to the website of the provider, by the mobile browser; receiving a cookie containing the identifier of the specific partner and a redirect to a section of an app store concerning the mobile app, from the website of the provider by the mobile browser; storing the cookie containing the identifier of the specific partner on the mobile computing device, by the mobile browser; navigating to the section of an app store concerning the mobile app, by the mobile browser, responsive to the received redirect; downloading the generic build of the mobile app, from the app store to the mobile computing device; the generic build of the mobile app registering itself with the sandboxed mobile operating system as a protocol handler for a provider specific protocol; launching the website of the provider, by the generic build of the mobile app; receiving a redirect to the provider specific protocol, from the website of the provider, wherein the redirect further comprises the identifier of the specific partner as a parameter, the identifier of the specific partner having been retrieved from the cookie on the mobile device by the website of the provider; the generic build of the mobile app executing on the mobile computing device as the registered protocol handler for the provider specific protocol, responsive to the redirect to the provider specific protocol; reading the identifier of the specific partner from the redirect to the provider specific protocol, by the mobile app; and using the identifier of the specific partner to provide features specific to the partner, by the mobile app on the sandboxed mobile operating system on the mobile computing device. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A computer implemented method for providing a generic build of a mobile app made available by a provider with specific variable data, on a sandboxed mobile operating system on a mobile computing device, the method comprising the steps of:
-
navigating to a website associated with the provision of the specific data, by a mobile browser on the mobile computing device; receiving, from the website associated with the provision of the specific data by the mobile browser, a link to a section of a website of the provider concerning the mobile app, the received link further comprising the specific data; navigating to the section of the website of the provider concerning the mobile app, by the mobile browser; providing the specific data to the website of the provider, by the mobile browser; receiving a cookie containing the specific data and a redirect to a section of an app store concerning the mobile app, from the website of the provider by the mobile browser; storing the cookie containing the specific data on the mobile computing device, by the mobile browser; navigating to the section of an app store concerning the mobile app, by the mobile browser, responsive to the received redirect; downloading the generic build of the mobile app, from the app store to the mobile computing device; the generic build of the mobile app registering itself with the sandboxed mobile operating system as a protocol handler for a provider specific protocol; launching the website of the provider, by the generic build of the mobile app; receiving a redirect to the provider specific protocol, from the website of the provider, wherein the redirect further comprises the specific data as a parameter, the specific data having been retrieved from the cookie on the mobile device by the website of the provider; the generic build of the mobile app executing on the mobile computing device as the registered protocol handler for the provider specific protocol, responsive to the redirect to the provider specific protocol; reading the specific data from the redirect to the provider specific protocol, by the mobile app; and using the specific data to provide specific corresponding features, by the mobile app on the sandboxed mobile operating system on the mobile computing device. - View Dependent Claims (14, 15, 16, 17)
-
Specification