2

What is your approach when it comes to distributing via the Mac App Store and having been using the Sparkle framework.

I found these two sites that mention the problems and how to resolve these but I'd like to know how you handle this.

http://furbo.org/2011/03/09/mac-app-store-guide/

http://danielkennett.org/blog/2010/12/techniques-for-managing-optional-code/

Thanks everyone.

[Update]

Here's another approach:

http://bruji.com/articles/2011/02/09/conditionally-building-a-mac-app-store-applications-to-exclude-sparkle/

uem
  • 713
  • 1
  • 7
  • 18
  • Are you looking to maintain both versions? – gaige Jun 10 '13 at 12:11
  • Yes, both versions is what I'd like to have. – uem Jun 10 '13 at 13:14
  • The Craig Hockenberry article is pretty much dead-on in terms of what you need to look for. Is there something in particular you don't like about that approach? We use a slight variation, but the philosophy is the same. – gaige Jun 10 '13 at 13:20
  • Thanks for pointing that out. I'm just curious which way devs go nowadays since that Hockenberry-post is 2 years old. – uem Jun 10 '13 at 14:16
  • 1
    For this, not much has changed. There's really not any better technology than conditional compilation. I will say that if you have the framework in your app at all, you will be rejected by the AppStore (been there, done that), so make sure that's neither linked nor copied in. – gaige Jun 10 '13 at 14:20

0 Answers0