Native modules katika React Native ni nini?

Question

Accepted Answer

**Native modules** huiwezesha React Native (JavaScript) kufikia **native platform code na features** (iOS/Android) ambazo hazipatikani kupitia JavaScript — zikiunganisha kwa native APIs, SDKs, au custom native functionality. Hupanua React Native zaidi ya kile ambacho JS pekee hutoa.

## Kwa nini native modules zipo

```text
React Native's JavaScript can't directly access every native capability. NATIVE MODULES
bridge JS to native code (Swift/Objective-C on iOS, Kotlin/Java on Android):
  → access native APIs/SDKs not exposed to JS
  → use existing native libraries
  → implement performance-critical or platform-specific functionality in native code
→ The bridge between React Native's JS and the native platform.
```

## Kutumia native modules (zaidi kupitia libraries)

```text
→ MOST native functionality is available via EXISTING LIBRARIES (npm packages that
  include native modules): camera, geolocation, Bluetooth, payments, push notifications, etc.
  → you usually INSTALL a library rather than writing native code yourself
→ EXPO provides many native APIs without writing native code (managed modules)
→ You WRITE a custom native module only when no library exists for your need
```

## Kuandika custom native module (kidhana)

```text
→ Write native code (Swift/Kotlin) exposing methods to JS
→ Register/expose it so JS can call it (via the bridge / new architecture's TurboModules)
→ Call it from JavaScript like a regular module
→ Requires native development knowledge; platform-specific implementation per OS
→ The NEW ARCHITECTURE (JSI, TurboModules, Fabric) improves native interop performance
```

## Kwa nini ni muhimu

Kuelewa native modules kuna thamani kwa sababu ndiyo **jinsi React Native inavyofikia native platform capabilities** zaidi ya kile JavaScript hutoa, uwezo muhimu kwa apps zinazohitaji native features, kwa hivyo ni maarifa muhimu kwa maendeleo ya React Native.

Hitaji la msingi — JavaScript ya React Native haiwezi kufikia moja kwa moja kila native capability, kwa hivyo **native modules huunganisha JS kwa native code** (Swift/Objective-C, Kotlin/Java) — hushughulikia jinsi React Native inavyofikia device features (camera, geolocation, Bluetooth, push notifications), hutumia native SDKs, na hutekeleza performance-critical au platform-specific functionality.

Kuelewa **uhalisia wa vitendo** ni muhimu: **native functionality nyingi inapatikana kupitia existing libraries** (npm packages zinazobundle native modules) au **Expo's managed native APIs**, kwa hivyo kwa kawaida **husakinisha library badala ya kuandika native code mwenyewe** — ikimaanisha developers wengi hutumia native modules kupitia libraries badala ya kuziandika, jambo muhimu la vitendo linaloweka matarajio halisi.

Kuelewa kwamba **huandika custom native module tu wakati hakuna library iliyopo** kwa hitaji lako mahususi (linalohitaji native development knowledge na implementation kwa kila platform) hufafanua wakati custom native work inahitajika.

Kujua kwamba **new architecture** (JSI, TurboModules, Fabric) huboresha native interop performance huonyesha ufahamu wa mageuzi ya React Native.

Native modules ndiyo jinsi React Native inavyounganishwa na native platform, muhimu kwa apps zenye native requirements, ingawa mahitaji mengi hutimizwa na existing libraries.

Kwa kuwa kufikia native capabilities wakati mwingine ni lazima (kwa device features na native integration) na native modules (zaidi kupitia libraries, mara chache custom) ni utaratibu wa React Native kwa hilo, na kwa kuwa kuelewa jinsi zinavyofanya kazi na kwamba mahitaji mengi hutimizwa na existing libraries kuna thamani kwa maendeleo ya React Native, kuelewa native modules ni maarifa yenye thamani, yenye umuhimu wa vitendo — bridge inayowezesha React Native kufikia native features, muhimu kwa apps zenye native needs huku ikifafanua kwamba functionality nyingi hutoka kwa existing libraries badala ya custom native code, muktadha wenye manufaa wa kufanya kazi na native capabilities za React Native.