I've been struggling for about 2 days to get a basic Expo project running with Vapi, and it's become clear that web development is the primary focus while Expo support feels like an afterthought.
I initially tried adding Vapi to my existing, mostly-built app, which should have been straightforward - an hour at most. Instead, I encountered constant dependency conflicts that made integration impossible. I had to completely restart using your official template just to match the old dependency versions, and while I finally got that working, I can't integrate the rest of my app because everything conflicts.
The repository was updated yesterday, but the README wasn't updated to match, and somehow things got worse. The repo now has zero UI components, the App.js file was removed with nothing to replace it, and I'm hitting issues at every step. The inconsistencies between the repository state and documentation are creating major roadblocks.
This has been genuinely disappointing. I've spent countless hours debugging problems that shouldn't exist for what's supposed to be an official integration. I'm working on the Vapi build competition with a personal project I'm taking seriously, and this experience has eaten into my competition time and honestly killed my motivation.
Since this isn't some random community repository, the back-and-forth just to get something basic running feels unacceptable. I need clear documentation that matches the current repository state, a working Expo integration example with current dependency versions, and guidance on resolving conflicts when integrating with existing applications.