Abstract
Enterprise organisations building React Native applications repeatedly face the same decision: whether a feature
should be implemented as a native module in Kotlin or Swift or remain in the shared JavaScript layer. In practice
this decision is rarely made systematically. It is shaped by individual familiarity, delivery pressure and precedent,
and over several years it produces fragmented native layers that are difficult to maintain, audit or hand over. This
study proposes a governance framework for making the native/shared decision consistently. The framework
combines four criteria (performance sensitivity, security and compliance requirements, platform capability access,
and long-term maintainability and team capability) into a 0–12 scoring model with three decision bands and an
explicit security override. It is accompanied by a three-layer reference architecture and a lightweight governance
process built around existing architecture reviews, a native module register, a periodic review cadence and
deliberate deprecation. The framework was developed through a design-oriented, practitioner-informed
methodology drawing on more than fifteen years of enterprise software delivery in regulated financial services,
and it is demonstrated through three illustrative cases and a weighting sensitivity analysis. The analysis shows
that clear-cut cases are stable under alternative weightings, while borderline cases are sensitive to organisational
context, which is precisely where structured review adds most value. Limitations, including subjective scoring,
possible misuse of the security override and the absence of empirical validation, are discussed explicitly.
should be implemented as a native module in Kotlin or Swift or remain in the shared JavaScript layer. In practice
this decision is rarely made systematically. It is shaped by individual familiarity, delivery pressure and precedent,
and over several years it produces fragmented native layers that are difficult to maintain, audit or hand over. This
study proposes a governance framework for making the native/shared decision consistently. The framework
combines four criteria (performance sensitivity, security and compliance requirements, platform capability access,
and long-term maintainability and team capability) into a 0–12 scoring model with three decision bands and an
explicit security override. It is accompanied by a three-layer reference architecture and a lightweight governance
process built around existing architecture reviews, a native module register, a periodic review cadence and
deliberate deprecation. The framework was developed through a design-oriented, practitioner-informed
methodology drawing on more than fifteen years of enterprise software delivery in regulated financial services,
and it is demonstrated through three illustrative cases and a weighting sensitivity analysis. The analysis shows
that clear-cut cases are stable under alternative weightings, while borderline cases are sensitive to organisational
context, which is precisely where structured review adds most value. Limitations, including subjective scoring,
possible misuse of the security override and the absence of empirical validation, are discussed explicitly.
Keywords
React Native, Native Modules, Mobile Architecture, Architecture Governance, Cross-Platform Development, Architecture Decision Records
References
1) Apple Inc. (2024). Apple platform security guide.
https://support.apple.com/guide/security/welcome/web
2) Avelino, G., Passos, L., Hora, A., & Valente, M. T. (2016). A novel approach for estimating truck
factors. In Proceedings of the 24th IEEE International Conference on Program Comprehension (ICPC)
(pp. 1–10). IEEE. https://doi.org/10.1109/ICPC.2016.7503718
3) Avgeriou, P., Kruchten, P., Ozkaya, I., & Seaman, C. (2016). Managing technical debt in software
engineering (Dagstuhl Seminar 16162). Dagstuhl Reports, 6(4), 110–138.
https://doi.org/10.4230/DagRep.6.4.110
4) Bass, L., Clements, P., & Kazman, R. (2021). Software architecture in practice (4th ed.). AddisonWesley.
5) Biørn-Hansen, A., Grønli, T.-M., & Ghinea, G. (2018). A survey and taxonomy of core concepts and
research challenges in cross-platform mobile development. ACM Computing Surveys, 51(5), Article
108. https://doi.org/10.1145/3241739
6) Biørn-Hansen, A., Rieger, C., Grønli, T.-M., Majchrzak, T. A., & Ghinea, G. (2020). An empirical
investigation of performance overhead in cross-platform mobile development frameworks. Empirical
Software Engineering, 25, 2997–3040. https://doi.org/10.1007/s10664-020-09827-6
7) Financial Conduct Authority. (2021). Building operational resilience (Policy Statement PS21/3).
https://www.fca.org.uk/publications/policy-statements/ps21-3-building-operational-resilience
8) Fowler, M. (2002). Patterns of enterprise application architecture. Addison-Wesley.
9) Google LLC. (2024). Android keystore system. Android Developers.
https://developer.android.com/privacy-and-security/keystore
10) Grassi, P. A., Fenton, J. L., Newton, E. M., Perlner, R. A., Regenscheid, A. R., Burr, W. E., Richer, J.
P., Lefkovitz, N. B., Danker, J. M., Choong, Y.-Y., Greene, K. K., & Theofanos, M. F. (2017). Digital
identity guidelines: Authentication and lifecycle management (NIST Special Publication 800-63B).
National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-63b
11) Hevner, A. R., March, S. T., Park, J., & Ram, S. (2004). Design science in information systems
research. MIS Quarterly, 28(1), 75–105. https://doi.org/10.2307/25148625
12) Jansen, A., & Bosch, J. (2005). Software architecture as a set of architectural design decisions. In
Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA) (pp. 109–
120). IEEE. https://doi.org/10.1109/WICSA.2005.61
13) Kruchten, P., Nord, R. L., & Ozkaya, I. (2012). Technical debt: From metaphor to theory and practice.
IEEE Software, 29(6), 18–21. https://doi.org/10.1109/MS.2012.167
14) Kruchten, P., Nord, R., & Ozkaya, I. (2019). Managing technical debt: Reducing friction in software
development. Addison-Wesley.
15) Meta Platforms. (2024a). About the new architecture. React Native.
https://reactnative.dev/architecture/landing-page
16) Meta Platforms. (2024b). Native modules: Introduction. React Native.
https://reactnative.dev/docs/native-modules-intro
17) Nagappan, M., & Shihab, E. (2016). Future trends in software engineering research for mobile apps. In
Proceedings of the 23rd IEEE International Conference on Software Analysis, Evolution, and
Reengineering (SANER) (pp. 21–32). IEEE. https://doi.org/10.1109/SANER.2016.88
18) Nygard, M. (2011, November 15). Documenting architecture decisions. Cognitect.
https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions
19) Ogata, M., Franklin, J., Voas, J., Sritapan, V., & Quirolgico, S. (2019). Vetting the security of mobile
applications (NIST Special Publication 800-163, Rev. 1). National Institute of Standards and
Technology. https://doi.org/10.6028/NIST.SP.800-163r1
20) OWASP Foundation. (2024). OWASP mobile application security verification standard (MASVS) and
mobile application security testing guide (MASTG). https://mas.owasp.org/
21) PCI Security Standards Council. (2017). Mobile payment acceptance security guidelines for merchants
(Version 2.0). https://www.pcisecuritystandards.org/
22) Runeson, P., & Höst, M. (2009). Guidelines for conducting and reporting case study research in
software engineering. Empirical Software Engineering, 14(2), 131–164.
https://doi.org/10.1007/s10664-008-9102-8
23) Saaty, T. L. (2008). Decision making with the analytic hierarchy process. International Journal of
Services Sciences, 1(1), 83–98. https://doi.org/10.1504/IJSSCI.2008.017590
24) Tyree, J., & Akerman, A. (2005). Architecture decisions: Demystifying architecture. IEEE Software,
22(2), 19–27. https://doi.org/10.1109/MS.2005.27
25) Weinreich, R., & Groher, I. (2016). Software architecture knowledge management approaches and
their support for knowledge management activities: A systematic literature review. Information and
Software Technology, 80, 265–286. https://doi.org/10.1016/j.infsof.2016.09.007
26) Wieringa, R. J. (2014). Design science methodology for information systems and software engineering.
Springer. https://doi.org/10.1007/978-3-662-43839-8
https://support.apple.com/guide/security/welcome/web
2) Avelino, G., Passos, L., Hora, A., & Valente, M. T. (2016). A novel approach for estimating truck
factors. In Proceedings of the 24th IEEE International Conference on Program Comprehension (ICPC)
(pp. 1–10). IEEE. https://doi.org/10.1109/ICPC.2016.7503718
3) Avgeriou, P., Kruchten, P., Ozkaya, I., & Seaman, C. (2016). Managing technical debt in software
engineering (Dagstuhl Seminar 16162). Dagstuhl Reports, 6(4), 110–138.
https://doi.org/10.4230/DagRep.6.4.110
4) Bass, L., Clements, P., & Kazman, R. (2021). Software architecture in practice (4th ed.). AddisonWesley.
5) Biørn-Hansen, A., Grønli, T.-M., & Ghinea, G. (2018). A survey and taxonomy of core concepts and
research challenges in cross-platform mobile development. ACM Computing Surveys, 51(5), Article
108. https://doi.org/10.1145/3241739
6) Biørn-Hansen, A., Rieger, C., Grønli, T.-M., Majchrzak, T. A., & Ghinea, G. (2020). An empirical
investigation of performance overhead in cross-platform mobile development frameworks. Empirical
Software Engineering, 25, 2997–3040. https://doi.org/10.1007/s10664-020-09827-6
7) Financial Conduct Authority. (2021). Building operational resilience (Policy Statement PS21/3).
https://www.fca.org.uk/publications/policy-statements/ps21-3-building-operational-resilience
8) Fowler, M. (2002). Patterns of enterprise application architecture. Addison-Wesley.
9) Google LLC. (2024). Android keystore system. Android Developers.
https://developer.android.com/privacy-and-security/keystore
10) Grassi, P. A., Fenton, J. L., Newton, E. M., Perlner, R. A., Regenscheid, A. R., Burr, W. E., Richer, J.
P., Lefkovitz, N. B., Danker, J. M., Choong, Y.-Y., Greene, K. K., & Theofanos, M. F. (2017). Digital
identity guidelines: Authentication and lifecycle management (NIST Special Publication 800-63B).
National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-63b
11) Hevner, A. R., March, S. T., Park, J., & Ram, S. (2004). Design science in information systems
research. MIS Quarterly, 28(1), 75–105. https://doi.org/10.2307/25148625
12) Jansen, A., & Bosch, J. (2005). Software architecture as a set of architectural design decisions. In
Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA) (pp. 109–
120). IEEE. https://doi.org/10.1109/WICSA.2005.61
13) Kruchten, P., Nord, R. L., & Ozkaya, I. (2012). Technical debt: From metaphor to theory and practice.
IEEE Software, 29(6), 18–21. https://doi.org/10.1109/MS.2012.167
14) Kruchten, P., Nord, R., & Ozkaya, I. (2019). Managing technical debt: Reducing friction in software
development. Addison-Wesley.
15) Meta Platforms. (2024a). About the new architecture. React Native.
https://reactnative.dev/architecture/landing-page
16) Meta Platforms. (2024b). Native modules: Introduction. React Native.
https://reactnative.dev/docs/native-modules-intro
17) Nagappan, M., & Shihab, E. (2016). Future trends in software engineering research for mobile apps. In
Proceedings of the 23rd IEEE International Conference on Software Analysis, Evolution, and
Reengineering (SANER) (pp. 21–32). IEEE. https://doi.org/10.1109/SANER.2016.88
18) Nygard, M. (2011, November 15). Documenting architecture decisions. Cognitect.
https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions
19) Ogata, M., Franklin, J., Voas, J., Sritapan, V., & Quirolgico, S. (2019). Vetting the security of mobile
applications (NIST Special Publication 800-163, Rev. 1). National Institute of Standards and
Technology. https://doi.org/10.6028/NIST.SP.800-163r1
20) OWASP Foundation. (2024). OWASP mobile application security verification standard (MASVS) and
mobile application security testing guide (MASTG). https://mas.owasp.org/
21) PCI Security Standards Council. (2017). Mobile payment acceptance security guidelines for merchants
(Version 2.0). https://www.pcisecuritystandards.org/
22) Runeson, P., & Höst, M. (2009). Guidelines for conducting and reporting case study research in
software engineering. Empirical Software Engineering, 14(2), 131–164.
https://doi.org/10.1007/s10664-008-9102-8
23) Saaty, T. L. (2008). Decision making with the analytic hierarchy process. International Journal of
Services Sciences, 1(1), 83–98. https://doi.org/10.1504/IJSSCI.2008.017590
24) Tyree, J., & Akerman, A. (2005). Architecture decisions: Demystifying architecture. IEEE Software,
22(2), 19–27. https://doi.org/10.1109/MS.2005.27
25) Weinreich, R., & Groher, I. (2016). Software architecture knowledge management approaches and
their support for knowledge management activities: A systematic literature review. Information and
Software Technology, 80, 265–286. https://doi.org/10.1016/j.infsof.2016.09.007
26) Wieringa, R. J. (2014). Design science methodology for information systems and software engineering.
Springer. https://doi.org/10.1007/978-3-662-43839-8