Getwebapp

[fuugsub]

Description

When converting a website URL into a mobile app, I am seeing two problems:

1. The Android/iOS download sometimes returns a ZIP/build artifact instead of the real installable .apk or .ipa file.
2. The generated mobile app sometimes uses a Google/default favicon instead of the website's actual logo/app icon.

Expected behavior:

• The Android download button should always return the actual .apk file.
• The iOS download button should always return the actual .ipa file.
• Source/build ZIP files should be available separately.
• The app icon should be selected from the website's real branding, preferably from:
  • Web App Manifest 512x512 / 1024x1024 icon
  • apple-touch-icon
  • largest rel="icon"
  • uploaded custom icon
• Google favicon services or generic browser favicons should not be used as the primary app icon.
• The selected icon should be converted into a proper 1024x1024 PNG and used for Android/iOS app assets.

Actual behavior:

• Sometimes clicking Download APK downloads a .zip artifact.
• Sometimes the app icon is a Google/default icon rather than the website's actual logo.

Steps to reproduce

1. Run the application.
2. Open the URL-to-mobile-app builder.
3. Enter a website URL that has a manifest icon, apple-touch-icon, or custom website logo.
4. Let the platform analyze the website.
5. Generate/build the Android mobile app.
6. Wait for the build to complete.
7. Click "Download APK".
8. Check the downloaded file.
9. In some cases, the downloaded file is a ZIP/build artifact instead of a real .apk.
10. Install/open a generated app and check the launcher icon.
11. In some cases, the icon is a Google/default favicon instead of the website's real logo.

Expected:

• A valid APK should be downloaded directly.
• The website's correct logo/app icon should be used.

Actual:

• ZIP artifact may be downloaded.
• Wrong/default icon may be used.

Additional context

The build/download pipeline should keep artifacts separate, for example:

• apkUrl
• aabUrl
• ipaUrl
• sourceBundleUrl

If the build provider returns a ZIP artifact, the backend should:

1. Download the artifact ZIP.
2. Extract it safely.
3. Search recursively for the actual release .apk / .ipa.
4. Prefer release APK over debug APK.
5. Validate that the binary exists and is non-empty.
6. Upload the binary separately.
7. Save the direct binary URL in the database.
8. Use that direct URL for the APK/IPA download button.

For icon detection, the priority should be approximately:

1. User uploaded icon
2. Manifest 1024x1024 / 512x512 icon
3. apple-touch-icon
4. Largest rel="icon"
5. Suitable og:image fallback
6. favicon.ico
7. Generated fallback

The final icon should be normalized into a 1024x1024 PNG before generating Android/iOS assets.

Please also ensure the app does not reuse stale/cached branding from previous builds.

Hedera network

No response

Version

v0.1.0

Operating system

Windows

[jwagantall]

@fuugsub , this is not related to hiero-ledger/governance

Is this related to any SDK or other repo you are leveraging in hiero-ledger. If so, it should be created there. Thank you!