Automated Mobile App Generator for Multi-Provider Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual process of generating mobile applications for different platforms and user groups is costly and time-consuming, requiring developers to create separate versions for providers and consumers with different views and features.

Innovation Solution

An automated mobile application generator system that uses a server computing system with an application generation server and API server to create customized mobile applications, allowing providers to configure and customize their apps for multiple platforms, including separate views for providers and consumers, and enabling automated updates and feature additions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual customization is used to create separate mobile applications for different application providers and user groups, then each provider can have customized views and features, but the development cost and time consumption increase significantly

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal mobile application platform that serves multiple application providers through a single app binary. The system uses a unified authentication mechanism and a common user interface framework that can adapt to different providers without requiring separate customized applications. This allows one application to perform multiple functions for different providers, eliminating the need for manual customization and significantly reducing development time and costs.

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

Solution Approach 2:

The system employs dynamic configuration where the application behavior, authentication methods, and user interface elements are determined at runtime based on the logged-in user's affiliation with specific application providers. The application can dynamically load different provider-specific configurations and policies without requiring separate compiled binaries, enabling flexible adaptation to different providers while maintaining a single codebase.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If separate mobile applications are generated for each application provider, then each provider gets customized functionality, but the complexity of the development process increases

Engineering Contradiction:
Improveprovider-specific customizationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary authentication server and configuration management system that mediates between the unified mobile application and multiple application providers. This intermediary layer handles provider-specific authentication, authorization, and configuration delivery, shielding the mobile application from direct complexity of managing multiple provider integrations. The intermediary translates diverse provider requirements into standardized configurations that the unified app can consume.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the complexity by separating concerns into distinct layers: the unified mobile application layer, the intermediary authentication and configuration layer, and the provider-specific backend services. This segmentation allows each layer to be developed and maintained independently, reducing overall system complexity while enabling provider-specific customization through the intermediary layer.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If manual updates are performed for each customized application version, then specific provider requirements can be met, but the update process becomes time-consuming and error-prone

Engineering Contradiction:
Improveprovider-specific featuresVSAvoidupdate time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges all provider-specific configurations, authentication methods, and feature sets into a single unified application binary. Instead of maintaining separate application versions for each provider, the system combines all provider requirements into one app that dynamically adapts based on user context. This merging eliminates the need for manual updates of multiple separate applications, as updates are deployed once to the unified app and automatically applied to all provider contexts.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary configuration of all provider-specific features, authentication methods, and policies during the application build process and initial deployment. Configuration data and provider-specific parameters are pre-loaded into the unified application, enabling rapid adaptation to different providers without requiring subsequent manual customization or updates. This preliminary setup reduces update time by eliminating the need for post-deployment customization work.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8656353B2Mobile application generator
Publication Date: 2014.02.18 USER FRIENDLY PHONE BOOK LLC
  • US8656353B2 patent drawing
  • US8656353B2 patent drawing
  • US8656353B2 patent drawing

AI summary

A system and a method are disclosed for receiving a request to create a mobile application, the request comprising provider-specific application information and provider-specific content for the mobile application, generating, by a processing device, an application description based on the provider-specific application information, wherein the application description comprises a selection of one or more application features for the mobile application, retrieving, by the processing device, a base mobile application stored in a data store, wherein the base mobile application comprises previously generated base application software code, modifying, by the processing device, the base mobile application in view of the application description; and generating, by the processing device, binary mobile application code for the mobile application in view of the modified base mobile application.