App provides genuine utility and is not too simple to justify a standalone app

Apple guideline 4.2 (Minimum Functionality) and Google Play's Spam policy exist specifically to block thin WebView wrappers masquerading as native apps. A single-screen app that renders an external URL full-screen provides no offline capability, no native hardware integration, and no experience a mobile browser cannot already deliver — reviewers are trained to spot this pattern and reject on first pass. Beyond the immediate rejection, an app that clears this bar only by the thinnest margin faces re-rejection on future updates whenever guidelines tighten.

Add at least one native capability that a mobile browser cannot replicate, then build a minimum of three distinct functional screens around it. The fastest defensible path is AsyncStorage-backed offline caching plus push notifications — both are available in Expo without additional entitlements.

// app.json — enable push notifications
{
  "expo": {
    "plugins": [
      ["expo-notifications", { "sounds": ["notification.wav"] }]
    ]
  }
}

If the app's primary value is web content, build a PWA instead — lower maintenance burden, no policy risk.