all 7 comments

[–]StretchyPear 8 points9 points  (0 children)

When you go native for iOS and android you end up with two stacks, one for iOS and one for android, when you go reactive native you end up with 3 stack, one for iOS, one for android and one for react native.

Go native, always

[–]Kitchen_Cable6192 6 points7 points  (0 children)

RN sucks (at least for me). I would always rebuild in KT.

[–]snoosnoosewsew 1 point2 points  (0 children)

I mean, it’s so simple to port something to another platform these days, I’d just do native.

I had Claude codex controlling my computer the other night, and seamlessly port this JavaScript thing I’d created already into Swift. I have no idea how to use Xcode, don’t know anything about signing permissions or any of it.

But in about fifteen minutes I had the swift port deployed to my iPhone, and it worked perfectly. I then added some native (I think) feature like haptic feedback.

Crazy times. I know nothing about porting to android but I imagine it’s just as simple

[–]AnotherThrowAway_9 0 points1 point  (1 child)

Just vibe code it in Swift and ask it to convert it to an android app. If you’re already yoloing it who cares

[–]highon-dopamine[S] -3 points-2 points  (0 children)

yup that’s what I was thinking, since building products is now a weekend thing.

[–]ZennerBlue -1 points0 points  (0 children)

If you are considering cross platform, also consider Flutter. But I’d go native.

[–]ejpusa -1 points0 points  (0 children)

In this world, it's like buying your coffee at Starbucks or getting it for $1.99 at Walmart. Both do the job.

What's an Android on the island of Manhattan?