Application Distribution System for Seamless Integration and Monetization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for distributing software applications and exchanging data between applications are cumbersome, requiring significant modifications to existing applications and lacking in search engine indexing capabilities, while also failing to effectively implement application metrics and monetization schemes.
Innovation Solution
The Application Distribution and Metrics System (ADMS) enables seamless integration of distributed applications across different platforms without modifying the original application, using an Efficient Hierarchical Data Format (EHDF) for data transmission and providing mechanisms for monetization, metrics gathering, and search engine compatibility through a cross-platform application distribution system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web services protocols (SOAP, WSDL, UDDI) are used for application distribution, then applications can communicate over the Internet, but the system complexity increases significantly and requires additional development effort
Solution Approach 1:
The patent introduces an application distribution system that acts as an intermediary between distributed applications and host applications. This mediator handles the complexity of data format conversion, protocol adaptation, and integration logic, allowing applications to communicate without directly implementing complex web service protocols. The system translates between different data formats and communication styles, reducing the burden on individual applications.
Solution Approach 2:
The application distribution system provides universal support for multiple communication protocols and data formats through a single unified interface. Rather than requiring each application to implement multiple protocol stacks, the distribution system handles SOAP, REST, and other protocols through a common architecture, reducing overall system complexity while maintaining versatility.
2Ease of manufacture
If REST architecture is used for application distribution, then data exchange becomes easier, but non-REST applications require reengineering and additional effort to implement RESTful APIs
Solution Approach 1:
The distribution system serves as a mediator that translates between REST and non-REST communication styles. Non-REST applications can communicate through the distribution system without being reengineered, while the system handles the translation to REST-compatible formats for web-based applications. This eliminates the need for non-REST applications to implement RESTful APIs directly.
Solution Approach 2:
Instead of requiring applications to adapt to REST architecture, the system inverts the approach by having the distribution layer adapt to various application architectures and translate them into REST-compatible communications. This allows legacy and non-REST applications to maintain their original architecture while still benefiting from REST-based distribution.
3Ease of operation
If widget techniques (Javascript, Flash) are used for application distribution, then integration with host web applications becomes easy, but the distributed application must be altered or modified and content is not visible to search engines
Solution Approach 1:
The distribution system introduces an intermediary layer that enables search engine visibility without requiring the distributed application to be a native web widget. The system can serve applications in their original format while providing web-compatible interfaces for search engine indexing, eliminating the need to alter the distributed application into Javascript or Flash widgets.
4Adaptability or versatility
If applications are distributed across different platforms, then application accessibility increases, but integration complexity and platform-specific modifications increase
Solution Approach 1:
The application distribution system provides a universal platform-agnostic interface that handles multiple operating systems, browsers, and device types through a single architecture. The system translates platform-specific requirements into a common internal format, allowing the same distributed application to run across different platforms without platform-specific modifications or increased integration complexity.
Data Source
AI summary
The present invention comprises an application distribution and metrics system as well as an application monetizing system (ADMS). The ADMS incorporates a cross-platform application distribution system and a usage-based and ad-based monetizing system which allows for fine-tuned usage-based pricing schemes to be created based on system-defined metrics and developer-defined metrics, seamless integration of ad-based monetizing, third party participation in monetizing efforts, and a flexible revenue allocation process.