-
Notifications
You must be signed in to change notification settings - Fork 10
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.
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
Make SDK work with React Native #75
Comments
Make the Fedimint Web SDK Work with React NativeScope overview: Enable the fedimint-client SDK to function within React Native environments, sharing library code with the existing web SDK. BackgroundOur current SDK includes a WebAssembly (WASM) bundle that exposes the Rust-based fedimint-client to web applications. This setup allows web environments to interact seamlessly with the fedimint client. However, React Native—a popular framework for building native/mobile apps using React—cannot directly leverage the existing WASM bundle due to environment differences between web and native mobile platforms. Objective
Scope of Work1. UniFFI Bindings for React Native
2. Architecting Shared Library Code
3. Testing and Validation
Deliverables
Acceptance Criteria
Additional Information
Challenges to Anticipate
References:Note: This bounty aims to expand our SDK’s reach to mobile platforms via React Native, promoting broader adoption and community engagement. Your contribution will play a crucial role in achieving this goal. |
@maan2003 take a look |
fedimint react native is not going to be fun we have to bundle rocksdb, and doing it as a library is not great :/ |
sad... any way around using rocks? Can we get a lighter-weight version of the DB with similar guarantees? |
Is that a problem if we just leave it to the rust RocksDB crate? That is statically linking by default anyway, right? We only do dynamic linking because it avoids recompiling it all the time. |
yea that sounds like the way to go |
@alexlwn123 can you add some context please?
1M bounty once scoped out.
The text was updated successfully, but these errors were encountered: