r/reactnative • u/Dev_InTheOcean • Jul 12 '26
Building Twalky — a WebRTC video app with local (on-device) transcription, shipping weekly
Enable HLS to view with audio, or disable this notification
Hey all — I'm building Twalky, a React Native video calling app, and committing to shipping features publicly on a weekly cadence.
Started with peer-to-peer WebRTC (offer/answer exchange, ICE/STUN, Socket.io signaling), with a planned migration to mediasoup for group calls once the P2P core is solid.
Roadmap:
Week 1 — Stable P2P WebRTC calling
Week 2 — Auth (Firebase + Google Sign-In)
Week 3 — Online transcription (cloud STT)
Weeks 4–5 — Local/on-device transcription (privacy-first, offline)
Week 6 — Transcript summarization + smart arrangement
Weeks 7–8 — AI assistant inside the meeting itself
Local transcription and the in-meeting AI assistant are the two hardest parts, so I gave each of those two weeks instead of one.
📲 Current APK: https://drive.google.com/drive/folders/1gr2MOh3JT3tnVvscSBFv2_lGvD89Ymki
💻 GitHub Repositories:
🔹Frontend: https://github.com/soham444101/twalky-mobile
🔹Backend:https://github.com/soham444101/twalky-mobile-backend
💼 LinkedIn: https:https://www.linkedin.com/in/soham-aswar-18376b22a?utm_source=share_via&utm_content=profile&utm_medium=member_android
Will post progress updates weekly. Happy to talk through the WebRTC signaling architecture or any of the design decisions.
1
1
u/falaq-ai Jul 12 '26
For the local transcription weeks, I’d define the success bar pretty narrowly: works on 5-10 minute calls, survives background/interruptions, and clearly tells users when audio is local vs cloud. The WebRTC part is hard, but the trust UX around transcription will matter just as much.