r/iOSProgramming • • Nov 27 '24

Discussion The Developer app is my new Netflix! 😍 As a former JavaScript developer, I just love Swift, SwiftUI, and the myriad of cool Apple frameworks! I'm binge-watching WWDC videos on this app whenever I have free time! ❤️

Post image
193 Upvotes

r/iOSProgramming • • Jul 26 '24

Humor Dodged a bullet today

Post image
193 Upvotes

r/iOSProgramming • • Jun 13 '24

News Xcode 16 now has a built-in formatter

193 Upvotes

This function's powered by swift-format


r/iOSProgramming • • Feb 15 '24

News [9to5mac] Apple to launch new AI coding and testing features in Xcode this year

Thumbnail
9to5mac.com
193 Upvotes

r/iOSProgramming • • May 06 '21

Application Made a Credit Card Reader in native Apple Vision/VisionKit!

193 Upvotes

r/iOSProgramming • • Dec 23 '19

News The App Store will no longer accept new apps using UIWebView as of April 2020 and app updates using UIWebView as of December 2020.

Thumbnail
developer.apple.com
193 Upvotes

r/iOSProgramming • • Jun 05 '26

Discussion i miss the "programming" aspect of ios programming.

192 Upvotes

remember when ios APIs and frameworks were still very new and exciting?

there was an actual art form in seeing how much of the new hardware/new OS capability you can use elegantly.

now most of this sub is AI posting, self promotion, and app marketing questions.

everyone seems to want "people who'll download and pay for my app" but nobody seems to want to "be the reason i have people who know me and download+pay for my app"?

vent over.


r/iOSProgramming • • Feb 23 '21

Application I've tried to clone Instagram Reels using Swift UIKit! what do you guys think? let me know in the comments.

192 Upvotes

r/iOSProgramming • • Aug 13 '20

News Epic Games is suing Apple

Thumbnail
theverge.com
192 Upvotes

r/iOSProgramming • • Sep 07 '25

Humor Xcode helped me turn into the Jacked Michelin Man. Thanks Xcode.

Post image
191 Upvotes

r/iOSProgramming • • Aug 15 '25

Discussion Our almost-two-year journey building for iOS | 55k+ downloads, 0 paid ads

Post image
191 Upvotes

Hey folks! Inspired by the story shared by another person here about their journey building 3 apps in 2 years and what they learned, I thought this would be a great time to talk about what WE learned so it can help people along the way.

Almost two years ago, a few friends and I started building an iOS-only, handwriting-based social app for sending letters, collecting digital stamps and meeting & making PenPals around the world. We wanted to make something that felt warm, human and slow in a good way. No ads, no data mining, no gamified dopamine loops: just thoughtful communication.

We launched on the App Store with no marketing budget and absolutely no idea how it would be received. Everything since has been organic: App Store Search accounts for over 91% of our downloads.

As of this week:

  • 395K+ App Store impressions (+774% growth recently)

  • 87K+ product page views (+249%)

  • 56.2K total downloads in under 2 years

  • Top countries: US, UK, Germany, India, Canada

  • Proceeds per paying user: $4.94 weekly average

  • I didn't share our total Proceeds due to superstitious reasons (yes, i am a little-stitious)

Some takeaways from the journey so far (including but not limited to):

  • Good ASO matters -> most of our growth came from optimizing keywords, description, and screenshots. We experimented with appstore ads but figured we didn't have enough budget to get good results. DO NOT run ads if you cannot afford to outbid everyone for your keywords.

  • Niche + personality beats broad + generic -> our “digital penpal” angle resonated more than generic “messaging app” language. A LOT of people love us just because of our novelty and the fact that we are free with no ads. (I wish we could get better at communicating)

  • Retention is everything -> big download spikes mean little if you can’t keep people engaged. We proudly boast close to 80% retention within a 6-month window

  • Small, frequent updates > big releases -> shipping fixes/features every couple of weeks keeps reviews positive and crashes low. Ship fast, ship often. Nothing beats actually shipping your work.

