Shim Application for Mobile Device Content Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Delivering content in an appropriate format to mobile devices with varying features, such as different web browsers, is challenging due to the need for constant updates of user agent repositories or requiring mobile devices to contain all possible libraries for various browser vendors, which is burdensome.
Innovation Solution
A shim application is provided to detect the capabilities of the mobile device and include this information in the request header, allowing the content server to generate and transmit content in a format compliant with the device's capabilities, ensuring appropriate display.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If the repository mapping user agent to features is constantly updated, then the content delivery accuracy is improved, but the maintenance complexity and time cost increase
Solution Approach 1:
The mobile device autonomously detects and reports its own capabilities through the shim application and capability detection module, eliminating the need for manual repository updates. The device self-identifies its browser type, screen resolution, and other features, making the system self-maintaining and removing the time cost of constant repository updates.
Solution Approach 2:
The shim application acts as an intermediary layer between the mobile device and the content delivery system. It captures device capabilities and transmits them to the server, serving as a mediator that eliminates the need for direct repository maintenance while ensuring accurate capability information is conveyed for content formatting.
2Adaptability or versatility
If all possible libraries for various mobile browser vendors are contained in mobile devices, then content rendering compatibility is improved, but the device memory consumption and complexity increase
Solution Approach 1:
The capability detection and content formatting logic is extracted from the mobile device and relocated to the server-side. The shim application on the device only needs to detect capabilities and transmit information, while the server handles the complex task of formatting content appropriately. This extraction eliminates the need for devices to store multiple browser libraries.
Solution Approach 2:
The server implements a universal content formatting capability that can adapt to various mobile browser types and configurations. Instead of each device needing specific libraries for different browsers, the server provides a multi-functional formatting system that handles all browser types through a single interface, reducing device memory requirements.
3Manufacturing precision
If content is formatted for each specific mobile device variant, then the content display quality is improved, but the system complexity and update frequency requirements increase
Solution Approach 1:
The system uses parameter-based content formatting where the server receives capability parameters (screen resolution, browser type, etc.) from the shim application and dynamically adjusts content parameters accordingly. This parameter-driven approach maintains high display quality across devices without requiring complex device-specific formatting logic, as the same formatting engine adapts to different parameter sets.
Data Source
AI summary
A method, system and computer program product for delivering tailored specific content to a mobile device. A shim application is provided to the mobile device by a content server after the mobile device visits the content server for the first time. The shim application detects the capabilities of the mobile device, such as the screen size, screen resolution, memory size, browser capabilities, etc. The shim application then includes such information in the header of the requests, such as a request for content, sent from the mobile device to the content server. The content server then generates the requested content in the appropriate format based on the information provided in the header. In this manner, the content server will now be able to ensure that the content provided by the content server for a particular mobile device will be appropriately displayed on the mobile device.