Device Adaptive Architecture for Multi-Platform Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of the Global Mobile Network, with numerous wireless device operating systems and platforms, makes it challenging to deploy functionally rich network applications across a wide variety of mobile devices, as existing technologies require extensive porting or rewriting for each platform, leading to high costs and inefficiencies.

Innovation Solution

The Device Adaptive Architecture (DAA) automatically determines device attributes, selects compatible software components, and combines them to generate customized applications, enabling rich network applications to run on multiple devices while leveraging each device's unique features.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional porting or rewriting is performed for each platform, then application compatibility with specific devices is improved, but development cost and time increase significantly

Engineering Contradiction:
Improveapplication compatibilityVSAvoiddevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The application is divided into platform-independent core components and platform-specific adaptive components. The core functionality is implemented once and reused across all platforms, while only the adaptive portions are customized for each device type, dramatically reducing the total development effort required for multi-platform compatibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses configurable parameters and metadata to describe device-specific characteristics (screen size, processor type, memory capacity) and automatically adjusts the application parameters accordingly. This allows a single application codebase to adapt to different platforms by changing parameters rather than rewriting code.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If a single application is deployed across multiple device types, then deployment efficiency is improved, but the application cannot optimize for device-specific features

Engineering Contradiction:
Improvedeployment efficiencyVSAvoiddevice optimization
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The application incorporates dynamic adaptation mechanisms that automatically detect device characteristics at runtime and adjust behavior accordingly. The system can dynamically select different UI layouts, feature sets, and performance optimizations based on the detected platform, enabling a single deployed application to optimize for each device type without requiring separate applications.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The application is designed with universal components that can function across multiple platforms while maintaining core functionality. These universal components serve multiple purposes and can be configured to leverage device-specific features when available, while falling back to generic implementations when needed, thus achieving both efficiency and optimization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If extensive porting is performed for each platform, then application functionality is maintained, but maintenance cost increases

Engineering Contradiction:
Improveapplication functionalityVSAvoidmaintenance complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

By segmenting the application into stable core components and flexible adaptive components, maintenance efforts are concentrated only on the adaptive portions that need updating for new platforms or device features. The core functionality remains stable and requires minimal maintenance, reducing overall maintenance complexity and cost.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of maintaining separate application codebases for each platform, the system creates platform-specific versions by copying and configuring a single master application template. This copying approach preserves functionality while simplifying maintenance, as updates to the master template automatically propagate to all platform versions.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8621423B2Method of automatically building a customised software application for a specific type of wireless computing device
Publication Date: 2013.12.31 LEMON INC(GB)
  • US8621423B2 patent drawing
  • US8621423B2 patent drawing

AI summary

A customized software application can be built for a specific type of Wireless Computing Device by (a) automatically determining attributes of that type of Wireless Computing Device; (b) automatically determining which Software Components from a library of Software Components are compatible with that type of Wireless Computing Device based on values of the attributes determined in (a); and (c) automatically combining the compatible Software Components together to generate a customized build of the application, compatible for that type of Wireless Computing Device. The attributes can be metadata. This approach enables rich Network Applications to be automatically built for Wireless Computing Devices of a wide variety of types.