Skip to content

docs: update swift support implementation detail for expo modules #1428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fobos531 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: update swift support implementation detail for expo modules #1428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 1 addition & 28 deletions docs/docs/resources/comparison.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -387,34 +387,7 @@ public class MathModule: Module {

#### Swift support

Just like Nitro, Expo Modules are written in Swift, instead of Objective-C.

Expo Modules however bridge through Objective-C, whereas Nitro bridges to Swift directly (using the new Swift <> C++ interop) which has proven to be much more efficient.

<div className="side-by-side-container">
<div className="side-by-side-block">

```mermaid
---
title: "Nitro Modules"
---
graph LR;
JS--> C++ --> Swift;
```

</div>
<div className="side-by-side-block">

```mermaid
---
title: "Expo Modules"
---
graph LR;
JS--> C++ --> Objective-C --> Swift;
```

</div>
</div>
Just like Nitro, Expo Modules are written in Swift, instead of Objective-C. Both bridge to Swift directly using the new Swift &lt;&gt; C++ interop which has proven to be much more efficient compared to bridging through Objective-C.

#### Kotlin coroutines

Expand Down