Server-Based Custom Application Deployment via Configuration Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software application deployment methods require manual installation and updating, which can lead to security issues and compatibility problems across different platforms.
Innovation Solution
A computing system that allows users to design and deploy custom applications without writing code, using a set of design tools to specify functionality, layout, and permissions, and storing configuration data to generate application data dynamically in response to user requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional software applications are installed and run on computing devices, then applications can be executed locally, but security issues and compatibility problems arise across different platforms
Solution Approach 1:
The patent introduces a server as an intermediary between users and applications. Instead of applications running directly on client devices, the server mediates by receiving requests from clients, retrieving appropriate applications from storage, and delivering them dynamically. This intermediary architecture resolves the contradiction by centralizing security control on the server while providing platform-independent access to clients through standard communication protocols.
Solution Approach 2:
The patent segments the application delivery system into separate functional components: a server component for managing applications, a storage component for holding application data, and client components for requesting applications. This segmentation allows each component to be optimized independently - the server handles security and compatibility logic, while clients simply need network connectivity, thereby improving both security and cross-platform compatibility.
2Ease of manufacture
If custom applications are designed without code using design tools, then ease of application creation is improved, but device complexity increases due to configuration data storage and retrieval mechanisms
Solution Approach 1:
The patent uses configuration data as a copy or representation of the application's intended behavior and structure. Instead of storing actual executable code for custom applications, the system stores a simplified configuration data structure that describes what the application should do. This copy approach simplifies the data storage mechanism while enabling complex application behavior to be defined through straightforward configuration files rather than code.
Solution Approach 2:
The patent transforms application creation from a coding process to a parameter configuration process. Design tools allow users to define applications by changing parameters in configuration data (such as function names, display properties, and behavior parameters) rather than writing code. This parameter-based approach reduces the complexity barrier for application creation while maintaining full functionality.
3Adaptability or versatility
If configuration data is stored separately from application code, then update flexibility is improved, but data management complexity increases
Solution Approach 1:
The patent segments application data into two distinct parts: configuration data that describes application behavior and parameters, and actual application code or modules. This segmentation is implemented through separate storage locations and retrieval mechanisms. The configuration data is stored as independent data structures that can be modified without affecting the application code, enabling flexible updates while maintaining manageable data organization through clear separation of concerns.
Data Source
AI summary
Methods, systems, and apparatus, including computer programs encoded on computer-storage media, for development and deployment of custom applications. In some implementations, configuration data that specifies a configuration of application elements is stored. A repository of modules that are used to implement the respective application elements is stored. A request from a client device over a network is received. User interface data for a view of the custom application is generated. The user interface data for the custom application is provided to the client device over the network in response to the request.