iOS indie app development looks like

Post by wahnfrieden » Thu, Feb 13, 2025, 10:32 PM UTC

talldayo wrote: post #78

ToucanLoucan wrote: post #77

Earlier quoted context omitted.

The iOS/MacOS ecosystem is changing all the time, a decent amount of that time, they're good changes to be making. Sometimes they're arbitrary. Sometimes they're stupid. Either way, you know all of this before you publish anything there, so complaining after the fact that Apple is not sufficiently incentivizing you to maintain your code that runs on and is distributed by their operating systems is bizarre to me. Yes,…

> complaining after the fact that Apple is not sufficiently incentivizing you to maintain your code that runs on and is distributed by their operating systems is bizarre to me. Let me tie things up a bit for you then. To repeat myself; I'm not complaining! I don't pay Apple a dime anymore, not for services nor hardware. I had a brief, happy stint as an iOS dev in my nascent, foolish years as a programmer and moved on…

Post by geoffpado » Fri, Feb 14, 2025, 3:26 AM UTC

emoII wrote: post #59

samtheprogram wrote: post #13

Earlier quoted context omitted.

People I know who are iOS developers say differently. The Swift language itself is bloated? Compared to what? Golang?

Something like go, yes. Imo there is benefit to only being able to do things one way, and in swift there are a lot of ways to do everything. A trivial example: why can you bind variables in pattern matches with both case let .some(x) and case .some(let x)?

Post by emoII » Sat, Feb 15, 2025, 8:32 AM UTC

geoffpado wrote: post #83

emoII wrote: post #59

Earlier quoted context omitted.

Something like go, yes. Imo there is benefit to only being able to do things one way, and in swift there are a lot of ways to do everything. A trivial example: why can you bind variables in pattern matches with both case let .some(x) and case .some(let x)?

Because the former works with all associated values in a case, whereas the latter does not. `case let .some(x, y, z)` vs `case .some(let x, let y, let z)`. And the latter exists because you may want some to be immutable and others to be mutable: `case .some(let x, var y, _)`.

Post by satanworker » Mon, Feb 17, 2025, 4:06 PM UTC

Post by satanworker » Mon, Feb 17, 2025, 4:11 PM UTC

999900000999 wrote: post #23

I gave up on mobile app dev years ago. To Apple, I'm not giving you $100 per year for four people to play my hobbyist games. Not to mention getting my account approved in the first place was such a horrible process. They can and will deny your app for random reasons. I don't know how any independent developer really wants to base their entire income around such madness . What they want is multi-billion companies publ…