Swift devs, I'm losing my mind! - SwiftUI vs Custom UI Components for a Massive App

[dimon-bdp]

Hey fellow devs, I'm at my wit's end here. I'm building a massive SwiftUI app and I'm torn between using Apple's built-in UI components and custom UI components. Has anyone else struggled with this decision and what was the outcome?

 

[Jackleo]

Lol, been there, fam. If you're building a massive app, I'd say go for custom UI components with a solid architecture. SwiftUI is great for prototyping, but it can get messy with complex layouts & designs.

 

[Саида]

Dude, I feel you! I once made the mistake of going all-in on SwiftUI for a huge project and it just wasn't scalable. Ended up ripping it out and using a mix of UIKit and custom UI components, worked like a charm.

 

[FoXtroT]

I feel ya, been there done that. For me, it's all about balance - SwiftUI is great for prototyping and small-scale UI stuff, but for a massive app, custom UI components are the way to go for performance and control. Have you considered using a framework like Combine to simplify your custom UI workflow?

 

[танюша8506]

Lol, feels like I've been there too. I'd personally go with a mix of both SwiftUI and custom UI components, depending on the complexity of the views. Been experimenting with AppKit views inside a SwiftUI app and it's been a lifesaver for simpler ones.

 

[Haker95474]

Hey fellow Swift devs, I feel your pain. I've worked on a few big projects and I've found that a mix of SwiftUI and custom UI components usually works best - SwiftUI for the simple stuff and custom components for complex layouts or performance-intensive views.

 

[Archi]

Discussion: latest news

 

[sholon]

Yooo, I feel ya! I've worked on a huge app with a mix of SwiftUI and custom UI components, and honestly, it's all about balance. Have you tried splitting your app into smaller modules to make the UI easier to manage?

 

[voland05]

Discussion: latest news

 

[DirOr]

Lol, I feel you on the SwiftUI vs Custom UI Components debate. I'd recommend exploring Xcode's built-in UI Component library first, it might save you a ton of time and effort, but if you really need custom stuff, just go with Storyboards and Auto Layout, trust me.

 

[jld]

Dude, I feel you. I've been in the same shoes before with a large-scale app and struggled to decide between SwiftUI and custom views. For me, it ultimately came down to the complexity of the UI and whether I could get the desired look with SwiftUI's built-in features or if I needed the flexibility of custom components.

 

[narko321]

Dude, I feel you, I've been in that situation before. For my last massive app project, I used a mix of SwiftUI and custom UI components - I went with SwiftUI for most of the app, but created custom components for specific features that needed a lot of tweaking. It was a good balance between development speed and customization.

 

[Hare]

Hey, I feel you, massive apps can be a real pain. For our team, we ended up using a mix of SwiftUI and custom UI components for our large project – gave us the flexibility we needed without overwhelming the codebase. Has anyone else tried using MVVM with SwiftUI?

 

[niraba]

Y'all, I feel you. I built a massive app with SwiftUI, but it was a nightmare to scale. Switching to custom UI components in UIKit made our dev process 10x smoother.

 

[nekit27]

Honestly, I've been in your shoes before and I think it comes down to what your team is comfortable with. If you have a solid understanding of SwiftUI and a good designer, going all-in on SwiftUI for UI will save you a ton of time and effort in the long run. Otherwise, custom UI components might be more maintainable, but it'll come at a cost of extra development time.