The interviewer asks about setting up a modular project with Tuist from scratch. Walk through the units and the layers you split the modules into.
Layer it App → Feature (per screen, with Interface and implementation separated) → Domain → Core (networking, storage) → Shared (design system, utilities), and allow dependencies downward only. Features depend on each other's Interface only, which stops cycles, and the App injects the implementations.
Build and distributionShort answerAdvanced
How do you set up a third-party library through SPM in a project that Tuist generates?
#tuist #project-generation
Build and distributionShort answerExpert
Over a hundred iOS engineers work on one app here. Hundreds of pull requests land a day…
#modularization
Build and distributionShort answerAdvanced
You inherit a project where a clean build takes 15 minutes and a one-line change still…
#modularization
Build and distributionShort answerExpert
A team on an app with more than a hundred modules is drowning in project.pbxproj…
#tuist