Mobile Cascading Style Sheets Compiler for Native App Development

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing mobile applications that run consistently across iOS and Android platforms is costly and time-consuming, and existing solutions like web apps and hybrid apps have limitations such as slower performance, limited access to native capabilities, and inconsistent user experiences.

Innovation Solution

The use of mobile cascading style sheets (MCSS) framework, which includes a compiler with a parser and applier module to convert MCSS code into native SDK instructions, allowing developers to create and maintain cross-platform applications with a consistent UX/UI, simplifying the coding process and enabling real-time updates without requiring app store uploads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If developers use native SDK code for each platform (iOS/Android), then the application can access full native capabilities and achieve optimal performance, but the development time and cost increase significantly due to requiring experienced developers in both iOS and Android

Engineering Contradiction:
Improvenative capabilities accessVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces MCSS (Mobile Cascading Style Sheets) as an intermediary language that sits between the developer's high-level CSS knowledge and the platform-specific native SDK code. The MCSS compiler acts as a mediator that translates cross-platform CSS code into platform-specific native code, eliminating the need for developers to write separate iOS and Android code while maintaining full native capabilities access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the programming paradigm by introducing a new parameter system (MCSS) that represents UI components and styles in a unified, platform-independent way. This parameter change allows the same code to be compiled to different native implementations, transforming the development process from writing platform-specific code to writing abstract, platform-agnostic code that is automatically translated.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If developers maintain separate code bases for iOS and Android, then each platform can be optimized independently, but fixing errors and making improvements becomes extremely challenging and time-consuming

Engineering Contradiction:
Improveplatform-specific optimizationVSAvoidmaintenance difficulty
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the code base into two distinct parts: the universal MCSS code that contains the application logic and UI definitions, and the platform-specific native SDK code that is automatically generated. This segmentation allows developers to maintain a single source of truth for the application code while each platform receives optimized native implementation, making maintenance easier as changes are made once in MCSS and automatically propagated.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses code generation to create platform-specific native code by copying and transforming the universal MCSS code. Instead of manually copying and adapting code for each platform, the system automatically generates platform-specific code from a single MCSS source, reducing maintenance errors and time requirements while preserving platform-specific optimizations.

Inventive Principle:
Principle #26Copying

3Ease of operation

If developers use web apps served through the internet, then the application can be accessed without app store downloads, but the application exhibits slower operating speed and has little or no access to native device capabilities

Engineering Contradiction:
ImproveaccessibilityVSAvoidoperating speed
Core Design Contradiction:
Ease of operationVSSpeed

Solution Approach 1:

The patent creates a hybrid approach by copying the accessibility benefit of web apps (no app store required) while copying the performance benefits of native apps. The MCSS framework compiles to native code that runs within the native SDK, achieving native-level performance while maintaining the ease of deployment and update capabilities of web applications.

Inventive Principle:
Principle #26Copying

4Ease of operation

If developers use hybrid apps with embedded browsers, then the application can be downloaded and installed locally, but the graphical appearance and behavior vary from platform to platform and performance is slower than equivalent native apps

Engineering Contradiction:
Improvelocal installationVSAvoidUX/UI consistency
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The patent uses MCSS as an intermediary that ensures consistent UX/UI across platforms. The MCSS compiler acts as a mediator that translates high-level CSS styling instructions into platform-specific native code, guaranteeing consistent graphical appearance and behavior across iOS and Android while maintaining local installation capability through native app packaging.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12182550B2Systems and methods for cascading style sheets in native mobile applications
Publication Date: 2024.12.31 DO GENIUS ON LLC
  • US12182550B2 patent drawing
  • US12182550B2 patent drawing
  • US12182550B2 patent drawing

AI summary

Mobile cascading style sheets (MCSS) are provided for use in conjunction with native mobile applications. The MCSS framework/library allows a developer to use the full potential and capabilities of the native software development kit (SDK) via a form of cascading style-sheet (CSS) code to design, build, and deploy an entire native application in much the same way a website is built with CSS. To achieve this, the system includes a compiler (consisting of an interpreter module and an applier module) configured to convert MCSS code to native SDK instructions, as described in further detail below. In this way, by simplifying the coding process, the present invention provides substantial savings in terms of both time and cost with respect to developing new applications and maintaining/updating existing applications.