Unified Display Template Configuration for Cross-Interface Synchronicity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-based CRM systems face challenges in providing a consistent user experience across different user interface types, as components designed for one interface type often inefficiently utilize resources or break when displayed on another, leading to synchronicity issues and high memory overhead due to separate definitions for each interface type.
Innovation Solution
Implementing a system where components are configured within a shared display template using a template customization application, with components supporting multiple user interface types defined by a single metadata file, and rendering decisions made at both the application builder and user device levels, ensuring synchronicity and reducing memory overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If separate versions of the application are defined for different user interface types, then the display quality for each interface type is improved, but memory overhead increases and synchronicity is lost
Solution Approach 1:
The patent merges multiple interface-specific application definitions into a single unified application definition that can dynamically adapt to different user interface types. Instead of maintaining separate versions for mobile, desktop, and tablet interfaces, the system uses one definition with conditional rendering logic that determines which components to display based on the detected interface type, thereby reducing memory overhead while maintaining display quality.
Solution Approach 2:
The unified application definition is designed to be universal across multiple user interface types. The single definition contains component configurations that can be conditionally applied to different interface types (mobile, desktop, tablet), making the definition multi-functional. This eliminates the need for separate definitions while ensuring each interface type receives appropriate display optimization.
2Manufacturing precision
If separate versions of the application are defined for different user interface types, then the display quality for each interface type is improved, but synchronicity between interface types deteriorates
Solution Approach 1:
By merging all interface-specific definitions into a single unified definition, the system ensures that any changes to the application structure, components, or logic are automatically synchronized across all user interface types. The unified definition serves as the single source of truth, eliminating version drift and maintaining consistency while still allowing conditional rendering for interface-specific optimizations.
3Productivity
If components are designed for a specific user interface type, then the component performance is optimized, but the system scalability to new interface types deteriorates
Solution Approach 1:
The unified application definition is constructed with universal component configurations that can adapt to multiple interface types. Each component is defined once with properties that allow conditional rendering based on interface type detection. This approach maintains optimized performance for existing interface types while enabling easy scalability to new interface types without requiring separate component definitions.
Solution Approach 2:
The system implements dynamic component rendering where the same component definition can behave differently based on the runtime interface type. The unified definition includes conditional logic that dynamically determines which components to display and how to configure them based on the detected user interface type, allowing the system to adapt to new interface types by adding detection rules rather than creating entirely new component definitions.
4Quantity of substance
If a single application definition is used across all user interface types, then memory overhead is reduced and synchronicity is maintained, but display quality and resource utilization deteriorate
Solution Approach 1:
The unified application definition incorporates local quality by allowing different rendering configurations for different interface types within the same definition. The system detects the user interface type and applies interface-specific rendering rules and component visibility settings, ensuring that each interface type receives optimized display treatment (e.g., mobile-optimized components for mobile devices, desktop-optimized components for desktops) while still using the same underlying definition structure.
Data Source
AI summary
Methods, systems, and devices for configuring components in a display template based on a user interface type are described. A template customization application may support configuration of a display template corresponding to multiple user interface types. A user may customize the display template by adding a component to the display template (e.g., where the display template is displayed by the template customization application according to a specific user interface type view). The template customization application may determine whether the added component supports rendering for the current user interface type and may display the component in the template based on the determination (e.g., either as a functional component or as a placeholder). Each user interface type supported by the template may be defined in a single underlying metadata file, so adding the component into one view will automatically add the component for all of the supported the user interface types.