App is not merely a web view wrapper around a website

Apple's guideline 4.2 requires apps to offer functionality beyond what a mobile web browser can provide. A root <WebView> loading your website URL — or a tab navigator where every tab is a WebView — provides exactly zero native value and is rejected routinely. Google Play applies the same standard. Beyond rejection: a WebView wrapper offers worse performance than Safari/Chrome, no access to native APIs, broken back-button behavior on Android, and user interfaces that feel foreign on mobile. The rejection is not a technicality — the platforms genuinely won't distribute apps that are just website containers.

Replace WebView-based primary content with native components. Start with the root navigator.

// Before (rejected):
export default function HomeScreen() {
  return <WebView source={{ uri: 'https://yoursite.com/home' }} style={{ flex: 1 }} />;
}

// After (native):
export default function HomeScreen() {
  const { data } = useHomeData();
  return (
    <ScrollView>
      <FlatList data={data} renderItem={({ item }) => <PostCard post={item} />} />
    </ScrollView>
  );
}

WebViews are permitted for: OAuth flows, in-app help browser, PDF preview, or one specific screen of third-party external content. Every tab in your tab navigator must render native components as its primary content.