Lynx Plugins Architecture #390
Replies: 2 comments 4 replies
-
🚀 Shaping the Best Plugin Architecture for LynxThe NitroModules author conducted a great comparison between ExpoModules, TurboModules, and NitroModules. Insights from this and other framework plugin architectures can help us shape the best Plugin Architecture for Lynx. While Lynx is still young, it has huge potential to learn from the experiences of mature frameworks like Flutter, React Native, Expo, and Capacitor. By leveraging past lessons, hope Lynx Team can design an efficient, scalable, and developer-friendly plugin system. I also came across this discussion #387 (comment) by @elcoosp, which highlights improvement suggestions. While that discussion focuses on short-term enhancements, I hope this thread can serve as a space for defining the long-term vision of where Lynx Plugin Architecture is headed in the bigger picture. Let's collaborate and shape the future of Lynx plugins! 💡🔥 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your advice. We will refer those frameworks and decide which road to walk. Because once this has been released, it will be very hard to change. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
import from #1 (comment)
🔹 Lynx Plugins Architecture
Currently, in the react-native world we have several approaches to native modules, including Native Modules, Turbo Modules, Expo Modules, and Nitro Modules. After reading comparisons like this and this, I hope Lynx will take inspiration from Nitro Modules.
Additionally, while Flutter Platform Channels (docs) offer an interesting approach, Google's recent slowdown in Flutter investments has led to forks like Flok. Even so, it's still a valuable reference point.
Beta Was this translation helpful? Give feedback.
All reactions