absolutely no. Alex is heavily optimized for xcode. If you work on an ios project that has more than 700 files, you'll understand how accurate it captures the context.
Is there a reason why the Claude cannot do the same thing?
So Claude could do it, it just seems like they're focusing on a different set of developers for the moment.
> There are huge issues in the Apple ecosystem with documentation and so much tribal knowledge.
I struggle to come up with an ecosystem where that doesn't apply. React, Angular, .NET, .... Though some of them probably even suffer from overdocumentation, e.g. React with the same beginner level tutorials / open source code regurgitating bad patterns, and you then have the challenge of separating the wheat from the chaff.
The question is really whether maintaining an ecosystem-specific model would be able outperform a better generalized coding model, and even further whether the marginal improvements would justify the additional maintenance process/cost.
I struggle to imagine a team of more than 10 people writing an iOS app with less than 700 files.
* dick pills and boob surgery, also government announcements for a country I don't live in, also offers to help renounce a citizenship I never had in the first place
Most noobs, such as those who think 700 files is too many because they've only worked on apps they never published, might just cram everything into that one file.
However, there would be various files for components, functions, etc. Code that's single responsibility and easy to test might mean there are lots of files. There might be upload queues, offline functionality, custom code to go beyond what the ios/android SDKs offer, and so on. DTOs, DAOs, etc. various services..
You probably (won't) get the gist but yeah.