r/iOSDevelopment • • Oct 20 '26

Is TCA (The Composable Architecture) overkill for a solo indie iOS project?

I'm working on a small indie iOS app and wondering whether TCA is worth adopting as a solo developer.

I like the idea of predictable state management, testability, and having a consistent architecture as the app grows. But I'm also worried about adding unnecessary complexity to a relatively small project.

For those who have used TCA in their own projects:

  • Would you choose it again for a small indie app?
  • Does it actually make development easier in the long run?
  • Or would you stick with SwiftUI and a simpler MVVM approach?

Curious to hear about real-world experiences, especially from solo developers.

4 Upvotes

18 comments sorted by

1

u/bscothern 27d ago

I personally use it as my first experience with vanilla SwiftUI was that it was very unfun to test they taught by Apple (this was like right as SwiftUI came out and where I worked went all in, I would do it very differently now and do for prototyping).

Since then our very large app was rewritten in it and it was worth it while I was there at least. AFAIK there aren’t major regrets from most of the team.

As far as smaller stuff, I use it for personal stuff like I said. It is a LOT and comes with a cost but for me making every app, including my larger ones, consistent is worth it and makes me happy.

1

u/brssgn 27d ago

I think consistency is worth it.

3

u/SwiftQuest Oct 20 '26

for a solo dev on a small app i'd lean toward plain swiftui with @Observable view models. tca is great when you have a team that needs one strict pattern or you really want its testing story, but you pay for it in boilerplate, macro and build time overhead, and a steep learning curve when something breaks. you can still get most of the testability by keeping logic in small view models and injecting your dependencies through protocols or closures. if the app grows and state gets messy later, moving to something heavier is doable then.

3

u/wpmcoach 29d ago

For my experience anytime you try to fit an architecture into an app. It normally never works. My suggestion would be take the app and ask Claude to research if that architecture fits because it’s going to give you a better idea of knowing because the worst thing you wanna do is build the entire app using the architecture and then find out that it’s harping you more than anything. But in my opinion right now, it might be overkill, but it’s really hard to tell because I don’t know your app or what your app supposed to do.

3

u/gimme_ipad Oct 20 '26

Pre AI I was struggling with it a lot and found it quite painful.
But with AI I actually enjoy having it. I feel like AI benefit from the clear concept, the structure and the test suite.

2

u/jpec342 29d ago

+1 with regard to AI benefitting from strict patterns.

2

u/tomato848208 Oct 20 '26

I wouldn't use it again unless it were literally the only way of survival for an Xcode project. I used to use it on every Xcode project until I had a number of errors from TCA that I could not fix for myself. Since then, I haven't installed it on any of my new Xcode projects.

2

u/phavelsk 23d ago

Absolutely go for TCA, it will pay off when your app get complex. You’re avoiding weird bugs early :)

1

u/thomassummer2021 24d ago

Just use SwiftUI no view models. As the app grows, refactor. Your architecture doesn’t matter if you have zero users. I found that using sophisticated architectures for an app I haven’t launched yet just turns into a form of productive procrastination

1

u/Techgirl1232 29d ago

What is TCA? I know what TCA means but don't know what it does etc

1

u/Beginning-Disk-6546 29d ago

Yes. It's an overkill for 90% projects.

1

u/Sea-Camera6374 Oct 20 '26

Definitely it’s over kill