Declarative Content Engine for Cross-Platform Rendering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing applications face challenges in seamlessly functioning across various operating systems and platform hardware combinations, often requiring separate code bases and design efforts, and may not fully utilize platform hardware capabilities due to abstraction layers.

Innovation Solution

A method and system that utilize a declarative content engine to receive requests from user devices, obtain field identifiers, and generate declarative content in a programming language, allowing for the transmission of application content that is platform-independent and capable of being rendered consistently across different computing devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate code bases are used for each platform, then application functionality can be optimized for specific platforms, but development complexity and maintenance burden increase significantly

Engineering Contradiction:
Improveplatform-specific optimizationVSAvoiddevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal content delivery system where a single declarative content definition can be rendered across multiple platforms (web browsers, mobile devices, desktop applications) through platform-agnostic rendering engines. This allows one code base to serve multiple platforms while maintaining platform-specific optimization capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system segments the application into two distinct layers: a platform-independent declarative content definition layer and platform-specific rendering layers. This separation allows the content logic to remain unified while enabling platform-specific optimizations in the rendering phase without increasing overall development complexity.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If a single version of application is deployed across all platforms, then development and maintenance are simplified, but platform hardware capabilities cannot be fully utilized

Engineering Contradiction:
Improvedevelopment simplicityVSAvoidhardware capability utilization
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system applies local quality by allowing each platform's rendering engine to optimize the presentation of declarative content according to its specific hardware capabilities and characteristics, while the core content definition remains unified. This enables platform-specific hardware utilization without requiring separate code bases.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If abstraction layers are added between application and hardware, then cross-platform compatibility is improved, but direct hardware capability access is reduced

Engineering Contradiction:
Improvecross-platform compatibilityVSAvoidhardware capability access
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent introduces a declarative content definition as an intermediary between the application logic and platform-specific rendering engines. This intermediary layer enables cross-platform compatibility while allowing each rendering engine to directly access and utilize its platform's hardware capabilities without requiring the application to know hardware specifics.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11645723B2Method and system for generating dynamic user experience
Publication Date: 2023.05.09 INTUIT INC
  • US11645723B2 patent drawing
  • US11645723B2 patent drawing
  • US11645723B2 patent drawing

AI summary

A method for providing user content that may receive, from a user device, a request for content. The method may obtain, in response to the request, a field identifier from a multiple of field identifiers according to a priority for a multiple of fields corresponding to the field identifiers. The field identifier may correspond to a field. The method may obtain application content based on the field identifier. The method may generate declarative content from the application content. The declarative content may express the application content in a declarative programming language. The method may transmit, to the user device, the declarative content.