This extension is for "pure" Swift development, not iOS development. I doubt the latter will ever officially happen. It's possible to make it work for iOS at an unofficial capacity though by hooking into the extension's LSP support. We did this at Spotify to enable iOS development in Cursor for Bazel iOS projects: https://github.com/spotify/sourcekit-bazel-bsp

▲

worldsavior 6 hours ago | parent | next [-]

You also can't do Android (app) development outside Android Studio.

▲

c0balt an hour ago | parent | next [-]

Are you sure about that? Flutter development for Android works great in VS Code/Codium. The Android extension [0] for VS Code has also worked fine in the past on a small Java-based App for me.

Android Studio is a probably the best IDE for this usecase but is not the only way.

[0]: https://marketplace.visualstudio.com/items?itemName=adelphes...

▲

Antonito 4 hours ago | parent | prev | next [-]

As others have stated it's possible, but might be cumbersome.

I made an example of an iOS/Android monorepo with a shared Rust core a few months ago: https://github.com/Antonito/bazel-app-core-native-example/

You do need the Android SDK to build, Android Studio makes things easier (even though the Bazel IDE plugin is a whole other topic itself..) but isn't mandatory to develop or run your app.

▲

tadfisher 5 hours ago | parent | prev | next [-]

That's just untrue on the face of it. All of the build tools are open and cross-platform. Is there a specific piece of Android Studio that you require for Android app development?

▲

manwe150 5 hours ago | parent [-]

Not certain if this answers the question, but it seemed like you're generally expected to install Android Studio to get the correct build versions of all of the tools and libraries. I guess theoretically you could repackage them yourself, but also not entirely clear why you would—other than perhaps download size. The tools can be driven externally, once installed, but so could XCode projects (with `xcodebuild`).

	▲	tadfisher 5 hours ago \| parent \| next [-]
		This is not an expectation, no. Libraries are managed via Gradle or whatever build system you use. Android-specific host tools are Gradle-managed, installed via the sdkmanager tool, or managed via other means; I maintain a repository to install them via Nix [0], and many Linux distributions package them. The Android Studio IDE is not required, and doing so would pretty much break everyone's CI setup. [0]: https://github.com/tadfisher/android-nixpkgs
	▲	daveoc64 4 hours ago \| parent \| prev [-]
		They've always offered a bundle of the command line tools separately to Android Studio: https://developer.android.com/studio#command-line-tools-only

▲

cyberax 5 hours ago | parent | prev [-]

Incorrect. You can (if you really want to) build an Android app without having any Google tools.

But even if you don't want to do any crazy stuff, Android SDK itself is just a bunch of Gradle scripts and Java apps. You can download and install them without any GUI in the way.

This is very common in CI/CD environments. Google provides a handy tool for that: https://developer.android.com/tools

Sorry, but Android and iOS are simply incomparable in their quality. Android SDK is a high-quality tool for developers that provides all the expected interfaces.

iOS SDK is a lock-in GUI hell that requires you to use a shitty macOS-only tool to even _upload_ apps to Apple Store. Never mind doing headless builds in CI/CD. Why that tool is shitty? It uses its own protocol for upload and doesn't do proper PMTU, so if you have a misconfigured MTU somewhere in the chain between you and Apple, uploads will just silently hang.

Edit: D'Oh, the correct URL for the sdkmanager is: https://developer.android.com/tools/sdkmanager

	▲	manwe150 5 hours ago \| parent \| next [-]
		Just to nit pick a bit, that link is for Android Studio and downloads from the "Google for Developers" website, then instructs how to install and manage the the command line tools using the GUI
	▲	thejazzman an hour ago \| parent \| prev [-]
		Not trying to argue but you can indeed pretty much completely avoid Xcode at this point. I’ve been doing it the past few weeks, including pushing to my phone and AppStore connect

▲

QQ00 4 hours ago | parent | prev [-]

What's the point then? Because nobody use Swift outside of iOS app development.

	▲	girvo 4 hours ago \| parent [-]
		> Because nobody use Swift outside of iOS app development Because that isn't true, people do use it outside of iOS app dev, and is becoming more true as time goes on to boot. It's also a chicken-and-egg problem: no one will use Swift for non-iOS tasks if the tooling support isn't there. The more investment into it, the more it will be picked up for other tasks. But it's been used outside of Apple-specific things since the early days in various niches.