Custom Enterprise Application Build System Bypassing App Store Review
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current enterprise application development and deployment processes are complex and time-consuming, requiring specialist knowledge and involving lengthy third-party review processes, making it difficult for enterprises to quickly and efficiently deploy custom applications to end users.
Innovation Solution
A streamlined method for building and deploying custom enterprise applications using a system that allows authorized users to create custom applications with minimal hardware, leveraging a bonding client and web access service to build and store applications directly, bypassing third-party digital distribution platforms, and enabling users to download and install them efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional third-party digital distribution platforms are used for enterprise application deployment, then applications can be published through established channels, but the review process takes an average of two days and enterprises have no control over the timeline
Solution Approach 1:
The patent extracts the application review and distribution process from the third-party digital distribution platform (App Store) and brings it into the enterprise's own controlled environment. The enterprise maintains its own application store and review process, eliminating the external bottleneck while maintaining application quality control through internal review procedures.
Solution Approach 2:
The patent implements preliminary action by establishing enterprise-controlled application review processes before deployment. Applications are reviewed and approved within the enterprise's own system beforehand, so they can be quickly distributed to employees without waiting for external platform review, thus reducing the two-day delay.
2Reliability
If specialist capabilities and specific knowledge are required to develop enterprise applications, then applications can be developed with proper expertise, but the development process becomes complex and time-consuming
Solution Approach 1:
The patent segments the enterprise application development process into distinct, manageable components: application submission, internal review, approval workflow, and deployment. This segmentation allows specialized tasks to be handled by different teams at appropriate stages, maintaining quality while reducing overall process complexity through clear division of responsibilities.
Solution Approach 2:
The patent creates a universal enterprise application platform that can handle multiple types of applications (mobile apps, web apps, desktop apps) through a single review and deployment system. This multi-functional platform reduces complexity by providing standardized processes for diverse application types, eliminating the need for separate specialized workflows for each application category.
3Productivity
If custom enterprise applications are built with minimal hardware and rapid processes, then deployment time is reduced, but control and quality assurance may be compromised
Solution Approach 1:
The patent implements feedback mechanisms through structured internal review processes where applications are evaluated against quality criteria before deployment. The review system provides feedback to developers about compliance and quality issues, allowing rapid iteration and correction while maintaining quality standards. This feedback loop ensures that speed does not compromise reliability.
Solution Approach 2:
The patent performs preliminary quality assurance actions through pre-deployment review and approval processes. Applications are tested, reviewed, and approved within the enterprise system before being deployed to employees, ensuring quality control is built into the rapid deployment process rather than added as a later bottleneck.
Data Source
AI summary
A system may receive a request from a user to build a custom application specific to an operating system (OS) platform. The system may include an application gateway and the custom application may be a user-customized variation of an application gateway client. The system may prepare a build request and send it to a bonding client running on a work station specific to the OS platform. The bonding client may execute build scripts with user-provided configuration information to create the custom application. Instead of submitting the custom application to a third-party digital distribution platform, the bonding client may store the custom application in a storage location accessible by the system. The system, responsive to the request from the user, may send a response to the computing device, the response containing a link to the storage location of the custom application.