Dynamic Client App Activity via Server-Generated Config Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client applications require significant updates and testing to change user interaction responses, leading to inefficiencies and errors due to hardcoded logic, making it difficult to adapt to new content formats and user interactions.
Innovation Solution
A server-generated config file dynamically specifies actions for client devices, allowing flexible and efficient response to user interactions without requiring application updates, enabling rapid changes and reducing client-side complexity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hardcoded logic is used in client applications to specify user interaction responses, then the application structure is simple and reliable, but the adaptability to new content formats and user interactions is poor, requiring significant updates and testing
Solution Approach 1:
The patent applies dynamics by replacing static hardcoded logic with dynamic server-generated config files. The config files are generated on-demand by servers based on current content formats and interaction rules, allowing the client application to adapt to changes without requiring updates. This resolves the contradiction by making the system adaptable while keeping the client-side logic simple and unchanged.
Solution Approach 2:
The patent introduces config files as an intermediary between the server and client application. These config files mediate the communication by carrying all necessary interaction rules and content format specifications from the server to the client, eliminating the need for hardcoded logic in the application while maintaining simplicity on the client side.
2Productivity
If traditional application updates are used to change user interaction responses, then the logic can be updated, but the lag time increases and errors are more likely to occur
Solution Approach 1:
The patent applies preliminary action by pre-generating config files on the server before they are needed by the client application. The servers prepare and cache config files in advance, so when the client requests interaction rules, they are already ready and can be delivered immediately without waiting for application updates or extensive testing cycles.
Solution Approach 2:
The system dynamically generates config files on-demand based on current interaction requirements, allowing rapid adaptation to new user interactions without the lag time associated with traditional application updates. The server can generate new config files instantly and serve them to clients, eliminating delays inherent in update deployment processes.
3Adaptability or versatility
If hardcoded logic is used in client applications, then the application is easier to implement, but the flexibility to respond to different content formats is reduced
Solution Approach 1:
The patent uses config files as an intermediary that carries all the logic for handling different content formats and interactions. This intermediary absorbs the complexity of format-specific handling, allowing the client application to remain simple while gaining flexibility through the server-generated config files that adapt to different content types.
Solution Approach 2:
The system changes parameters by generating different config files with different interaction rules and content format specifications based on the current context. When new content formats are introduced, the server generates updated config files with appropriate parameters for those formats, allowing the application to adapt without changing its core implementation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method includes selecting, by one or more servers, a digital component to be presented in an application executed at a client device; obtaining attributes of the digital component, including a destination network location to which the digital component redirects users in response to interaction with the digital component and a reporting network location to which the interaction with the digital component is reported; after selecting the digital component and obtaining the attributes, selecting, based on the obtained attributes, a config file that specifies a set of operations to be performed by the client device that presents the digital component; and transmitting, to the client device, a payload that includes information specifying the digital component to be presented in the application and the config file that, upon execution by the client device, causes the client device to perform the set of operations specified by the config file.