AppCode 2020.2 Roadmap

Hi everyone!

It’s time for us to share our plans for AppCode 2020.2:

  • Add Xcode 12 and Swift 5.3 support.
  • Provide support for Xcode projects that use Swift Package Manager dependencies.
  • Enhance SourceKit-based completion.
  • Implement the Change Signature refactoring for Swift.
  • Improve caching speed and 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.

8 Responses to AppCode 2020.2 Roadmap

  1. Marcel Bradea says:

    Would you guys elaborating on ‘Enhance SourceKit-based completion’?

    We’ve noticed recently that completion is blockingly slow (ie: doesn’t work for usually long periods at a time) – to the point that we’re switching back to Xcode to see what comlpetion drop-down options exist on a regular basis.

    This is extremely unproductive and interruptive to development flow.

    Or would this more be part of the ‘Improve caching speed and eliminate as many freezes as possible.’ focus area?

    • Stanislav Dombrovsky says:

      Would you guys elaborating on ‘Enhance SourceKit-based completion’?

      That’s about using SourceKit during indexing and caching to provide completion – further improvements.

      We’ve noticed recently that completion is blockingly slow (ie: doesn’t work for usually long periods at a time) – to the point that we’re switching back to Xcode to see what comlpetion drop-down options exist on a regular basis.

      Would be great to have a CPU snapshot from 2020.1 to understand why the code completion is slow (if it’s not yet there in one of the tickets in our tracker).

  2. Jindrich says:

    Please, please, focus on speed. The indexing times are really bad, something like 20 minutes after opening project. Why is needed to reindex everything again and again? For example Apple frameworks or sources that I didn’t touched?

  3. Bruce says:

    I am disappointed that performance is not the first bullet point. 2020.1 has been awful:

    1) 200-400% CPU usage when indexing and it often takes a long time.

    2) Serious memory leaks. I have seen RAM use climb as high as 32GB.

    3) Code completion seems to stop working often. Doing a ‘Find Usage’ will often result in the dreaded ‘Resolving…’ dialog that never seems to finish.

    • Stanislav Dombrovsky says:

      Hi Bruce, we’ve received your support request and our engineers will try to help. We are really sorry that after all our work on performance you still have problems, though for 2020.1 we’ve heard more positive feedback about the performance compared to previous versions. Looks like we need to take a look at your project, because it’s really big and complex.

      In any case, please, note that the order in this blog post is not a priority – it’s just an order of tasks, where performance issues still have a higher priority compared to almost any bug fixes or features and the same priority as Xcode/Swift support.

Leave a Reply

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