Child Application Developer Tool With Configuration-Based Runtime Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing mini programs for terminals requires significant manpower and device resources, resulting in high costs due to the need for dedicated developer tools.

Innovation Solution

A child application development method and apparatus that utilizes a native child application developer tool with extensions to create a child application running environment, allowing for development processing without the need to develop a new native tool for each parent application, by obtaining and loading a child application base library.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a dedicated developer tool is developed for each parent application, then the child application can be developed specifically for that parent application, but a large quantity of manpower and device resources need to be consumed, resulting in relatively high costs

Engineering Contradiction:
Improvecustomization for parent applicationVSAvoiddevelopment tool
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a common developer tool that can serve multiple parent applications. Instead of developing separate dedicated tools for each parent application, a single developer tool is designed with the capability to work with different parent applications through configuration files, thereby reducing the need for multiple specialized tools and lowering development costs while maintaining adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies segmentation by separating the developer tool into modular components: a common developer tool framework and application-specific configuration files. This segmentation allows the core functionality to be reused across different parent applications while still enabling customization through configuration, thus avoiding the need to develop entirely separate tools for each application.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a dedicated developer tool is developed for each parent application, then the child application development can be tailored to specific parent application requirements, but a large quantity of manpower and device resources need to be consumed

Engineering Contradiction:
Improvedevelopment capabilityVSAvoidmanpower and device resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements universality by designing a common developer tool that can be used across multiple parent applications. This single tool incorporates universal functionalities that work with different parent applications, eliminating the need to allocate separate manpower and device resources for developing and maintaining multiple dedicated tools, thereby reducing overall resource consumption while preserving development capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies discarding and recovering by eliminating the need to create new dedicated tools for each parent application. Instead, the system recovers and reuses the common developer tool for each new parent application by loading appropriate configuration files, thus avoiding redundant resource consumption associated with developing and maintaining multiple separate tools.

Inventive Principle:
Principle #34Discarding and recovering

3Reliability

If a native child application developer tool is used for a first parent application, then the tool is optimized for that specific application, but it cannot be used for a second parent application without developing a new native tool

Engineering Contradiction:
Improvedevelopment tool performanceVSAvoidtool compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies universality by creating a common developer tool that maintains reliable performance across multiple parent applications. The tool achieves this by loading parent-application-specific configuration files that contain optimized settings and parameters for each application, thereby preserving the reliability benefits of dedicated tools while extending adaptability to work with multiple different parent applications through a single unified tool.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies parameter changes by using configuration files to dynamically adjust tool parameters and settings based on the target parent application. Instead of requiring different native tools for different applications, the common developer tool changes its operational parameters by loading appropriate configuration files, thus maintaining optimized performance for each specific application while preserving tool compatibility across multiple applications.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12159124B2Child application development tool
Publication Date: 2024.12.03 TENCENT TECHNOLOGY (SHENZHEN) CO LTD
  • US12159124B2 patent drawing
  • US12159124B2 patent drawing
  • US12159124B2 patent drawing

AI summary

In a method for developing a child application, an interface of a child application developer tool is displayed. The child application developer tool is configured to provide a plurality of child application development modes. Each of the child application development modes is associated with a different run-time environment. A user selection of one of the plurality of child application development modes is received via the interface. Based on the selected one of the plurality of child application development modes, development mode information of a parent application that is associated with the one of the plurality of child application development modes is obtained. The run-time environment of the parent application is created based on the obtained application development mode information. At least one of code editing or code debugging of the child application is performed via the child application developer tool.