11–20 of 109 posts
After Compose Multiplatform has matured a bit more I'd be seriously considering using that for everything going forward.
I would use Kotlin multiplatform and Jetpack Compose multiplatform. But mainly because I already know Kotlin. It's definitively nicer than typescript though.
The only problems with Compose Multiplatform are the lack of multiplatform libraries, and documentation, but JetBrains tells me that a new documentation site is due this summer.
Purely curious; why not start natively with iOS or Droid (depending on which one your target audience uses more)? You'd have the easiest native API access and fewer headaches. Once you hit PMF & have proven the idea, add the second platform. Is there a benefit to launching on both platforms out of the gate? Unless perhaps there are specific React web assets you'd like to reuse to get up and running faster via React n…
For me, React is just easier to use than natively supporting iOS or Droid. No new languages or skills to learn.
I also found for social/marketplace apps, Droid users are the supply and iOS is the demand. Can't have one without the other.
Earlier quoted context omitted.
Because you might want to give your users a somewhat decent experience.
Depends on the specific experience you're trying to create but there are fewer and fewer cases where what you want to achieve with a mobile app cannot be done with the mobile web. I can only think of one case in my career where native was actually necessary and not the vanity of the manager having an irrational disdain of the mobile web. Or stated differently: unless it can be articulated why mobile web/PWA/hybrid ca…
Nothing beats native. 2nd best is what you know. I'm using egui right now for quickly putting together a native cross platform tool. For a startup, again I'd pick what you know. RN and Flutter will provide similar experiences for most apps. Flutter will perform better with charts etc.
Purely curious; why not start natively with iOS or Droid (depending on which one your target audience uses more)? You'd have the easiest native API access and fewer headaches. Once you hit PMF & have proven the idea, add the second platform. Is there a benefit to launching on both platforms out of the gate? Unless perhaps there are specific React web assets you'd like to reuse to get up and running faster via React n…
I guess the benefit is access to larger audience, and as a result easier growth; this could be especially important in the context of a startup.
React native imo. Expo is terrific and the library ecosystem, while it might feel like it’s one step down from web JavaScript, is still robust enough for what you need since there are more than enough people out there shipping rn apps.
My only concern with Expo is once you're using it, you're going to get charged per user and per update. It's $0.005 per user per update (plus additional bandwidth and storage charges). So if you have 100K users, that's $500 per update. One update per month would be $6K per year. So you have to factor in the economics of your app.
React native imo. Expo is terrific and the library ecosystem, while it might feel like it’s one step down from web JavaScript, is still robust enough for what you need since there are more than enough people out there shipping rn apps.
My only concern with Expo is once you're using it, you're going to get charged per user and per update. It's $0.005 per user per update (plus additional bandwidth and storage charges). So if you have 100K users, that's $500 per update. One update per month would be $6K per year. So you have to factor in the economics of your app.
Purely curious; why not start natively with iOS or Droid (depending on which one your target audience uses more)? You'd have the easiest native API access and fewer headaches. Once you hit PMF & have proven the idea, add the second platform. Is there a benefit to launching on both platforms out of the gate? Unless perhaps there are specific React web assets you'd like to reuse to get up and running faster via React n…
> Is there a benefit to launching on both platforms out of the gate? I guess the benefit is access to larger audience, and as a result easier growth; this could be especially important in the context of a startup.
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.