native-data-fetching

예상 결과:

Use the fetch API with error handling:

```tsx
const fetchUser = async (userId: string) => {
const response = await fetch(`https://api.example.com/users/${userId}`);

if (!response.ok) {
throw new Error(`HTTP error! status: ${response.status}`);
}

return response.json();
};
```

Key points:
- Always check response.ok before parsing
- Handle network errors separately from HTTP errors
- Consider adding retry logic for resilience

예상 결과:

Use SecureStore for authentication tokens and other sensitive data:

```tsx
import * as SecureStore from 'expo-secure-store';

await SecureStore.setItemAsync('auth_token', token);
// NOT: await AsyncStorage.setItem('token', token);
```

AsyncStorage is not encrypted and is accessible to any app with root access. SecureStore uses the device's secure enclave for sensitive data.

예상 결과:

Use EXPO_PUBLIC_ environment variables with .env files:

```
# .env.development
EXPO_PUBLIC_API_URL=http://localhost:3000

# .env.production
EXPO_PUBLIC_API_URL=https://api.production.com
```

```tsx
const BASE_URL = process.env.EXPO_PUBLIC_API_URL;
```

Only use EXPO_PUBLIC_ prefix for client-safe values. Never put secrets (API keys, database passwords) in these variables.