# המפה הנייטיבית

> תיעוד מקור. מקור: docs/platform/mobile-native-map.md · 6a466bf.

## Runtime

The iOS/Android mobile client uses:

- `react-native-maps 1.29.11`
- `expo-location 58.0.20`

The app requests **foreground location only**. No background tracking or geofencing is enabled.

## Privacy boundary

The device's precise location is kept in app memory and is used to center the map. LinkNodes sends only the visible map viewport bounds to the authenticated Mobile Client API. The server does not persist device location.

## Tenant boundary

`GET /api/client/v1/tenants/:tenantId/map`:

- verifies the Clerk Bearer session;
- re-checks active tenant membership;
- uses the user JWT-backed Supabase client;
- relies on Supabase RLS;
- returns locations only for charging providers selected by that tenant;
- caps each viewport response at 400 locations.

No provider API, live charger availability, remote-start or fuel-station API data is implied by this view. Those arrive with provider integrations.

## Native map providers

iOS uses Apple Maps through `react-native-maps` by default.

Android uses Google Maps and therefore requires a Google Maps SDK for Android API key before a signed Play Store build. The key must be restricted to:

- package: `com.linknodesenergy.app`
- the release signing SHA-1 fingerprint

The Google Maps key must be supplied through native/EAS configuration and must never be committed to Git.

## Release gate

Before Google Play internal testing:

1. enable Maps SDK for Android in the production Google Cloud project;
2. create an Android-restricted API key;
3. bind package `com.linknodesenergy.app` and the Play/EAS signing SHA-1;
4. inject the key through EAS/native config;
5. build a new Android binary and verify map tiles on a physical device.

iOS requires no Google Maps key when using Apple Maps.
