Android TV Hybrid App Development via WebView Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional Android TV applications face high development and maintenance costs due to their native nature, while Web Apps offer low-cost updates but compromise on design and performance, resulting in a suboptimal user experience.

Innovation Solution

Developing an Android TV hybrid application using an Android WebView component, WebSettings subclass, and embedded Java and JavaScript modules to integrate Web technologies with native Android systems, allowing for cost-effective UI development and business logic implementation while maintaining user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a native Android TV application is developed, then user experience and performance stability are improved, but development cost and maintenance cost increase

Engineering Contradiction:

Improveperformance stabilityVSAvoiddevelopment cost

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The application is segmented into two distinct parts: a native Android part (using Java/Kotlin) that handles performance-critical functions, and a web-based part (using HTML5/CSS3/JavaScript) that handles UI and content display. This segmentation allows each part to be optimized independently - the native part ensures performance stability while the web part reduces development and maintenance costs through standard web technologies.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent merges native Android development with web development by integrating WebView component into the native application. This combination allows the app to leverage both native performance capabilities and web-based ease of development, resolving the contradiction between performance stability and development cost.

Inventive Principle:

Principle #5Merging (Combining)

2Ease of manufacture

If a Web App is used to replace native App, then development cost is reduced, but user experience and performance are compromised

Engineering Contradiction:

Improvedevelopment costVSAvoiduser experience

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

By segmenting the application into web-based UI components and native Android functionality, the solution allows web technologies to handle cost-effective development while native code ensures high-performance operations and smooth user experience, preventing the degradation of user experience that would occur with a pure web app.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The WebView component acts as an intermediary that embeds the web application within the native Android environment. This mediator allows the web app to access native Android capabilities (camera, microphone, sensors, etc.) while maintaining the cost benefits of web development, thus preserving user experience that would otherwise be compromised.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If a native Android TV application is developed, then performance stability is improved, but development cycle and maintenance time increase

Engineering Contradiction:

Improveperformance stabilityVSAvoiddevelopment cycle

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Segmenting the application allows the time-consuming UI development and frequent content updates to be handled by web technologies with rapid development cycles, while the performance-critical native components are developed once and reused, significantly reducing the overall development cycle while maintaining performance stability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the development paradigm by adopting web standards (HTML5, CSS3, JavaScript) for UI development instead of traditional native UI frameworks. This parameter change enables faster development iterations, easier updates, and reduced maintenance time while the native Android backend continues to provide performance stability.

Inventive Principle:

Principle #35Parameter changes

4Adaptability or versatility

If a Web App is used, then development flexibility is improved, but design capability and performance are limited

Engineering Contradiction:

Improvedevelopment flexibilityVSAvoidperformance

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The segmentation strategy allows the web-based portion to provide development flexibility for UI changes and content updates, while the native Android portion maintains high-performance operations. This division enables the system to achieve both development flexibility and performance capability simultaneously.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

By merging web development flexibility with native Android performance capabilities through WebView integration, the solution achieves both development adaptability and execution performance, overcoming the limitations of using either approach alone.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11966734B2Method for developing Android TV hybrid application

Publication Date: 2024.04.23 REALTEK SEMICON CORP

AI summary

A method for developing an Android TV hybrid application includes: generating a WebView component in an Android Activity belonging to an Android side of the application; obtaining a WebSettings subclass and using it to configure the WebView component; using Web technologies to develop a Web page belonging to a Web side of the application; using the WebView component to show the Web page; creating a first Java object blended with a JavaScript context in the Android side to define different interfaces, and creating a second Java object to implement the interfaces defined by the first Java object, so that the Web side can call the functions of the Android side; providing a packaged Java class in the Android side to send messages, and providing a packaged JavaScript module in the Web side to process the messages, so that the Android side can feedback the messages to the Web side.