Reaching platform capability.
WHAT A NATIVE MODULE IS
Native code exposed to JavaScript.
WHEN YOU NEED ONE
Capability no package provides.
WHAT IT REQUIRES
Implementation for each platform, in that platform's language.
WHAT PACKAGES PROVIDE
Existing implementations of common needs.
WHAT TO CHECK BEFORE ADOPTING ONE
Whether it supports the current architecture Maintenance activity Whether it requires manual native configuration Its effect on application size
WHY THE FIRST POINT MATTERS NOW
Packages not updated for the newer architecture become blockers.
WHAT TO BE CAREFUL WITH
Many packages, each with native configuration Packages that must be configured differently per platform Upgrades, which are frequently the hardest part of maintaining these applications
WHY UPGRADES ARE HARD
The framework, the platforms and every native package must remain compatible.
WHAT TO DO ABOUT IT
Upgrade regularly in small steps, never after years.
WHAT TO USE FOR MANAGED WORKFLOWS
Tooling that handles native configuration, where it covers your needs.
WHAT THAT COSTS
Limits on which native code you can include.
