Metadata-Driven Mobile App Architecture for Unique Store IDs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Small and medium-sized businesses face challenges in developing mobile applications that are both customizable and cost-effective, as they often rely on templates which result in less flexible, lower-quality apps that may be rejected by app stores due to duplication concerns.

Innovation Solution

A computer-implemented method and system for developing mobile applications using a declarative user interface that allows users to select features, generate metadata, and create unique code for mobile applications, ensuring each app has a distinct global identifier for app store distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If templates are used to develop applications for small and medium-sized businesses, then development cost is reduced, but application quality, usability, performance and flexibility deteriorate

Engineering Contradiction:
Improvedevelopment costVSAvoidapplication quality
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The application is divided into modular components including a shell application and configurable feature modules. Each module can be independently selected and configured through metadata, allowing businesses to assemble customized applications from proven quality components without developing everything from scratch.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses metadata parameters to dynamically configure application behavior, UI elements, and functionality. By changing metadata values rather than code, businesses can customize applications to meet specific quality and performance requirements while maintaining cost efficiency.

Inventive Principle:
Principle #35Parameter changes

2Ease of manufacture

If templates are used to develop applications, then development cost is reduced, but application flexibility and customization capability deteriorate

Engineering Contradiction:
Improvedevelopment costVSAvoidapplication flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The application configuration is made dynamic through metadata that can be modified at runtime without requiring code changes or recompilation. This allows businesses to flexibly adapt applications to changing requirements while maintaining the cost benefits of template-based development.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The shell application and feature modules are designed to be universal and multi-functional, capable of serving multiple business purposes through different metadata configurations. This enables a single template framework to adapt to diverse business needs without requiring separate custom development for each case.

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

3Ease of manufacture

If template-based applications are distributed to app stores, then development cost is reduced, but app store acceptance deteriorates due to duplication concerns

Engineering Contradiction:
Improvedevelopment costVSAvoidapp store acceptance
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system generates unique metadata configurations and branding elements in advance during the customization process. This preliminary configuration ensures that each submitted application has distinct identifying characteristics, preventing app store rejection due to duplication while maintaining the efficiency of template-based development.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11294648B2Application development architecture for mobile applications
Publication Date: 2022.04.05 SALESFORCE INC
  • US11294648B2 patent drawing
  • US11294648B2 patent drawing
  • US11294648B2 patent drawing

AI summary

Methods and systems for developing mobile applications are disclosed. A method may include providing a user interface with one or more options for selecting features of a mobile application; obtaining the selected features of the mobile application, the selected features including at least one or more product display features and one or more product navigation features; generating metadata corresponding to the selected features of the mobile application, including at least metadata corresponding to the one or more product display features and metadata corresponding to the one or more product navigation features; generating code associated with the mobile application based on the metadata, the code executable by a processor of a mobile operating system (OS) based device; and associating the code with a unique mobile application global identifier relative to an app store.