As someone who was using AppCode to build multipla...

# multiplatform

[saket]

As someone who was using AppCode to build multiplatform macOS projects, I'm very sad that I'll have to go back to Xcode 😔.

https://blog.jetbrains.com/appcode/2022/12/appcode-2022-3-release-and-end-of-sales-and-support/

[itnoles]

AppCode doesn't work with SwiftUI?

[saket]

It does, except for layout previews

[curioustechizen]

For me the real productivity killer will be context switching between keyboard shortcuts for AS and XCode 😞

[Mustafa Ozhan]

I think instead of seperate product would be much better to add the functionalities in AppCode into IntelliJ and Android Studio with plugin

[Fred Bowker]

This is terrible if you develop cross platform or full stack, at the moment I can develop a feature for android and IOS using the same IDE’s same key bindings etc, having to go back to XCode is a total pain. Would be really great if JetBrains could make AppCode a plugin for IntelliJ

[Fred Bowker]

It seems a solution of AppCode AndroidStudio and KMM would have been a great solution for mobile dev

[czuckie]

will there be a memorial service? I remember extracting functions and renaming symbols in objective-C using appcode. It brought tears to my eyes how well it worked, even on one crazy rats nest of a codebase.

Goodnight sweet prince 😞

[Marko Novakovic]

I will hate to go back to working in xcode. I love to have similar dev experience for Android and iOS development (Jetbrains IDEs are simple the best). it is what it is. thank you for the great product

[Fred Bowker]

I kind of feel like without AppCode jetbrains is missing part of the KMM puzzle and IOS dev will become a second class citizen in the KMM Mobile development solution. If IOS devs used AppCode and Android devs used AndroidStudio then it makes it far easier for them to jump into each others code basis. But that is more a vision of how I want things to work, in reality I suspect there just wasn’t enough AppCode paid subscribers

[Jeff Lockhart]

Cmd+click navigating code to implementations/callers works 1000x better in AppCode. Xcode almost never works, either failing to navigate anywhere or worse, taking you to a completely incorrect location, wasting time just figuring out the only thing the code has in common with what you're in fact looking for is possibly the function's name. I will miss AppCode dearly.

[darkmoon_uk]

https://kotlinlang.slack.com/archives/C9JM6Q2UX/p1671176985335459?thread_ts=1670610941.766059&cid=C9JM6Q2UX

[humblehacker]

@darkmoon_uk That's a very interesting take, and if true is good news as JetBrains dropping AppCode support along with planned Swift support being removed from their roadmap had me questioning the long term viability of KMM and reconsidering our recent decision to adopt it.

I've been using AppCode since the very first release. I'm very sorry to see it go.

[itnoles]

Was Apple is planning to convert Foundation to Swift?

[saket]

yep some context here: https://kotlinlang.slack.com/archives/C9JM6Q2UX/p1670610941766059

[itnoles]

https://forums.swift.org/t/what-s-next-for-foundation/61939/31 This can be a huge breaking change if they can break backward compatibility.

[darkmoon_uk]

...maybe they won't break backward compatbility, but maybe they will. Either way, being Apple they surely won't give clues to JetBrains or anyone else about their specific intentions. Perhaps this caused JB to immediately divert their best Swift experts - surely the AppCode team - to start working on Swift interop to try and mitigate the risk.