<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>sebleon</author><text>My take is that RN is great for demo apps or simple UIs, but I would not choose it for a production app where performance matters (ie. using camera, audio, custom controls, platform-specific SDKs, multi-threading, etc). You&amp;#x27;re definitely going to do heavy lifting in native code, and a hybrid app quickly becomes a mess. Dealing with multiple environments and super slow build times in Xcode will seriously slow down development cycles.&lt;p&gt;IMO RN is no exception to the Simple vs Easy trade-off [1] Not to mention using RN gives FB a legal blank check from your company [2]&lt;p&gt;[1] &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;chrisfrost.com&amp;#x2F;wp-content&amp;#x2F;uploads&amp;#x2F;SimpleVsEasy-478x512.png&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;chrisfrost.com&amp;#x2F;wp-content&amp;#x2F;uploads&amp;#x2F;SimpleVsEasy-478x51...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;@raulk&amp;#x2F;if-youre-a-startup-you-should-not-use-react-reflecting-on-the-bsd-patents-license-b049d4a67dd2&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;@raulk&amp;#x2F;if-youre-a-startup-you-should-not-...&lt;/a&gt;</text><parent_chain><item><author>jjeaff</author><text>In my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won&amp;#x27;t work well with RN), then deploy to both at once. We have had excellent results.</text></item><item><author>sebleon</author><text>The logic still applies.&lt;p&gt;1. Start with platform you&amp;#x27;re most comfortable with.
2. Iterate on product until you have a winning formula
3. Replicate on 2nd platform to double revenues&lt;p&gt;Building is a lot easier than identifying what to build, better to speedily experiment on one platform.</text></item><item><author>Pharaoh2</author><text>This may have been historically true, but our internal data shows us that starting early 2017, people in tier 1 countries were equally likely to pay and have comparable LTV on both platforms.&lt;p&gt;And if you also going to launch in EU&amp;#x2F;Australia&amp;#x2F;Canada, you will have a nearly 50-50 split of ios and android users on a platform neutral app.&lt;p&gt;So the classical logic of implementing on iOS first doesn&amp;#x27;t really apply anymore. Now its more, implement first on the platform you are comfortable with but don&amp;#x27;t forget about the other platform because there is a equal amount of money to be made there...&lt;p&gt;PS: Data excludes low end iOS and android devices. (&amp;lt; SE, old iPads&amp;#x2F;iPods, old and cheap android devices). These devices have extremely low conversion on both platforms anyway.</text></item><item><author>sidlls</author><text>If I were to seriously attempt to commercialize the toy apps I build for my kids&amp;#x2F;family I&amp;#x27;d go iOS first easily. People with Apple devices are far likelier to pay, and Android development is, in my view, an inferior experience (although Kotlin makes it marginally less so these days).</text></item><item><author>mullingitover</author><text>And just like that, by dropping Android support, Buddybuild goes from viable solution to total non-starter. Does any serious mobile app development these days really go all-in on one platform?</text></item></parent_chain></comment><story><title>Apple acquires Buddybuild</title><url>https://www.buddybuild.com/blog/buddybuild-is-now-part-of-apple</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ewjordan</author><text>React Native is great for apps, and if it&amp;#x27;s a game, just use Unity. They&amp;#x27;re building up their internal CI infrastructure and it works better every month.&lt;p&gt;Tbh, I&amp;#x27;m not sure how many use cases don&amp;#x27;t fit either React Native or Unity, I&amp;#x27;d practically never choose to do an app another way these days.</text><parent_chain><item><author>jjeaff</author><text>In my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won&amp;#x27;t work well with RN), then deploy to both at once. We have had excellent results.</text></item><item><author>sebleon</author><text>The logic still applies.&lt;p&gt;1. Start with platform you&amp;#x27;re most comfortable with.
2. Iterate on product until you have a winning formula
3. Replicate on 2nd platform to double revenues&lt;p&gt;Building is a lot easier than identifying what to build, better to speedily experiment on one platform.</text></item><item><author>Pharaoh2</author><text>This may have been historically true, but our internal data shows us that starting early 2017, people in tier 1 countries were equally likely to pay and have comparable LTV on both platforms.&lt;p&gt;And if you also going to launch in EU&amp;#x2F;Australia&amp;#x2F;Canada, you will have a nearly 50-50 split of ios and android users on a platform neutral app.&lt;p&gt;So the classical logic of implementing on iOS first doesn&amp;#x27;t really apply anymore. Now its more, implement first on the platform you are comfortable with but don&amp;#x27;t forget about the other platform because there is a equal amount of money to be made there...&lt;p&gt;PS: Data excludes low end iOS and android devices. (&amp;lt; SE, old iPads&amp;#x2F;iPods, old and cheap android devices). These devices have extremely low conversion on both platforms anyway.</text></item><item><author>sidlls</author><text>If I were to seriously attempt to commercialize the toy apps I build for my kids&amp;#x2F;family I&amp;#x27;d go iOS first easily. People with Apple devices are far likelier to pay, and Android development is, in my view, an inferior experience (although Kotlin makes it marginally less so these days).</text></item><item><author>mullingitover</author><text>And just like that, by dropping Android support, Buddybuild goes from viable solution to total non-starter. Does any serious mobile app development these days really go all-in on one platform?</text></item></parent_chain></comment><story><title>Apple acquires Buddybuild</title><url>https://www.buddybuild.com/blog/buddybuild-is-now-part-of-apple</url></story>