Kuika's Web View element allows you to display an external web page or web-based content directly within your application. This feature enables users to access documentation, support pages, dynamic content, or third-party tools without leaving the application.

The Web View element is supported in both web and mobile applications.

Use Cases

• Embed third-party support and help pages
• Display dynamic reports, surveys, or data dashboards
• Show web-based forms or application fields
• Directly present internal portals, documentation, or CRM screens within the application
• Displaying content from external services (e.g., YouTube, Google Docs, Kuika Docs)

Use Case – Help Center Integration

The Web View element is used in a dashboard application to allow users to directly access help content or documentation pages.

In the scenario:

• The main application is an administration screen where users perform operations via the panel.
• The Web View element is placed in the panel area on the right.
• Kuika's help page titled “How can we help?” is embedded in this area.
• Users can search the documentation or get help without leaving the panel.

Using Features in the Scenario Context

• URL: The address of the page to be displayed in the Web View.
  
  • Static usage: https://help.kuika.com
  • Dynamic usage (with Symbol Picker): {{selectedHelpTopic.url}}

UI Design Module Operations

1. Go to the UI Design module.
2. From the left panel, select the Elements > Special > Web View element.
3. Drag and drop it onto the screen, for example, onto the right panel of your dashboard page.

4. Configure the following settings in the Properties panel:
   
   • URL: https://help.kuika.com
5. The Web View area is pinned next to the user panel, making the help content constantly accessible.

Scenario Flow

1. While working in the admin panel, the user sees the “Help” area on the right.
2. The help.kuika.com content automatically loads via the Web View element.
3. The user enters their query in the “How can we help?” search box to access the relevant documentation.
4. The content is displayed directly within the application; the user does not leave the page.
5. If necessary, the content can be dynamically redirected to another page (e.g., {{selectedTopic.url}}).

Limitations

• Web View only supports pages using the HTTPS protocol.
• Some external sites (e.g., those set to “X-Frame-Options: DENY” due to security policy) cannot be embedded.
• Loading external pages on mobile devices may take slightly longer.
• Web View content is independent of the application's data sources.

Tips and Best Practices

• Displaying help and documentation pages within Web View allows you to redirect users without leaving the application.
• Prefer dynamic URL linking for web-based content (e.g., reports, embedded YouTube videos).
• When integrating with an external system, ensure that the target URL allows iframe or embed usage.
• Design the Web View area to be responsive (adaptable to different screen sizes) to enhance the user experience.
• If you want to offer multilingual support, make the URL value dynamic based on the {{selectedLanguage}} variable.

When the Scenario is Complete

• The user can access external content without leaving the application.
• Help pages, documentation, or dynamic content are displayed via Web View.
• The process of accessing information is accelerated, and the user experience is improved.
• The application gains both a functional and supportive structure.