AppCode 3.4 roadmap update

Hi everyone,

Two months ago we published AppCode 3.4 Roadmap and now it’s time to update it and make some corrections in the release schedule:

  • We plan to release AppCode 3.3.3 update at the beginning of February without significant additions to features and fixes that are already included in 3.3.x EAP builds. Approximately at the same time we will start the Early Access Program for AppCode 3.4.
  • ETA for AppCode 3.4 release is early Spring, as planned before.
  • Features that are currently not marked as “completed” here will be partially delivered in AppCode 3.4 release, while others will be included in 3.4.x updates. It means that some of the most complicated features (such as syntax inspections or refactorings) can appear only in 3.4.x updates, but we will try to deliver both of those in 3.4. The preliminary schedule for minor updates will be published after the release.
  • Currently we have the following features left in the roadmap that are planned for 3.4 and 3.4.x releases:
  • In addition to the features mentioned above we’ve decided to add the following items in our roadmap based on your reports and requests:
    • Fixes for bridging header problems (subtasks of OC-10438 and related issues) that currently affect different code constructions when using mixed code (Swift + Objective-C)
    • Fixes for issues with resolve that currently affect completion in Swift (for example, OC-11729 and related issues)
    • Fixes for Swift debugger

As usual, there can be some external factors that can change our plans (like any massive changes in new Xcode updates), but we’ll do our best to deliver most of the features mentioned here on time.

Stay tuned and don’t miss 3.4 EAP launch!

Your AppCode team
The Drive to Develop

Comments below can no longer be edited.

7 Responses to AppCode 3.4 roadmap update

  1. Avatar

    Dev says:

    January 22, 2016

    This one is such a small feature, but would make a huge difference for every user, saving them a lot of time. I would definitely prioritise this feature over pretty much any other in the app:

    This one is very irritating in day-to-day AppCode usage, too:

    As is this one:

    I know everyone’s got their pet bugs, but I hit each of those every single day, and I’m sure many others do too.

    • Stanislav Dombrovsky

      Stanislav Dombrovsky says:

      January 22, 2016

      Thanks for mentioning it, we understand the priority of this feature. As soon as we will have available resources – we will implement it.
      Regarding other issues – if it will be possible, we will try to include it into some of 3.4.x updates.

    • Avatar

      luke says:

      February 4, 2016

      yes this so much. also add automatically closure boiler plate generation. Im sick of typing { x in


  2. Avatar

    Tropper says:

    January 27, 2016

    Nice, I really excited for 3.4. 😀

  3. Avatar

    Fabian says:

    January 28, 2016

    Is there anything planned for integrating ObjC Generics better? Currently when generating code, the Generic markup is lost, which is quite a time killer.

    E.g. `newVar = [self someMethodReturningGenericArray]`
    Then “Introduce Variable” results in
    `NSArray *newVar = [self someMethodReturningGenericArray]`
    Missing the Generic information.

  4. Avatar

    Joel Dean says:

    February 24, 2016

    I am wondering if its just me or what. When I add third party libraries I am not getting any code completion for them? Is that already available?

    • Stanislav Dombrovsky

      Stanislav Dombrovsky says:

      February 24, 2016

      Could you please give some more details about it – which language do you use in your project (Objective-C, Swift, or both), which libraries are you trying to add, are you trying to add it manually or via CocoaPods?

Discover more