Systems and methods for real time version control for integrating updated web-based components with a native application

• US 10,379,846 B1
• Filed: 01/25/2018
• Issued: 08/13/2019
• Est. Priority Date: 01/25/2018
• Status: Active Grant

• Current Assignee: Walmart Apollo, LLC (WalMart Inc.)
• Original Assignee: Walmart Apollo, LLC (WalMart Inc.)
• Inventors: Mercille, Richard, Lemaire, Benoit, Shah, Krunal, Li, Weijie, Ganapathiyadan, Deepu Eswarath, Marulasiddappa, Bharath
• Primary Examiner(s): Lyons, Andrew M.
• Application Number:
  US15/880,217
• Publication Number:
  US 20190227794A1
• Time in Patent Office: 565 Days
• Field of Search: 717120, 717168-178
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• 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
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

An approach is proposed to support version control for integrating updated web-based components with a native application of a mobile device. A new version of a mini app is received at an application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features in JavaScript to be integrated with the native application. Version compatibility checks are performed to confirm that the new version of the mini app only contains native dependencies that match with a version of the native application the version of the mini app depends on. The new version of the mini app is integrated with the native application into the target mobile application if the version compatibility checks pass. Finally, the target mobile application is uploaded to an app store to make the target mobile application available to an end user.

Claims

1. A system to support real time version control for integrating updated web-based components with a native application, comprising:

a computing device configured to;

receive a new version of a JavaScript mini app at a centralized application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features to be deployed to and integrated with the application native to a platform of a mobile device into a target mobile application;

perform a plurality of version compatibility checks between the new version of the mini app and the native application to confirm that the new version of the mini app to be integrated with the native application only contains one or more native dependencies that match with a version of the native application the new version of the mini app depends on;

add native dependencies that are missing from a current version of the mini app to the new version of the mini app based on the version compatibility checks;

publish and integrate the new version of the mini app with the native application into the target mobile application if the version compatibility checks pass;

upload the target mobile application to an app store to make the target mobile application available to an end user.

2. The system of claim 1, wherein:

the platform of the mobile device is iOS or Android.

3. The system of claim 1, wherein said computing device is configured to:

maintain version information of one or more of the target mobile application, the native application, the platform, the mini app and its native dependencies in the application version control module.

4. The system of claim 1, wherein said computing device is configured to:

maintain configurations of the application version control module in a single JavaScript Object Notation (JSON) document.

5. The system of claim 1, wherein said computing device is configured to:

perform the version compatibility checks when a new mini app is to be added to an in-development target mobile application, a new mini app is added to a version of a released target mobile application, when an existing mini app is being removed from the target mobile application, or when the version of the mini app is being updated.

6. The system of claim 5, wherein said computing device is configured to:

perform the version compatibility checks when native dependencies are directly added, updated, or removed in the version of the mini app.

7. The system of claim 1, wherein said computing device is configured to:

enable Over-the-Air (OTA) update to the version of the mini app and/or its native dependencies on the native application, wherein the OTA update happens in real time whenever a new version of the mini app and/or its native dependencies become available without generating another version of a container for the mini app.

8. The system of claim 1, wherein said computing device is configured to:

maintain traceability of the mini app by keeping track of various versions of the mini app delivered to the mobile device and integrated into the target mobile application over time.

9. A computer-implemented method to support cross-platform information exchange mechanism for integration of web-based components with a native application, comprising:

receiving a new version of a JavaScript mini app at a centralized application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features to be deployed to and integrated with the application native to a platform of a mobile device into a target mobile application;

performing a plurality of version compatibility checks between the new version of the mini app and the native application to confirm that the new version of the mini app to be integrated with the native application only contains one or more native dependencies that match with a version of the native application the new version of the mini app depends on;

adding native dependencies that are missing from a current version of the mini app to the new version of the mini app based on the version compatibility checks;

publishing and integrating the new version of the mini app with the native application into the target mobile application if the version compatibility checks pass;

uploading the target mobile application to an app store to make the target mobile application available to an end user.

10. The computer-implemented method of claim 9, further comprising:

maintaining version information of one or more of the target mobile application, the native application, the platform, the mini app and its native dependencies in the application version control module.

11. The computer-implemented method of claim 9, further comprising:

performing the version compatibility checks when a new mini app is to be added to an in-development target mobile application, a new mini app is added to a version of a released target mobile application, when an existing mini app is being removed from the target mobile application, or when the version of the mini app is being updated.

12. The computer-implemented method of claim 11, further comprising:

performing the version compatibility checks when native dependencies are directly added, updated, or removed in the version of the mini app.

13. The computer-implemented method of claim 9, further comprising:

enabling Over-the-Air (OTA) update to the version of the mini app and/or its native dependencies on the native application, wherein the OTA update happens in real time whenever a new version of the mini app and/or its native dependencies become available without generating another version of a container for the mini app.

14. The computer-implemented method of claim 9, further comprising:

maintaining traceability of the mini app by keeping track of various versions of the mini app delivered to the mobile device and integrated into the target mobile application over time.

15. A non-transitory computer readable storage medium having software instructions stored thereon, wherein when executed by at least one processor, the computer-executable instructions cause the at least one processor to:

receive a new version of a JavaScript mini app at a centralized application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features to be deployed to and integrated with the application native to a platform of a mobile device into a target mobile application;

perform a plurality of version compatibility checks between the new version of the mini app and the native application to confirm that the new version of the mini app to be integrated with the native application only contains one or more native dependencies that match with a version of the native application the version of the new mini app depends on;

add native dependencies that are missing from a current version of the mini app to the new version of the mini app based on the version compatibility checks;

publish and integrate the new version of the mini app with the native application into the target mobile application if the version compatibility checks pass;

upload the target mobile application to an app store to make the target mobile application available to an end user.

16. The non-transitory computer-readable storage medium of claim 15, wherein the computer-executable instructions further cause the at least one processor to maintain version information of one or more of the target mobile application, the native application, the platform, the mini app and its native dependencies in the application version control module.

17. The non-transitory computer-readable storage medium of claim 15, wherein the computer-executable instructions further cause the at least one processor to perform the version compatibility checks when a new mini app is to be added to an in-development target mobile application, a new mini app is added to a version of a released target mobile application, when an existing mini app is being removed from the target mobile application, or when the version of the mini app is being updated.

18. The non-transitory computer-readable storage medium of claim 17, wherein the computer-executable instructions further cause the at least one processor to perform the version compatibility checks when native dependencies are directly added, updated, or removed in the version of the mini app.

19. The non-transitory computer-readable storage medium of claim 15, wherein the computer-executable instructions further cause the at least one processor to enable Over-the-Air (OTA) update to the version of the mini app and/or its native dependencies on the native application, wherein the OTA update happens in real time whenever a new version of the mini app and/or its native dependencies become available without generating another version of a container for the mini app.

20. The non-transitory computer-readable storage medium of claim 15, wherein the computer-executable instructions further cause the at least one processor to maintain traceability of the mini app by keeping track of various versions of the mini app delivered to the mobile device and integrated into the target mobile application over time.