Repository navigation
|
How can a team catch Thin web wrapper with no added value automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'WKWebView\|loadRequest\|Capacitor\|Cordova' --include='*.swift' . | wc -l # a high count with little native code is a thin wrapperRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. The app is mostly a single web view loading a website with little native code. The fix. Add native capability, offline value, device integration, or content the web version lacks. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
APPLE-4.2-WEB-WRAPPERwith a coverage line and a proper exit code.What the hit means. The app is mostly a single web view loading a website with little native code.
The fix. Add native capability, offline value, device integration, or content the w…