JS SDK Login Path Selection for App Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and error-proneness of access processes in providing multiple login methods for applications, such as QQ, WeChat, and Microblog login, using the OAuth2.0 standard, lead to high development costs due to compatibility issues across different running environments.
Innovation Solution
A JavaScript SDK file encapsulates multiple login paths, detects the running environment, and sends the supported login path to the application, simplifying the access process and improving compatibility by selecting a path compatible with the current environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple login interfaces are provided for different login methods (QQ, WeChat, Microblog), then login versatility is improved, but access process complexity increases and errors become more frequent
Solution Approach 1:
The patent merges multiple login interfaces into a single unified JS SDK file that encapsulates all login paths (QQ, WeChat, Microblog). The SDK automatically detects the running environment and selects the appropriate login method, eliminating the need for developers to manually integrate multiple separate login interfaces while maintaining support for all login methods.
Solution Approach 2:
The JS SDK file acts as an intermediary layer between the application and multiple login services. It provides a standardized interface that the application calls, while the SDK handles the complexity of environment detection and login path selection, shielding the application from access process complexity and potential errors.
2Adaptability or versatility
If multiple login interfaces are provided for different login methods, then login versatility is improved, but development costs increase due to compatibility adaptation
Solution Approach 1:
The JS SDK file is designed as a universal component that can adapt to multiple running environments (iOS, Android, different browsers) and multiple login methods (QQ, WeChat, Microblog) through a single interface. This multi-functionality eliminates the need for separate integration work for each login method and environment, significantly reducing development costs while maintaining broad compatibility.
Solution Approach 2:
The SDK performs preliminary environment detection and login path selection automatically before the actual login process. By pre-configuring and pre-detecting the appropriate login method based on the running environment, the SDK eliminates the need for developers to perform manual compatibility adaptation work for different platforms and login services.
3Device complexity
If a single login interface is used, then access process complexity is reduced, but login versatility deteriorates
Solution Approach 1:
The single login interface in the JS SDK is dynamic in nature - it automatically adapts its behavior based on the detected running environment. The SDK detects the platform (iOS, Android, browser type) and dynamically selects the appropriate login path from multiple supported methods, providing login versatility through a unified, adaptive interface rather than static multiple interfaces.
4Device complexity
If login paths are not selected based on running environment, then implementation is simpler, but compatibility deteriorates and errors increase
Solution Approach 1:
The JS SDK implements environment detection feedback mechanisms that automatically identify the running environment (platform, browser type, version) and use this feedback to select the most compatible login path. This feedback-driven approach ensures high compatibility and reliability across different environments while maintaining simple implementation through automated detection and selection logic within the SDK.
Data Source
AI summary
A method is provided in which a JavaScript (JS) SDK file is called by an application. A plurality of login paths for logging in to the application is encapsulated in the JS SDK file. When the application is started, a running environment of the application is detected by using the JS SDK file. A login path supported by the running environment is determined by using the JS SDK file. Further, a first login path is sent to the application by using the JS SDK file. The first login path is the login path supported by the running environment and is one of the plurality of login paths.