Delete and remove if completely inappropriate and off basis, but seeing as swift on android is now official and spm is going open source, would tuist theoretically if work was done, be able to be used to generate both ios xcode and android projects using tuist? Using spm to structure swift packages used for shared logic between both platforms? E.g on ios build and compile with xyz and for android use android toolchain and sdk to compile abc
It’s been a while 
. Tuist builds on Xcode projects, so we are reliant on them supporting additional build systems. With the unification of build systems and graphs via swift-build we are one step closer to see that happening, at which point I wonder if we can add any value upon SwiftPM’s support. What features of Tuist would you like to see working with Android?
When/if using shared swift logic between iOS and Android one has to compile swift code for android explicitly.
i use tuist and enjoy having everything project related in code (trying to build a fullstack workspace iOS/Android/Vapor) and just thought it would be sweet if one could compile all swift code for all three of those platforms from a single point.
I see what you mean now. We are not opposed to that, but I think it’s better to hold to see how Apple evolves Xcode projects and its build system.
Xcode projects can incorporate a node in the build graph that shells out to Gradle, makint it feel integrated into the rest of the project, but if problems arise, it’ll be a bit of a pain to diagnose why the Gradle build fails (compared to doing this in let’s say Android Studio). Will Apple make Gradle be a first-class citizen in the new build system swift-build. I hightly doubt, but who knows… the community seems to be active lately on bridging the Swift and Android gap.
i wasn’t really thinking that tuist would compile any android project or gradle hooks, more structure all the swift code using tuist and build each and any modules for all archs and then using android studio to compile the built modules into android
Oh I see what you mean.
Like I mentioned, Tuist integrates or abstracts, depending on the feature, Xcode, so they are the one defining and processing the build graph, which means we rely on them to add support for it. Have you considered using SwiftPM’s recent support for Android via a toolchain?