AppCode 2016.2 roadmap & thanks to our EAP users

Hi everyone,

Two weeks ago we published AppCode 2016.1 and now it’s time to reveal our plans for the next release.

Special thanks

We’d like to thank everyone who evaluated AppCode during the Early Access Program and shared their feedback and suggestions in our Twitter, blog and support channel, and especially to those who submitted issues or feature requests to our tracker. Several evaluators deserve special gifts for their contributions: free 1-year subscriptions. So here they are:

  • Mark Anders (YouTrack: markand)
  • Ian Bytchek (YouTrack: ianbytchek)
  • Benjamin Winterberg (YouTrack: Benjamin.Winterberg)
  • Jon Akhtar (YouTrack: sylvanaar)

A personal message will be sent to each one with the details on how to obtain the license. (If you see your name above and you don’t get an email from us within a week, ping us here in the comments.)

Roadmap

The main directions of development will remain the same as for AppCode 2016.1, with a few additions:

  • Swift
    • Syntax inspections (OC-13024)
    • Swift 2.2 support in parser (OC-13365 and subtasks)
    • New refactorings for Swift (Inline variable (OC-11356) and Introduce variable (OC-11591) first)
    • Related editor performance issues
  • Mixed Objective-C and Swift code:
    • Resolve issues
    • Improvements for Rename refactoring and Find Usages
  • Objective-C: fixes for generics

The current plan is to deliver Swift 2.2 and part of the mixed code improvements in updates for 2016.1. All other improvements are scheduled for 2016.2 EAP, which we plan to open around mid-May.

Stay tuned and don’t to miss the next EAP launch!

Your AppCode team
JetBrains
The Drive to Develop

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

3 Responses to AppCode 2016.2 roadmap & thanks to our EAP users

  1. Randy Tamura says:

    Do you have a plan/date for Swift 3 support?

    • Stanislav Dombrovsky says:

      According to official blog post from Apple, Swift 3.0 is expected to be released sometime in late 2016. Our date is the same here )

      To makes things clear:

      1. From our testing there are no problems with running/debugging apps when using current Xcode 8 beta with AppCode.

      2. There are some issues with SourceKit integration we’ll need to handle (there is a blinking dialog shown while running the SourceKit inspections with Xcode 8, but they still work)

      3. As now AppCode uses SourceKit bundled to Xcode selected in AppCode settings for running on-the-fly analysis for Swift files and displaying warnings/errors in editor for Swift, in terms of using fix-its for migration from one Swift version to another, warning and error messages you will have mostly the same experience. You will be able to see problems in your code and fix it in the same way as in Xcode.

      4. There can be issues related to parsing/resolve related to the changes in Swift 3.0, currently we are investigating where they can appear. We’ll consider needed changes after the current release and publish the information about them in the roadmap for the next release. Current understanding is that there should not be a lot of significant problems in general IDE experience with Swift.

  2. Lee Laborczfalvi says:

    One of the things that Apple has stated for XCode 8 is improved performance. On large projects AppCode build times are really slow when compared to xcode. Will performance improvements that are made in XCode 8 also lead to performance optimizations in AppCode?

Leave a Reply

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