4 ms·

Yeah - however IMO large growth isn't as important until some semblance of PMF is hit with a few core users. Then can treat the other platform as a marketing c

Yeah - however IMO large growth isn't as important until some semblance of PMF is hit with a few core users. Then can treat the other platform as a marketing cost - i.e. if you're making 75k on iOS and predict a similar revenue for Android it's worth it to hire an Android developer for to build it out. But if one hasn't yet found a few hundred quality users on one platform why build the other one.

thih9 3y ago
For some apps, cross platform mobile development and finding core users across larger audience can be easier than going native and finding core users on a single platform. There can be probably other reasons too.
artifabrian 3y ago
I agree with this and reflects my personal experience. While potencial of a large audience is great, if you don't even have users to start with, the choice should be the response to "what gets PMF faster" and not "what do I need to take me from 500k ARR to +2M ARR".
a_wild_dandan 3y ago
Why target one platform when your project can target all major platforms (web, iOS, Android, MacOS/Windows/Linux)? Especially if you're already experienced with React and can later hire from that monstrous talent pool? Hell, instead of casting that wider net for users, you could still only release/focus on iOS, but still have tons of work done when you're ready to move your React app to those other platforms.
- scarface_74 3y ago
  Because your app will equally suck on all platforms?
  - thih9 3y ago
    You might not be the target user - and actual target users might not care about the native vs react native app UX.
  - mkss 3y ago
    Because your app will work on all platforms and the rest of the billions of app users outside of this little niche-of-a-niche-of-a-niche forum just want to do whatever they need to get done on a app in their normal lives and don't even know what you are talking about when you say the app "sucks" because it doesn't use exactly the right rounded corners on a button or the listview scroll physics are exactly same as a "native" app.
    - scarface_74 3y ago
      Until the people wonder why it doesn’t do $x new feature that Apple released a year ago but there is no cross platform equivalent. But more importantly, why it doesn’t take advantage of an accessibility feature that that a native app would get for free.

thih9 3y ago

For some apps, cross platform mobile development and finding core users across larger audience can be easier than going native and finding core users on a single platform. There can be probably other reasons too.

artifabrian 3y ago

I agree with this and reflects my personal experience. While potencial of a large audience is great, if you don't even have users to start with, the choice should be the response to "what gets PMF faster" and not "what do I need to take me from 500k ARR to +2M ARR".

a_wild_dandan 3y ago

Why target one platform when your project can target all major platforms (web, iOS, Android, MacOS/Windows/Linux)? Especially if you're already experienced with React and can later hire from that monstrous talent pool? Hell, instead of casting that wider net for users, you could still only release/focus on iOS, but still have tons of work done when you're ready to move your React app to those other platforms.

scarface_74 3y ago
Because your app will equally suck on all platforms?
- thih9 3y ago
  You might not be the target user - and actual target users might not care about the native vs react native app UX.
- mkss 3y ago
  Because your app will work on all platforms and the rest of the billions of app users outside of this little niche-of-a-niche-of-a-niche forum just want to do whatever they need to get done on a app in their normal lives and don't even know what you are talking about when you say the app "sucks" because it doesn't use exactly the right rounded corners on a button or the listview scroll physics are exactly same as a "native" app.
  - scarface_74 3y ago
    Until the people wonder why it doesn’t do $x new feature that Apple released a year ago but there is no cross platform equivalent. But more importantly, why it doesn’t take advantage of an accessibility feature that that a native app would get for free.