←back to thread

I Built My Own Audio Player

(nexo.sh)
292 points nexo-v1 | 3 comments | 22 May 25 14:09 UTC | HN request time: 0s | source
Show context
codingjerk ◴[23 May 25 07:56 UTC] No.44070837[source]▶
I feel like developing an app for iOS is harder than developing one for Android.

Everything from writing code to building and publishing is overcomplicated.

replies(2): >>44071161 #>>44072537 #
1. eddieroger ◴[23 May 25 13:08 UTC] No.44072537[source]▶
I've done both, and this was not my experience. Nowadays, they're much more similar than different, but 10 years or so ago, "easy" was defined by if you knew Java or Objective-C. Android, like most Java, required a lot of code to do simple things (public static void main...), and tons of XML to make the app support so many devices. Objective-C had good boiler plate thanks to Apple and NeXT before it using the frameworks for years.

Now, SwiftUI and Compose are effectively cousins, as are Kotlin and Swift. Both App Stores have their quirks. Publishing is part of both workflows. It's really not harder for one or the other, it's just administrivia.

replies(1): >>44073647 #
2. codingjerk ◴[23 May 25 15:17 UTC] No.44073647[source]▶
Thanks for sharing. I agree in general,

But for me language is not a problem at all. I mean that you have a lot of pre-requirements to start developing for iOS.

And the stuff, except writing code feels much more restricted. AppStore is a walled garden itself.

But yeah, Objective-C was something...

replies(1): >>44082654 #
3. eddieroger ◴[24 May 25 17:47 UTC] No.44082654[source]▶
What prerequisites are you thinking of? Nowadays, all you need is a Mac, download Xcode, and go. You can't do /everything/ if that's as far as you go, but if all you wanted to do was flesh out an idea, that would get you started. And how's that's any different than getting a computer, installing Android Simulator, and starting a new project?