We’re still tiny (a couple of us code from our kitchen tables) and we’re learning as we go, but seeing people form real friendships through something we built has been worth every late night. It’s been surreal watching this grow from a scrappy side project into a global little community. The most rewarding part? Hearing stories from people who’ve made real friends, reconnected with family, or just rediscovered the joy of putting pen to (digital) paper.

If anyone’s curious about indie iOS growth, ASO experiments, or monetization without ads, happy to answer questions.

Cheers,


r/iOSProgramming • • Jan 31 '23

Humor I am an iOS dev with 10y of experience

191 Upvotes

Today, on an interview, I have been asked if I know what Xcode is.


r/iOSProgramming • • Jan 29 '23

Application I call this one a Snake pagination. A fun little project I made this weekend with SwiftUI. What do you guys think about it?

191 Upvotes

r/iOSProgramming • • Oct 08 '21

Roast my code I ported SM64 to iOS but still have some questions to make it better

191 Upvotes

r/iOSProgramming • • Aug 03 '25

Article SwiftUI in Production: What Actually Worked (and What Frustrated Me) After 9 Months

Post image
190 Upvotes

TL;DR: Shipped a SwiftUI app after 9 months. SwiftUI is amazing for iteration speed and simplicity, but watch out for state management complexity and missing UIKit features. Start small, profile often, and keep views tiny.

Hey folks, I just shipped an app which I built over 8-9 months of work, going from being seasoned in UIKit, to attempting SwiftUI. This is about 95% SwiftUI, and on the way I feel I learnt enough to be able to share some of my experiences here. Hence, here are learnings, challenges and tips for anyone wanting to make a relatively larger SwiftUI app.

🟢 The Good

1. Iteration speed is unmatched

In UIKit, I'd mostly wireframe → design → build. In SwiftUI, however, with Claude Code / Cursor, I do iterate many a times on the fly directly. What took hours in UIKit, takes minutes in SwiftUI.

// Before: 50+ lines of UITableView setup
// Now: Just this
List(entries) { entry in
    JournalCardView(entry: entry)
}

2. Delegate pattern is (mostly) dead

No more protocol conformance hell. Everything is reactive with u/Published, u/State, and async/await. My codebase went from 10+ delegate protocols to zero. Nothing wrong in the earlier bits, but I just felt it's much lesser code and easier to maintain.

3. SwiftData + iCloud = Magic

Enabling cloud sync went from a weekend project to literally:

.modelContainer(for: [Journal.self, Tag.self],
                inMemory: false,
                isAutosaveEnabled: true,
                isUndoEnabled: true)

4. Component reusability is trivial

Created a PillKit component library in one app. Now I just tell Claude Code "copy PillKit from app X to app Y" and it's done. It's just easier I feel in SwiftUI, UIKit I had to be very intentional.

// One reusable component, infinite uses
PillBarView(pills: tags, selectedPills: selected)
    .pillStyle(.compact)
    .pillAnimation(.bouncy)

5. iOS 17 fixed most memory leaks

iOS 16 SwiftUI was leaking memory like a sieve. iOS 17? Same code, zero leaks. Apple quietly fixed those issues. But I ended up wasting a lot of time on fixing them!

6. Preview-driven development

Ignored previews in UIKit. In SwiftUI, they're essential. Multiple device previews = catching edge cases before runtime.

7. No more Auto Layout

I've played with AutoLayout for years, made my own libraries on it, but I never really enjoyed writing them. Felt like I could use my time better at other areas in code/design/product. SwiftUI, does save me from all of that, changing/iterating on UI is super fast and easy, and honestly it's such a joy.

// SwifUI
HStack {
    Text("Label")
    Spacer()
    Image(systemName: "chevron.right")
}

// vs 20 lines of NSLayoutConstraint

All in all, I felt SwiftUI is much much faster, easier, flexible, it's easier to write re-usable and reactive code.

🔴 The Struggles:

1. Easy to land up with unexpected UI behaviour:

Using .animation instead of withAnimation can end up in animation bugs, as the former applies modifier to the tree vs the latter animates the explicit property we mention inside.

