AUTOMATIC PERSONALIZATION OF DOWNLOADABLE MOBILE APPS

• US 20130124606A1
• Filed: 11/14/2011
• Published: 05/16/2013
• Est. Priority Date: 11/14/2011
• Status: Abandoned Application

• Current Assignee: Boopsie Incorporated
• Original Assignee: Boopsie Incorporated
• Inventors: Carpenter, G. Gregory, Kay, Timothy L.
• Application Number:
  US13/295,748
• Publication Number:
  US 20130124606A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

The present invention greatly simplifies the process of downloading and personalizing a mobile app by employing a unique code or “User ID” that associates the user with the mobile app. This User ID enables the mobile app to personalize itself automatically—i.e., without requiring the user to enter login information. To overcome the obstacle of providing the mobile app with access to the User ID, the invention existing web browser functionality is leveraged by employing a “cookie” into which the User ID is stored, and from which it is retrieved by an app server after the mobile app has been downloaded and initially launched by the user, thereby enabling the app server to provide the user with a personalized experience automatically. The app server sends the User ID to the mobile app, which stores it to enable a personalized experience whenever the user subsequently invokes the mobile app.

Claims

1. A method for downloading and automatically personalizing an application, the method including the following steps:

(a) invoking a first link on a client device to open a web browser that accesses a web server on a first server device, the first link including a User ID identifying the user of the client device;

(b) receiving the User ID on the web server and instructing the web browser to store a cookie on the client device, wherein the cookie contains the User ID and is accessible by the web browser;

(c) redirecting the web browser to access a second server device and download the application from the second server device onto the client device;

(d) invoking the application for the first time after being downloaded to the client device, wherein the application opens the web browser with a second link, causing the web browser to retrieve the cookie and access the web server on the first server device; and

(e) receiving the cookie on the web server and reinvoking the application on the client device, employing the User ID to provide the user with a personalized experience.