Mobile App Customization via Multi-Device Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile applications require significant security and logistical challenges for personalized customization, often necessitating physical access and personnel involvement, which is impractical and costly, and remote customization poses security risks.
Innovation Solution
A customization server stores data independently of the mobile device, allowing users to remotely personalize applications using authorization data from postal, email, SMS, or visual codes, ensuring secure customization without personnel intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If physical access to each mobile device is required for customization, then security is improved, but ease of operation and cost are worsened
Solution Approach 1:
A customization server acts as an intermediary between the user and the mobile device customization process. The server receives customization requests, generates secure authorization data (such as QR codes or visual codes), and provides it to the user through alternative channels (email, SMS, postal message). This eliminates the need for physical presence at a bank branch while maintaining security through the intermediary's controlled authorization process.
2Ease of operation
If remote customization is implemented, then ease of operation is improved, but security is worsened
Solution Approach 1:
The system performs preliminary security actions before remote customization occurs. The customization server generates secure authorization data (QR codes, visual codes) that are sent to the user through secure channels. The user's mobile device then presents this pre-generated authorization data to the server, which verifies it before allowing customization. This preliminary authorization process ensures security is maintained despite remote operation.
3Adaptability or versatility
If custom corporate applications are developed with built-in approval workflows, then functionality is improved, but device complexity and development cost are worsened
Solution Approach 1:
The approval workflow functionality is extracted from the custom corporate application and moved to a separate, standardized service layer. Instead of embedding complex approval workflows directly into each custom application, the system uses a universal authorization mechanism where the customization server handles approval requests. This separation reduces application development complexity while maintaining the necessary approval capabilities.
Data Source
AI summary
Customizing an application on a mobile device includes storing at least a portion of customization data in a customization server that is independent of the mobile device, a user of the mobile device accessing the customization server independently of the mobile device, receiving authorization data from the customization server that enables the mobile device to securely receive customization data from the customization server, and the mobile device using the authorization data to cause the customization server to provide the customization data to the mobile device. The authorization data may be provided by postal message, email message, an SMS text message, and/or a visual code provided on a screen of a computer used to access the customization server. The user may use a computer to provide credential information to access the customization server. Customizing the application may allow the mobile device to access a user service on behalf of the user.