AppCode 2020.1 Roadmap

Hi everyone,

It’s time to share our plans for AppCode 2020.1, which haven’t changed much since 2019.3. We will continue to focus primarily on enhancing performance and Swift support:

  • Swift 5.1 & 5.2
  • Performance:
    • Make code highlighting, completion, and navigation faster for mixed and pure Swift projects.
    • Improve caching speed, including the “Processing Swift Modules” and “Building Module Maps” cache phases.
    • Eliminate as many freezes as possible.

If you have any questions, please ask them in the comments below.

Your AppCode team
JetBrains
The Drive to Develop

This entry was posted in Announcement and tagged , , . Bookmark the permalink.

14 Responses to AppCode 2020.1 Roadmap

  1. AT says:

    This is great. 2019.3 is so much better than 2019.2, and I look forward to further performance enhancements. Yay!

    • Vyacheslav Karpukhin says:

      No, these two issues are not on our roadmap at the moment.

      • Juan says:

        It’s a pity to hear that, as it’s a pain in the ass to work with assets inside AppCode.

        Support for Swift Package Manager would be a great advance too.

        And what about support for frameworks like Vapor?

  2. PangMo5 says:

    I’m using it too well.
    Thank you.

  3. Ot says:

    Thank you for sharing the roadmap.

    I am looking forward to AppCode 2020.1.!

    Will AppCode 2020.1 support SPM?

    https://youtrack.jetbrains.com/issue/OC-19012

    • Vyacheslav Karpukhin says:

      We’re looking into SPM support, but it’s too early to tell, whether it’s going to be ready by 2020.1.

      • Joost says:

        I would love to see SPM support as soon as possible. Some of our internal frameworks are packaged as a Swift Package. It works really nice in Xcode 11, but unfortunately AppCode does not handle these projects very well. AppCode is great, but we have to shelve AppCode until SPM arrives.

        • Vyacheslav Karpukhin says:

          We’ll do our best to support SPM as soon as we can. In the meantime, you could try a workaround: generate Xcode project from SPM, and then add it as a subproject to your main project.

          • Ota says:

            Hey Vyacheslav,

            could you elabore a bit more on the details? E.g. how does one add “the genearted xcode project” as a subproject to the actuall project? Is that in AppCode or Xcode?

          • Vyacheslav Karpukhin says:

            You can just drag the generated .xcodeproj into your main project, or add it using “Add Files”.

            It’s easier to set this up in Xcode, and then AppCode will pick up the changes.

  4. Guilherme Endres says:

    I am very happy that there will be more focus on performance issues.
    2019 I was unable to use AppCode because of that. I hope 2020 is a bright year for AppCode.

  5. Bill says:

    I would love to see more refactorings.

  6. Mike Schnaser says:

    Great news. I still have to double-drive XCode and AppCode, looking forward to the day where XCode is a distant memory :)

Leave a Reply

Your email address will not be published. Required fields are marked *