2 posts tagged with "architecture"

Early on, this library was four separate workspace packages: a core package (gestures/ prediction/layout types), a raw Gradle module wired in through a hand-edited settings.gradle, a Swift-sources-plus-Ruby-script package hardcoded to one example project's paths, and the actual published react-native-keyboard-bridge npm package. A real external consumer would have needed two npm installs, a git submodule or hand-copy for the native folders, and manual edits across settings.gradle, app/build.gradle, MainApplication.kt, and AndroidManifest.xml.

Android's InputMethodService has a much larger memory budget than iOS's extension model, which is exactly why the Android side of this library could go straight to "host real React Native" with none of the multi-generation caution iOS needed.