Standard Data Component for Cross-Device Native API Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing software applications for diverse mobile devices is challenging due to the lack of compliance between native application programming interfaces (APIs) from different manufacturers, requiring separate code versions for each device to access native application data entities, which is time-consuming and inefficient.
Innovation Solution
A system and method for developing a standard data component that uses a structured definition language to define metadata descriptors, allowing access to native application data entities across multiple devices, by storing a model of the component-based application and properties of the native application, and generating standard data component definitions for execution in a runtime environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If native APIs are tailored for each device to access native application data entities, then device compatibility is improved, but development time and complexity increase
Solution Approach 1:
The patent creates a universal native API layer that can access native application data entities across multiple device types and manufacturers. The standardized data component definition allows a single API implementation to serve multiple devices, eliminating the need for separate tailored APIs for each device while maintaining full compatibility with native data entities.
Solution Approach 2:
The patent introduces a standardized data component as an intermediary layer between the application logic and device-specific native application data entities. This mediator translates standardized access requests into device-specific operations, enabling universal access without requiring custom APIs for each device.
2Ease of operation
If code is rewritten for each device-specific native application, then access to native data entities is achieved, but maintenance burden increases
Solution Approach 1:
The standardized data component provides a universal interface for accessing native data entities across all devices. A single codebase using this standardized component can access native data entities on any device without requiring device-specific code versions, dramatically reducing maintenance burden while maintaining ease of access.
3Reliability
If separate native APIs are used for each manufacturer's devices, then device-specific functionality is optimized, but code reusability decreases
Solution Approach 1:
The standardized data component acts as an intermediary that preserves device-specific functionality optimization while enabling code reusability. The component maintains standardized access patterns that work reliably across different manufacturers' devices, allowing code to be reused without sacrificing device-specific performance or functionality.
Data Source
AI summary
A system and method for developing a standard data component for coupling with a plurality of components of a component-based application to access a stored data entity of a non-component-based native application, the applications for executing in a runtime environment of a device. The system and method comprises an application module configured for storing a model of the component-based application including features of data and message component definitions expressed in a structured definition language. Also included is a native module configured for storing properties of the data entity of the native application and a standard module for generating the standard data component definition based on the features of the component-based application and the properties of the data entity of the native application. The standard data component definition is expressed in the structured definition language.