Getting Started Resources for Mac and iOS Developers

Are you just getting started with Mac or iOS development?  Maybe just trying to improve what you know?  Here is a great resource from Dave Mark.  Everything is covered including blogs, conferences, forums and official Apple documentation.

I went looking for a reasonably recently updated list of dev resources to link to from the article. Couldn’t find one I was happy with, then remembered that we included a pretty solid list at the end of the book Beginning iOS 6 Development. Since that list needed to be updated for the iOS 7 rev of the book, I thought, why not pop the list into a blog post. And here we are.

At its core, programming is about problem solving and figuring things out. It’s fun, and it’s rewarding. But, at times, you will run up against a puzzle that just seems insurmountable—a problem that appears to have no solution. In those situations, it’s good to have friends in high places. This post outlines some resources you can turn to when you’re in a bind.

So add Resources for Mac and iOS Developers… to you reference list and be sure to check out the post comments for some other great resources.

Dave also has a great list of developer tools as well, Dave’s List: Apple Dev Tools…


Palliative Symptoms Survey Hits the Apple App Store

I have been working diligently on a project for some time now and it’s finally available.  My company, Still River Software, received approval from Apple last week for Palliateive Symptoms Survey to help doctors and caregivers provide better and faster care to their patients.

Palliative Symptoms Survey is an application based on the Edmonton Symptom Assessment Survey (ESAS-r) which was developed to assist in the assessment of nine symptoms that are common in palliative care patients: pain, tiredness, drowsiness, nausea, lack of appetite, depression, anxiety, shortness of breath, and wellbeing There is also a blank scale for patient-specific symptoms.

The application is a native iPad application written in Objective-C with a back-end using Ruby on Rails.   Please read a little bit about the project on my company web site.

Is JetBrains appCode a Solution Looking for a Problem?


Sometimes when a company releases a new product I sit back and think if I would use it.  If not, I try to understand who the customer might be and the reasons they use it.  When I first saw the announcement for the new Objective-C IDE from JetBrains, appCode, I asked myself those questions.

As a user of Apple’s XCode IDE for writing Objective-C, I tried to imagine the reasons why I might use it and none came to mind.  I also tried to imagine who might use it and I couldn’t think of anyone.  OK, maybe there are folks out there who use XCode and hate it, they may use it but I think the market is far too small to consider putting efforts into writing an IDE to target those people.

InfoQ has an interview with Maxim Shafirov of JetBrains about the project and after reading the article, I am still scratching my head.  From the article, appCode features include:

Main features of the IDE are:

  • Smart editor with code completion
  • Opening and creating Xcode projects (including Xcode 4)
  • Integration with the standard Interface Builder
  • Running applications in iOS Simulator
  • Debugger with breakpoints, variables, watches and evaluate expression
  • Refactorings, e.g. ‘Change Signature’ and ‘Extract Method’
  • On the fly code analysis and quick-fix suggestions
  • Tight version control systems integration (Subversion, Git, Perforce and CVS)

    I don’t see a feature here in the short list which Apple’s IDE doesn’t include.

    A question I asked myself..why develop appCode in the first place?

    InfoQ: What drove the decision to develop appCode?

    Maxim: We at JetBrains admire what Apple has done to desktop apps and more generally to a consumer targeted software. They’re setting new interaction design quality standards. But this is not the case when it comes to developers software, in our opinion. So we see a great opportunity for JetBrains to bring its development tools expertise to this emerging market of developers, who know how a great software should look, who care about their productivity and code quality.

    Developers even need to have XCode 3 or 4 installed to use appCode:

    InfoQ: Do I still need XCode / the Apple development infrastructure to develop applications?

    Maxim: Yes. You need to have Xcode 3 or Xcode 4 installed. At the very least we need a platform SDK that comes with Xcode, the Interface Builder and device simulator.

    I have used JetBrains’ RubyMine IDE in the past and it is not free.  I don’t think other JetBrains’ product are free, so one can only assume appCode will not be free.  Why would I pay for something Apple gives me free, as a registered developer or $5 in the App Store?

    I had thought that maybe appCode would be developed to be cross-platform, like their other products, and run on OS X as well as Windows and Linux.  This would make it a really nice proposition for non-Mac owners but the dependency on XCode makes it unrealistic.

    In summary, appCode:

    • Is an Objective-C IDE just like XCode
    • Needs XCode to Run
    • Only runs on OS X
    • Is likely not to be free

    To be fair, I downloaded appCode and it looks nice, opens my XCode projects but I ran into issues trying to actually run the project.   It built but the simulator never loaded and ran.  I will probably wait for a future EAP build to try again.

    I realize appCode is only an EAP and not even beta at this point.  I’m sure things will improve and new features will be added but I’m not sure JetBrains has a winner here.  The XCode environment is the gold standard for Objective-C development and I don’t see so many problems with that would drive me to use an alternative IDE at this point.  I will keep an open mind but it seems JetBrains is trying to solve a problem that doesn’t exist.