False positive Flutter detection for WebView-wrapped React web apps (web-to-apk converters)

[GIRIDHAR-U-47]

Hi 👋, first of all, great project — really clean UI and very useful concept.

I found a stack detection edge case that may lead to misleading classification.

I built a React JS web app, then used a web-to-apk converter (basically a WebView wrapper) to generate an Android APK.
When scanning this APK using Unfilter, it gets detected as Flutter, even though the actual UI/content is a React web app running inside a WebView.

Many web-to-apk converter tools internally use Flutter WebView wrappers, so the APK includes flutter_assets/ and libapp. so, which triggers Flutter detection even though the actual application content is a web bundle (React).

Expected Behavior

Instead of showing only Flutter, it would be more accurate to classify it as something like:

Flutter (WebView wrapper)

Hybrid (WebView-based)

or Flutter + Web App

Actual Behavior

Detected stack is shown as:

Flutter

Suggested Improvement

If Flutter is detected, it may be useful to additionally scan for common WebView/web-app indicators such as:

bundled index.html

presence of HTML/CSS/JS assets inside APK

Then label it as a WebView-based wrapper.

Steps to Reproduce

Create a React web app.

Convert it into an APK using any web-to-app converter (WebView wrapper).

Install the APK.

Scan using Unfilter → it shows Flutter.

Device: Vivo T2

Android version: 15

Converter used: Appilix

Thanks again for the project 🙌 This is not a big issue, but could improve accuracy for hybrid WebView apps.

[r4khul]

thanks for reporting the issue @GIRIDHAR-U-47

the core logic of classification itself is happening based on this - flutter_assets/ and libapp.so

so yeah it is obvious that it gets detected as flutter

i will try to make a improvisation that is possible!

[GIRIDHAR-U-47]

Thanks a lot for the quick response @r4khul 🙌

Yes makes sense, since flutter_assets/ and libapp.so are present in the wrapper APK it will naturally be classified as Flutter.

Maybe one possible improvement could be:
If flutter_assets is detected, also check whether the APK contains bundled web assets (index.html, *.js, *.css) or WebView-based markers and classify it as something like “Flutter (WebView wrapper)” or “Hybrid”.

Happy to test any changes if needed. Thanks again!