Rebuild app in React Native

[kodjima33]

Let's fully rebuild main omi ai app in React Native (there is a bigger community)

how we will assign this task:

1. please try to build an example of omi in react and send demo
2. or send links your best react projects with the biggest traction (how many users/revenue)
   /bounty $20000

This is a multi-month project that requires:

• previous successful react projects with hundreds of thousands of users
• or traveling to San francisco to build from our office

--

thinh's comments: resources that might help #1944 (comment)

[algora-pbc]

💎 $20,000 bounty • omi

Steps to solve:

1. Start working: Comment /attempt #1944 with your implementation plan
2. Submit work: Create a pull request including /claim #1944 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to BasedHardware/omi!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @bibekkd	Mar 4, 2025, 11:17:35 AM	WIP
🔴 @Rutik7066	Mar 4, 2025, 6:09:50 PM	WIP
🟢 @ryenguyen7411	Mar 4, 2025, 6:16:32 PM	WIP
🟢 @Myestery	Mar 5, 2025, 2:49:44 PM	WIP
🔴 @shivansh193	Mar 5, 2025, 8:12:53 PM	WIP
🟢 @kamolesh97	Mar 10, 2025, 2:06:16 PM	WIP
🟢 @itsparser	Mar 22, 2025, 4:28:29 AM	WIP
🟢 @Raheman-08	Mar 26, 2025, 6:22:28 PM	WIP

[kodjima33]

cool example https://github.com/ex3ndr/glassium

[bibekkd]

/attempt #1944

I have decided to implement this using the tech stack and dependencies similar to the Glassium project. This will ensure a modern, scalable, and high-performance React Native implementation of Omi.

Implementation Plan

1️⃣ Project Setup & Dependencies

• Initialize a new React Native Expo project (npx create-expo-app@latest).
• Use Expo Router for file-based routing.
• Configure TanStack Query or Jotai for state management as per requirement.

2️⃣ Core Features Implementation

• Replicate Omi’s core functionalities using React Native components.
• As AI integration with a backend already exists, I don’t need to worry about it.
• Optimize performance and responsiveness.
• Lock the feature to the current version 1.0.57.

3️⃣ UI/UX Design

• Create a modern and intuitive UI inspired by the original Omi app.
• Ensure the design is mobile-friendly and accessible.

4️⃣ Testing & Debugging

• Write unit and integration tests using Jest and React Native Testing Library.
• Debug and optimize performance.

5️⃣ Final Review & Submission

• Ensure all functionalities match the existing Omi app.
• Document the setup and usage instructions.
• Submit a PR with /claim #1944 for review.

Let me know if you need any changes before I proceed! 🚀

Options

• Cancel my attempt

[nishantkluhera]

Hello, I have a few queries about this task:

1. If assigned what might be the timeline for the final app delivery
2. For the demo what might be the expected core functionalities
3. What are the expected features for v1 of the rebuild
4. Can we work as a team of 2-3 for the rebuild
5. Any specific requirement you might want us to keep in mind
6. How will the rebuild go along with the other functionalities/services that are being built in parallel

@kodjima33

[PaperBoardOfficial]

After checking out your Omi app code, I'd strongly recommend using React Native CLI instead of Expo for the conversion. Expo's limitations with Bluetooth and native modules would be a dealbreaker for your device integration. Also, one would definitely need an actual Omi device for testing - there's no way to properly simulate your custom BLE protocol, firmware updates, or audio processing. Bluetooth connections are too unpredictable to rely on mocks alone, and one would risk building something that works in theory but fails with real hardware. Another challenge will be recreating your background services for continuous device communication and the audio processing pipeline with the Opus codec - these are non-trivial to implement in React Native and would require careful testing with the actual device.

[bibekkd]

I don’t have any issue with this; I can use React Native CLI instead of Expo to handle Bluetooth and native modules properly.

Other than this, are there any additional conditions or specific requirements I should follow for device integration, background services, or the audio processing pipeline? Let me know if there are any key considerations before I proceed.

[PaperBoardOfficial]

How would you do E2E testing without the omi friend device?

[bibekkd]

As I am building the main Omi AI app, most of the functionalities can be tested using mobile devices or an emulator. In cases where the Omi Friend device is required, I will collaborate with individuals who have access to one to ensure proper testing.

[rutikthakre]

/attempt #1944
@bibekkd How about collab?

Algora profile	Completed bounties	Tech	Active attempts	Options
@Rutik7066	12 bounties from 9 projects	Go, TypeScript, Rust & more		Cancel attempt

[ryenguyen7411]

/attempt #1944

Hey @kodjima33 and the Omi team! 👋

My team (based in Vietnam) and I are excited about rebuilding the Omi AI app in React Native. Here’s our straightforward plan to tackle this:

Tech Stack

• React Native + Expo: The go-to combo for scalable, high-performance apps.
• State Management:
  • TanStack Query: For handling API calls.
  • Zustand: Lightweight and modern for local state needs.
• Styling:
  • I’ve built a Tailwind-like utility-first solution (way before NativeWind existed 😄). Key values:
    • Write CSS directly (supports variables, calc, media queries, dark mode). Cascading styles also work, yes, you can define style like color, font-size, … at root component and it will apply to all descendent!!
    • Auto-handles unsupported React Native styles (e.g., outline, position: fixed).
• Testing: Focus on critical features with unit tests (100% coverage might be tough, but we’ll prioritize stability).

---

Task Breakdown & ETA

Rough estimate: ~90 days (ETA might not be very accurate at this point).

Screen 1: Onboarding

• Simple multi-step UI.
• Persist state to storage so it doesn’t reappear after setup.

Screen 2: Home

• Audio recording will be handled by expo-av library.
• Otherwise there’re full of basic UI + API calls, so I will use TanStack Query for best performance.

Screen 3: Chat

• Streaming API integration (it works well in the current app, should not be a problem with React Native).

Screen 4: Explore

• It has couple of filter/search functionality, also app listings.
• For WebView implementation for subscribed apps, we can consider following 2 options:
  • Option 1: react-native-webview (seamless but less secure).
  • Option 2: react-native-inappbrowser (uses system browsers for better security).

Screen 5: User & Settings

• Multiple sub-screens handled with react-native-bottom-sheet for smooth transitions.

---

Libraries for Performance

• Animation/UI: react-native-reanimated, react-native-gesture-handler.
• Navigation: Expo Router (stable and flexible).

---

Engineer Team Lineup 👨💻

Lead Engineer - @ryenguyen7411

• 8+ years with React (ReactJS + React Native).
• Owns: App architecture, core features, and code quality.
• Bonus superpower: Deep React ecosystem knowledge (state patterns, component architecture) from years of web + mobile work.

Senior Mobile Engineer - @phuongddx

• 7+ years in native mobile (iOS/Android) + 3 years React Native.
• Brings: Platform-specific optimization hacks and cross-device polish.

Let me know if you’d like to tweak any part of this plan! Happy to discuss details or adjust timelines based on your needs. 🚀

Cheers,
Rye Nguyen

Options

• Cancel my attempt

[beastoin]

hi folks, tell us more about how you understand the main omi ai app. we want to ensure you haven’t missed any important core features that could prevent you from building a good product.

regarding the tech stack, I care about:

1. how big and experienced the community is.
2. how simple the technology (tech stack) is.
3. any limitations.

regarding the product (app), I care about:

4. how straightforward(and, solid) the architecture is (connectivity management, data flow, state management).
5. how convenient the UX is.

regarding you (your team), I care about:

6. how much experience you have.
7. how fast you can deliver a high-quality (9/10) product.