Hmm… I agree and disagree at the same time. To elaborate:
On one hand, I can see the value of building a Meteor app and rolling it out simultaneously for web, iOS, and Android. Yes, the mobile apps won’t feel 100% native, but some clients don’t care. They just want a presence in the AppStore/Google Play Store.
On the other hand, I’m working on a mobile app now using Meteor/Cordova, and there are definitely some frustrations involved. I have to come up with hacks to make it feel more native, such as gestures that people are used to (swipe from left edge = go back). Or even the work involved in having a page/card that slides onto the screen when you drill down into item detail just feels like too much work. On top of that, even though it’s a mobile app, it still needs to connect to a Meteor server for reasons that I feel are totally unnecessary (e.g. Facebook OAuth), so you have to have the server counterpart running somewhere. For mobile apps that are only fetching data from a REST API and not storing data in a database, it doesn’t make a lot of sense to me.
I’ve started to get into React Native, and am super impressed so far. It’s pretty refreshing to not have to think about grid columns, and instead use flexbox for everything.