PREVIEW AND PUBLISHING OF MOBILE APPLICATIONS

• US 20170308368A1
• Filed: 04/22/2016
• Published: 10/26/2017
• Est. Priority Date: 04/22/2016
• Status: Active Grant

• Current Assignee: Kony, Inc. (Temenos AG)
• Original Assignee: Kony, Inc. (Temenos AG)
• Inventors: TREVATHAN, Matthew B., KATZ, Keith, TERRY, Matthew A.
• Granted Patent: US 10,740,080 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

The present disclosure relates to mobile applications and, more particularly, to systems and processes of automated application publishing using back end systems. A method is implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium and having programming instructions operable to: automatically generating a unique identification for each version of an app uploaded to a back end system; and uploading the app and its collateral with the unique identification to one or more management instances which are compatible with the back end system.

Claims

1. A method implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions operable to:

automatically generating a unique identification for each version of an app uploaded to a back end system; and

uploading the app and its collateral with the unique identification to one or more management instances which are compatible with the back end system.

2. The method of claim 1, wherein the back end system is a mobile backend as a service (MBaaS).

3. The method of claim 1, wherein the app is uploaded to the back end system from a development tool with identification information different than the unique identification generated at the back end system.

4. The method of claim 1, wherein the unique identification is at least one of a bundleID, a custom name and a version number for each version of the app.

5. The method of claim 4, wherein the unique identification is different than an identification of another version of the app such that conflicts are avoided on a mobile device.

6. The method of claim 1, further comprising uploading the app with the unique identification to the one or more management instances with targeting information to one or more user devices and flagged as live.

7. The method of claim 6, further comprising one of prompting a user of the targeted one or more user devices to install the app and automatically uploading the app to the targeted one or more user devices.

8. The method of claim 1, further comprising appending one or more policies to the app at the back end system.

9. The method of claim 8, wherein the one or more policies comprise targeting of users/groups, pre-selection of an expiration date on a per user/group basis, purging of the app, and/or flag the app for immediate expiry.

10. The method of claim 1, wherein the back end system uses APIs to name the app with its unique identification and submit the apps and other collateral and publish the app to the one or more management instances which are compatible with the back end system.

11. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions being executable by a back end system server to cause the back end system server to:

receive one or more mobile apps and collateral information in the back end system server;

generate a unique identification, in the back end system server, for each of the one or mobile apps; and

publish for preview the one or more mobile applications in at least one management instance which is compatible with the back end system server using one or more rest APIs.

12. The computer program product of claim 11, wherein the unique identification generated at the back end system server is different than an identification of a previous app uploaded to the at least one management instance.

13. The computer program product of claim 12, wherein the unique identification is at least one of a bundleID, a custom name and a version number for each version of the one or more mobile apps.

14. The computer program product of claim 13, wherein the one or more apps are publish for preview to the at least one management instance with targeting already designated and flagged as live.

15. The computer program product of claim 13, wherein program instructions are executable to cause the back end system server to append policies to the one or more mobile apps.

16. The computer program product of claim 15, wherein the one or more policies comprise targeting of users/groups, pre-selection of an expiration date on a per user/group basis, purging of the app, and/or flag the app for immediate expiry.

17. The computer program product of claim 11, wherein the back end system server

18. A system comprising:

a CPU, a computer readable memory and a computer readable storage medium;

program instructions to automatically generate a unique identification for an app and its collateral that is uploaded to an enterprise system;

program instructions to publish the app and its collateral with the unique identification in a management instance which is compatible with the enterprise system through a catalog of APIs; and

program instructions to flag the app as live for publishing to one or more targeted devices as defined by an administrator of the enterprise system,

wherein the program instructions are stored on the computer readable storage medium for execution by the CPU via the computer readable memory.

19. The system of claim 18, wherein the unique identification is bundleID, custom name and a version number.

20. The system of claim 18, wherein the unique identification prevents conflicts between versions of a same app on a mobile device.