Comment on What is the best approach to port an iOS app to Android?
forrgott@lemmy.zip 14 hours agoThis is an absolutely terrible idea first of all debugging code that you’re completely unfamiliar with is not easier than writing your own. The code you end up with is also likely to end up being very insecure with vulnerabilities exposing both you and your users.
When people actually crunch the numbers, vibe coding does not save time. So there is nothing to offset the massive drawbacks to this approach.
okwhateverdude@lemmy.world 14 hours ago
Well, given the level of effort in the OP, I figured this was the best response. If some serious engineer came up to me and told me they wrote a whole app with some platform specific language and now are looking for tips for porting it to some other platform with some other language, I’d laugh. What else can you say other than “Learn the language of that platform and good luck with the rewrite”? You’re barking up my tree when it is OP with the very lazy fucking question.
q1p_@lemmy.zip 14 hours ago
I originally built the app just for iOS, not really planning to make an Android version. Later, I started thinking it could be worth porting to Android. The app feels totally native, clean design, well-structured code, no bugs so far, everything tested. It looks and works like an Apple pre-installed app (not even joking lol) fast, smooth, and responsive. I’m not trying to sell it or anything, it’s completely free, and I’m genuinely proud of it. Now it’s more about marketing and seeing how it does, but bringing it to Android could open it up to a bigger audience.
forrgott@lemmy.zip 13 hours ago
Umm, okay.
You’re advice was still terrible. And now you’re justifying it by making unkind and equally unfounded assumptions about the OP?
Whatever, dude.