// 💥 Sheet animation leaks to counter
Text("\(counter)")
    .sheet(isPresented: $showSheet) { SheetView() }
    .animation(.spring(), value: showSheet)
    .onTapGesture { counter += 1 }  // Animates!


// ✅ Isolate animations
Text("\(counter)")
    .sheet(isPresented: $showSheet) { SheetView() }
    .onTapGesture { 
        counter += 1
        withAnimation(.spring()) { showSheet = true }
    }

2. Be super careful about State Management:

Published, State, StateObject, Observable, ObservableObject, u/EnvironmentObject. It's very easy for large portions of your app to re-render with super small changes, if you aren't careful on handling state. I would also recommend using the new u/Observable macro, as it ensures only the parts of view using the property are updated.

Pro tip: Use this debug modifier religiously:

extension View {
    func debugBorder(_ color: Color = randomColorProvider(), width: CGFloat = 1) -> some View {
        self.overlay(RoundedRectangle(cornerRadius: 1).stroke(color, lineWidth: width))
    }
}

func randomColorProvider() -> Color {
    let colors = [Color.red, Color.yellow, Color.blue, Color.orange, Color.green, Color.brown]
    let random = Int.random(in: 0..<6)
    return colors[random]
}

3. Compiler errors are often un-informative:

"The compiler is unable to type-check this expression in reasonable time"

Translation: We don't know why it does not compile, try commenting out last 200 lines to find a small comma related issue.

4. Debugging async code is painful

SwiftUI is async by default, but the debugger isn't. Lost call stacks, breakpoints that never hit, and

u/MainActor confusion everywhere.

5. API churn is real:

  • iOS 15: NavigationView

  • iOS 16: NavigationStack (NavigationView deprecated)

  • iOS 17: Observable macro (bye bye ObservableObject)

6. Some things just din't exist:

Need UIScrollView.contentOffset? Here's a 3rd party library. Want keyboard avoidance that actually works? Introspect to the rescue.

UITextView with attributed text selection? UIViewRepresentable wrapper. UICollectionView compositional layouts? Back to UIKit.

Pull-to-refresh with custom loading? Roll your own. UISearchController with scope buttons? Good luck.

First responder control? @FocusState is limited. UIPageViewController with custom transitions? Not happening.

The pattern: If you need precise control, you're bridging to UIKit.

7. Complex gestures = UIKit

My journal view with custom text editing, media embedding, and gesture handling? It's UITextView wrapped in UIViewRepresentable wrapped in SwiftUI. Three layers of abstraction for one feature.

💡 Hard-Won Tips

1. State management architecture FIRST

