Login is not required for features that do not need identity

Apple's guideline 5.1.1 states that apps may not require users to register or log in before using features that don't require identity. An app that redirects everyone to a login screen on first launch gives the reviewer no way to evaluate the core functionality — which itself can cause rejection. Beyond compliance, requiring signup before showing any value is the single highest-conversion-killing pattern in mobile onboarding: users uninstall rather than create accounts for apps they haven't seen yet. A meaningful guest mode isn't optional polish — it's required by policy and critical for growth.

Implement a guest navigator that exposes the app's core read-only value before authentication is required.

// src/navigation/RootNavigator.tsx
export function RootNavigator() {
  const { user } = useAuth();

  return (
    <Stack.Navigator screenOptions={{ headerShown: false }}>
      {user ? (
        <Stack.Screen name="App" component={AuthenticatedNavigator} />
      ) : (
        // Guest users see the main browse/explore experience
        <Stack.Screen name="Guest" component={GuestNavigator} />
      )}
    </Stack.Navigator>
  );
}

Gate only actions that genuinely require identity: saving, posting, purchasing, syncing preferences. When a guest attempts a gated action, show a prompt inviting them to sign up — not a hard redirect to login from the app root.