2026-09-19T13:52:59Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/1449102022-08-30T03:32:05Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Madden, Samuel
Wang, Alexander
Li, Yanlin
Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science
2022-08-29T16:20:20Z
2022-08-29T16:20:20Z
2022-05
2022-05-27T16:19:18.627Z
https://hdl.handle.net/1721.1/144910
https://orcid.org/0000-0002-1986-4664
Mobile application development frequently requires usage of third-party software development toolkits (SDKs), which usually come in two variants, Android and iOS. This necessitates two separate workflows and expertise to create the application on both platforms, rendering the native development process both time-intensive and costly. Although the emergence of cross-platform frameworks like React Native attempts to streamline the process by allowing developers to share code on multiple operating systems via a single code base, many SDKs provide no React Native integration — a bridge must be built out of the native versions.
In this thesis, we present a React Native bridging library for Cambridge Mobile Telematics’ Android and iOS SDKs. We explore and evaluate abstraction and implementation strategies for mitigating differences between the two SDKs and platforms. Accompanying the library is the React Native Sample App, which demonstrates the library in action. We then evaluate the React Native Sample App by comparing first its line count and secondly its performance against native versions of sample applications previously built by CMT. Finally, we suggest possible software design choices that can facilitate cross-platform development. Our results suggest that a bridging library, on a cross-platform framework, is promising in improving code portability and thus reducing development effort in building mobile applications.
M.Eng.
Massachusetts Institute of Technology
In Copyright - Educational Use Permitted
Copyright MIT
http://rightsstatements.org/page/InC-EDU/1.0/
Building a Cross-Platform Bridging Library for Native Mobile SDKs
Thesis
application/pdf
Master
Master of Engineering in Electrical Engineering and Computer Science
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="8c526c95-c876-4efa-888b-2019579ac5ab">
<Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type>
<Title>Building a Cross-Platform Bridging Library for Native Mobile SDKs</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2022-05</PublicationDate>
<Authors>
<Author>
<DisplayName>Li, Yanlin</DisplayName>
<Affiliation>
<OrgUnit>
</OrgUnit>
</Affiliation>
</Author>
</Authors>
<Editors>
</Editors>
<Publishers>
<Publisher>
<DisplayName>Massachusetts Institute of Technology</DisplayName>
<OrgUnit />
</Publisher>
</Publishers>
<License>http://rightsstatements.org/page/InC-EDU/1.0/</License>
<Abstract>Mobile application development frequently requires usage of third-party software development toolkits (SDKs), which usually come in two variants, Android and iOS. This necessitates two separate workflows and expertise to create the application on both platforms, rendering the native development process both time-intensive and costly. Although the emergence of cross-platform frameworks like React Native attempts to streamline the process by allowing developers to share code on multiple operating systems via a single code base, many SDKs provide no React Native integration — a bridge must be built out of the native versions.
In this thesis, we present a React Native bridging library for Cambridge Mobile Telematics’ Android and iOS SDKs. We explore and evaluate abstraction and implementation strategies for mitigating differences between the two SDKs and platforms. Accompanying the library is the React Native Sample App, which demonstrates the library in action. We then evaluate the React Native Sample App by comparing first its line count and secondly its performance against native versions of sample applications previously built by CMT. Finally, we suggest possible software design choices that can facilitate cross-platform development. Our results suggest that a bridging library, on a cross-platform framework, is promising in improving code portability and thus reducing development effort in building mobile applications.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>