Don't wing it. Have a plan before hand, this will really come in handy as the app starts bloating

  • u/Environment injection (my preference)

  • MVVM with ViewModels

  • TCA (I find the complexity a bit too much, it's like learning SwiftUI + another SDK.)

  • Stick to ONE pattern

2. Keep views TINY

// BAD: 200-line body property
// GOOD:
var body: some View {
    VStack {
        HeaderSection()
        ContentSection()
        FooterSection()
    }
}

3. Enums for state machines

enum ViewState {
    case loading
    case loaded([Item])
    case error(Error)
    case empty
}

// One source of truth, predictable UI
 private var state: ViewState = .loading

4. Debug utilities are essential

extension View {
    func debugBorder(_ color: Color = .red) -> some View {
        #if DEBUG
        self.border(color, width: 1)
        #else
        self
        #endif
    }
}

5. Profile early and often

  • Instruments is your friend

  • Watch for body calls (should be minimal)

  • _printChanges() to debug re-renders

6. Start small

Build 2-3 small apps with SwiftUI first. Hit the walls in a controlled environment, not in production.

🎯 The Verdict

I will choose SwiftUI hands down for all iOS work going forward, unless I find a feature I am unable to build in it. At that place I will choose UIKit and when I do not have to support iOS 15 or below. For larger applications, I will be very very careful, or architecting state, as this is a make or break.

------------------

For those curios about the app: Cherish Journal. Took me an embarrassingly long time to build as an indie hacker, and it's still needs much love. But happy I shipped it :)


r/iOSProgramming • • Feb 27 '25

Discussion Before & after a much needed redesign (finally paid a UX designer)

Post image
190 Upvotes

r/iOSProgramming • • Jun 22 '20

News Good news everyone! No more UIApplicationDelegate

Post image
190 Upvotes

r/iOSProgramming • • Nov 30 '25

Discussion No one wants to admit that Xcode has been a buggy pile of steaming shit for years now, and we'd all switch to a VS Code IDE full time if we could

189 Upvotes

Intellisense covers the code you're writing, the static analyzer reports errors that aren't actually errors, the visual debugger still can't serialize swift objects to show you anything helpful, SwiftUI previews crash on any moderately complex views, etc. etc.

I've been building iOS apps full time since 2010, and Xcode was solid back in the Objective-C days. It's been on a downward trajectory since the very first Swift release, and it took a real nosedive when SwiftUI was released. It's been 11 years since Swift was released, and six years for SwiftUI, and Xcode gets worse every year, and I hate that I have to use it at least some of the time.


r/iOSProgramming • • Dec 29 '24

Discussion Started a Youtube channel to review apps from Indie IOS Developers.

189 Upvotes

I’ve always wanted to create a channel to review apps, but I’ve always been scared to. My constant fears have been: what if this flops like everything else? What if nobody watches the videos? What if nobody subscribes to my channel? These fears have held me back for a long time, but I’ve decided not to let them stop me anymore. I’ve gone ahead and created a channel, and I’m making this post to hold myself accountable.

I’ll post one review every week starting the first week of January (or more frequently if people are interested in the reviews). The videos will share my complete, unbiased personal opinion from a user’s point of view while using your app. I’ll provide feedback—whether good or bad—and mention areas for improvement.

Right now, I don’t have any videos posted (mainly because I created the channel just last night), but I’ll have one up in a few days (working on it!). I’ll almost exclusively feature and review apps from this subreddit. :)

If you’d like to support me, please subscribe—20 subscribers would make my whole year . https://www.youtube.com/@letsreviewthatapp

EDIT:

First Video is Published : https://youtu.be/BgwU2gtJVL4


r/iOSProgramming • • Sep 29 '22

Application iOS 16 introduced the Live Text API, so I made an app to quickly markup text within your images.

189 Upvotes

Instead of scribbling over image text, my app lets you use Live Text selection to quickly/cleanly white out or highlight images.

Live Text is the same feature used in the native photos app, but now its available to developers in ios 16.

Is anyone else incorporating Live Text into one of their apps? It hasn’t gotten a lot of attention since most devs are focused on the island, or lock screen widgets.


r/iOSProgramming • • Jun 07 '21

Application I've been exploring SwiftUI Complex layouts 😅 what do you think of this? let me know!

189 Upvotes

r/iOSProgramming • • Jun 23 '19

SwiftUI vs UIKit – Comparison of building the same app in each framework

Thumbnail
youtube.com
189 Upvotes

r/iOSProgramming • • Feb 07 '26

Discussion The secret to buttery smooth SwiftUI

188 Upvotes

This morning at 1 am (always when you say “this is the last post I read then I go to sleep) I found one of the best resources about SwiftUI in a while:

An article explaining how SwiftUI rendering works

https://www.swiftdifferently.com/blog/swiftui/swiftui-performance-article

The agent skill created with the article’s knowledge in mind:

https://skills.sh/avdlee/swiftui-agent-skill/swiftui-expert-skill

Hope you find it useful


r/iOSProgramming • • Nov 01 '25

Discussion Got this one star review and it perfectly sums up how confusing Apple’s subscription system can be

Post image
188 Upvotes

hi all,

I got this review on my app recently

The user says they can’t cancel their subscription through the app and will only change their review if someone shows them how.

I replied and explained that Apple handles all iOS subscriptions in Settings, not inside individual apps.

It made me wonder how other devs handle this. Do you include a little “how to cancel” section or just link to Apple’s help page?

It feels like this confusion happens a lot and we end up taking the blame for something completely outside our control.