Interactions Layer in Web Application Builder Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web application builder frameworks lack the ability to create specialized application builders for specific use cases, such as community and technical support applications, as they do not provide the necessary components for routing and live chat functionality, limiting their versatility and customization options.
Innovation Solution
A web application builder framework with a multi-tenant database system that allows for the creation of reusable, configurable components, including a base editor and property editor, and an interactions layer, enabling developers to construct custom application builders using a set of reusable building blocks, allowing for the creation of specialized builders like Community and Technical Support Builders.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a web application builder framework provides generic components only, then the framework remains simple and easy to operate, but it cannot create specialized application builders for specific use cases like community and technical support applications
Solution Approach 1:
The framework is divided into distinct layers: a base layer with generic components, an interactions layer with specialized components (including routing and live chat), and an application layer where builders are constructed. This segmentation allows specialized functionality to be added without complicating the entire framework structure.
Solution Approach 2:
The framework employs a nested architecture where specialized application builders are constructed by composing base components with interactions layer components. The interactions layer components can be nested within application-specific builders, allowing specialized functionality to be embedded within the generic framework without increasing overall complexity.
2Adaptability or versatility
If the framework includes routing and live chat functionality, then it enables specialized application builders, but it increases the complexity of the framework
Solution Approach 1:
The interactions layer components (routing and live chat) are designed as universal building blocks that can be reused across multiple specialized application builders. These components serve multiple functions within different application contexts, reducing the need for duplicate implementations and thereby limiting the increase in framework complexity despite adding specialized capability.
3Ease of operation
If developers need to create custom web applications with specific functionalities, then they require extensive programming knowledge, but the framework should enable this without requiring extensive programming knowledge
Solution Approach 1:
The framework provides self-service capabilities through its interactions layer, which includes pre-built routing and live chat components that automatically adapt to different application needs. Developers can configure these components without extensive programming knowledge, as the framework handles the complex interactions and routing logic automatically based on configuration inputs.
Data Source
AI summary
Disclosed are examples of systems, apparatus, methods and computer program products for providing an interactions layer in a web application builder framework. A database system maintains a database associated with a number of web application builder components, each with one or more attributes and one or more component behaviors, for constructing web application components based on user input. The system displays a user interface with development areas comprising one or more web application builder components. Based on a user request to select a web application builder component in some form, the system prevents one or more component behaviors of the web application builder component, determines one or more builder component behaviors for the component based on the form of selecting the component, and presents the component in the user interface according to a form corresponding to the one or more builder component behaviors.