Mobile App Configuration via OData Gateway

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modifying mobile applications to access centrally stored databases is challenging due to the need for specialized programming skills and significant code changes, making it costly to update user interfaces or perform CRUD operations.

Innovation Solution

A configuration tool that allows for modifying the user interface of mobile apps without changing the application code, dynamically generating CRUD operations, and storing configuration data on an OData gateway, enabling easy customization and updates without programming knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If custom programming is used to create mobile applications that access centrally stored databases, then the applications can provide full functionality and access to database operations, but the cost and complexity of modifying the application increase significantly

Engineering Contradiction:
Improvedatabase access functionalityVSAvoidapplication modification complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system separates the mobile application into two independent parts: a static application binary that provides the user interface and interaction logic, and a dynamic configuration data set that defines database access parameters, query structures, and CRUD operations. This segmentation allows the configuration to be modified without recompiling or redistributing the application binary, resolving the contradiction between maintaining full database functionality and reducing modification complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic configuration where the mobile application loads and adapts to configuration data at runtime rather than having fixed, hard-coded database access logic. The configuration data can be updated centrally and pushed to multiple devices, enabling the application behavior to change dynamically without code modifications. This dynamic approach maintains full database access functionality while eliminating the need for complex reprogramming when changes are needed.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If specialized programmers are hired to modify mobile applications, then the applications can be updated with new features and interface changes, but the cost becomes prohibitive

Engineering Contradiction:
Improveapplication customization capabilityVSAvoidmodification cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system enables non-programmer users to customize and modify mobile application behavior through a configuration interface that provides visual, form-based editing of database access parameters, query definitions, and CRUD operations. The configuration tool automatically generates the necessary configuration data files that the mobile application consumes at runtime. This self-service capability allows business users to perform customizations that previously required specialized programmers, dramatically reducing modification costs while maintaining full adaptability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a configuration data layer as an intermediary between the mobile application and the centrally stored database. This configuration layer acts as a mediator that translates user-friendly configuration parameters into the technical specifications needed for database access. By inserting this intermediary layer, the system decouples the user interface from the database access logic, allowing non-technical users to make changes without needing to understand complex programming concepts or database schemas.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If code changes are made to update the mobile application interface, then the user interface can be modified to meet changing requirements, but significant development time and expertise are required

Engineering Contradiction:
Improveinterface modifiabilityVSAvoidimplementation time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary configuration setup where all database access parameters, query structures, and CRUD operation definitions are prepared and stored in a centralized configuration repository before being deployed to mobile devices. The mobile application is pre-built with the capability to consume this configuration data at runtime. When interface changes are needed, only the configuration data needs to be updated in the repository, and the changes are automatically available to all devices without requiring compilation, testing, or deployment cycles. This preliminary preparation of configuration templates and structures dramatically reduces implementation time from days or weeks to minutes or hours.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10448227B2Mobile database access application development system and method
Publication Date: 2019.10.15 INNOVAPPTIVE INC
  • US10448227B2 patent drawing
  • US10448227B2 patent drawing
  • US10448227B2 patent drawing

AI summary

A system and method are presented that provide a configuration tool on a database gateway. The configuration tool stores configuration data that is used by a mobile app to customize the mobile application user interface. Changes made to the configuration data are accessed by each mobile application to revise the user interface of the mobile application. In one embodiment, the database gateway is an OData gateway that is used by the mobile device to communicate with the database.