Card-Based Information Displaying Method for Version Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for displaying new card types in applications (APPs) fail when APP version updates are unsuccessful due to server busy conditions or other issues, leading to a lower user experience.
Innovation Solution
A card-based information displaying method that determines if the client's configuration version supports the card type, and if not, associates a second card supported by the configuration version using an association identifier, allowing the second card to display target information and version update prompts, thereby ensuring consistent display and facilitating card type management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the APP version is updated to support new card types, then the card type compatibility is improved, but the system reliability deteriorates because the update may fail due to server busy conditions or other circumstances
Solution Approach 1:
The server pre-processes new card types and generates corresponding second cards that are compatible with old client versions before the client actually needs to display them. This preliminary preparation ensures that when old-version clients receive content with new card types, they can immediately display compatible versions without requiring real-time updates or complex version checking during display operations.
Solution Approach 2:
The server acts as an intermediary that translates new card types into compatible second cards for old clients. Instead of requiring direct compatibility between new card types and old clients, the server mediates this incompatibility by generating appropriate second cards that old clients can display, thus resolving the compatibility issue without forcing clients to update.
2Adaptability or versatility
If the APP guides users to update the version for displaying new card types, then the card type support is improved, but the user experience deteriorates due to update failures and additional operational steps required from users
Solution Approach 1:
The system automatically handles card type compatibility without requiring user intervention. When old clients receive content with new card types, the server automatically generates and returns compatible second cards, eliminating the need for users to manually update the APP or perform any update-related operations.
Solution Approach 2:
The server mediates between new card types and old clients, automatically translating incompatible content into displayable formats. This intermediary approach eliminates the need for direct user action to update versions, as the server handles the compatibility transformation transparently in the background.
3Adaptability or versatility
If the system checks client version support for each card type, then the card type compatibility is improved, but the processing complexity increases
Solution Approach 1:
The system extracts the version compatibility checking logic from the client side and moves it to the server side. Instead of having each client check its own version compatibility (which would require complex client-side version management), the server centralizes this functionality by automatically determining compatibility and generating appropriate second cards based on client version information.
Solution Approach 2:
The server acts as an intermediary that centralizes version compatibility management. Rather than distributing complex version checking logic across multiple clients, the server handles all compatibility determinations centrally, receiving client version information and returning appropriately compatible card representations.
Data Source
AI summary
Disclosed in the present application are a card-based information displaying method and apparatus, and an information displaying service processing method and apparatus. The card-based information displaying method comprises: determining target information to be displayed and a card type of a first card for displaying the target information; determining whether a configuration version of a client supports the card type of the first card; when it is determined that the configuration version of the client does not support the card type of the first card, determining an association identifier corresponding to the first card, and associating with a second card supported by the configuration version of the client according to the association identifier; and displaying the target information of the client using the second card.