We're Joining OpenAI

If your iOS project has more than 700 files... you might be doing it wrong?

Bear in mind 600 of those files are icon and screenshot variants for various screen dpis and spec ratios..

In your mind is 700 files a lot or a little? It feels very small to me, and Xcode really ought to be able to handle that tiny scale on modern machines with ease.

I struggle to imagine a team of more than 10 people writing an iOS app with less than 700 files.

Instagram.app likely has 30,000 files for iOS. And it produces 10-figures of revenue. So how is that wrong?

I mean.. say its an enterprise mobile app. Maybe there are 2 shells, each shell has 5 tabs. Each tab might have 5 screens on it.. that's 50 files already just for the screens. Each screen might have various UI components or steppers, etc.

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.

In fairness, as a mere generator of eyeball time that gets mis-sold* to advertisers, I'd say the FB user experience is very much "doing something wrong".

* 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

Translation files, themes, drawables .etc...the list is endless. Even a simple app will easily have a thousand files.