dean_mcpherson

I don't have many connections to the #buildinpublic community though, so I'm trying out running a giveaway to get connected.

Dubble made $1024 USD in January - so the idea is that I'm going to give away all of February's revenue to the person who guesses the closest amount.

I'll be submitting updates on how this works out as a campaign on Indie Hackers and Twitter (@dean_mcpherson) if you want to see if silly give aways help, hinder or do not much at all

The update prompt is actually from http://microsoft.github.io/code-push/ which allows us to push minor updates directly to the app without going via the app store. Say goodbye to 2 week time cycles. A newer release of Code Push actually doesn't prompt the user at all, and can download an update during use and load it when the app goes inactive.

I've been using React Native on iOS in production since last November for http://townske.com/app,

Over that period, I did hit some performance issues, but the vast majority of those were implementation flaws (i.e. my fault), not framework flaws. Real user feedback has been overwhelmingly positive, including being featured in the app store multiple times.

I just launched another app for iOS and Android last weekend (https://curbitapp.com) that was built with React Native in a few weeks, and shares about 80% of the codebase. I haven't spent any time optimising these apps for performance, other than following standard react best practices and see sufficient performance on both iOS and Android.

For someone who has a web background, React Native is a no brainer. 60fps native UI is generally attainable, you can use the exact same tooling (good dev tools, hot reloading), and you have the ability to pick up a large chunk of your code and put it on Android, or web, or now potentially OSX.