Supplemental Computer Instructions Injection for Mobile Sales Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile applications often lack the capability to integrate sales functionality, requiring developers to invest additional resources and provide SDKs or APIs, which is costly and resource-intensive for sales services.

Innovation Solution

Sales services inject computer instructions into mobile applications to enable sales functionality, eliminating the need for developers to implement sales capabilities themselves, allowing for customizable appearance and interaction with sales servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers integrate sales functionality using SDKs or APIs, then sales functionality is enabled in mobile applications, but the cost and resource investment for developers and sales services increases significantly

Engineering Contradiction:
Improvesales functionality integrationVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the sales functionality code from the SDK/API framework and directly embeds it into the mobile application's executable code. This extraction of the integration layer eliminates the need for developers to implement complex SDK integration, while the sales functionality remains fully operational within the application.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent merges the sales functionality code with the mobile application's core codebase, combining what were previously separate components (application code and sales SDK) into a unified executable. This merging eliminates the boundary between application and sales functionality, simplifying the integration process.

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If developers implement sales capabilities themselves, then customization is possible, but the burden and resource requirements on developers increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent performs preliminary compilation of the sales functionality into the application code during the build process. By pre-integrating and compiling the sales code alongside the application code, the system eliminates the need for developers to perform complex integration tasks, while the resulting executable contains fully customized sales functionality.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If sales services provide comprehensive SDKs and APIs, then functionality is enabled, but the cost and resource investment for sales services increases

Engineering Contradiction:
Improvesales functionalityVSAvoidresource investment
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent enables the mobile application to self-integrate sales functionality through automated compilation processes. The build system automatically incorporates sales code into the application executable without requiring manual SDK integration by developers, eliminating the need for sales services to maintain and distribute complex SDKs.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If developers use SDKs or APIs for sales functionality, then integration is achieved, but the time and effort required for SDK development and education increases

Engineering Contradiction:
Improveintegration easeVSAvoidintegration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent replaces the manual mechanical process of SDK integration with an automated compilation process. Instead of developers manually implementing SDKs and APIs, the build system automatically compiles and integrates sales functionality into the application code, eliminating the time-consuming manual integration steps.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9465592B1Injection of supplemental computer instructions
Publication Date: 2016.10.11 AMAZON TECH INC
  • US9465592B1 patent drawing
  • US9465592B1 patent drawing
  • US9465592B1 patent drawing

AI summary

Application computer instructions can be provided to a publishing server. The publishing service can parse the application computer instructions to identify one or more locations where supplemental computer instructions can be inserted. Metadata about purchasable items can be obtained and the supplemental computer instructions can be written based on the item metadata. The supplemental computer instructions can be inserted into the application computer instructions. A publishable application can be created by compiling the application computer instructions with the inserted supplemental computer instructions.