Comments on: Airfoil Speakers Touch 1.0.2 Is Now Available

By: Marty Gough

Marty Gough — Tue, 01 Dec 2009 04:58:33 +0000

I’m so glad that this story has a happy ending! There’s hope!

I just posted about another rejection for following Apple’s rules. Unfortunately, the only people this will hurt is our users.

http://www.juicybitssoftware.com/2009/11/30/apple-is-rejecting-its-own-advice/

By: Soth

Soth — Sun, 29 Nov 2009 23:03:20 +0000

This is a good thing. People who give up at first rejection and go out in the press to slam apple aren’t commited enough to their apps. All they see is money and often they play on the apple brand and icons to make their app seem more official then actually develop their own art and brand.

There is no mass exodus of developers. Alot of them have no trouble at all with submitting apps. Also thank god for the review process or we would have had an appstore flooded with 500000 apps about nothing right now. Thank god that apple has removed app spammers who just put up different versions of the same app or apps making a funny sound when you press 1 button and nothing more.

By: Tristan

Tristan — Sun, 29 Nov 2009 06:06:24 +0000

I encourage you to at least look into developing for Android, should you have the desire to bring a mobile app to market in the future.

A version of AirFoil speakers for android would be great, and the market for it is growing rapidly. I’d be first in line, as a Mac user with an Android phone, happy with both.

By: Dave Mac

Dave Mac — Wed, 25 Nov 2009 08:07:16 +0000

Jim Hillhouse… If you read all of the posts, you would find that RA did not use any of the NSImage code in the iPhone app. It was in the Mac app, of which the picture was sent to the iPhone. Not much different that a web view or VLC stream.

By: Carlos

Carlos — Wed, 25 Nov 2009 04:47:43 +0000

Still can get to see graphics from a PC using Airfoil!
Is there an Airfoil PC update coming soon?

By: Jim Hillhouse

Jim Hillhouse — Wed, 25 Nov 2009 02:51:46 +0000

Paul, the problem was that you were using images that were allowed under the Mac developers agreement but not the iPhone developers agreement. It’s too bad that >90% of the posters here don’t know the difference between NSImage or UIImage, “Mac OS X” and “iPhone”, and haven’t read the “Registered iPhone Developer Agreement” or more specifically “Guidelines For Using Apple Trademarks and Copyrights”.

I know you guys are not lawyers, but you don’t need to be one to understand that understand that, under Part 8 of the Agreement,

10. Use Of Apple Trademarks, Logos, etc. You agree to follow Apple’s Guidelines For Using Apple Trademarks and Copyrights as published on Apple’s website at http://www.apple.com/legal/guidelinesfor3rdparties.html and as may be modified from time to time. You agree not to use the marks “Apple,” the Apple Logo, “iPhone,” “iPod touch” or any other marks belonging or licensed to Apple in any way except as expressly authorized in writing by Apple in each instance. You agree that all goodwill arising out of your authorized use of Apple’s marks shall inure to the benefit of and belong to Apple.

or more specifically under the Guidelines,

2. Apple Logo and Apple-owned Graphic Symbols: You may not use the Apple Logo or any other Apple-owned graphic symbol, logo, or icon on or in connection with web sites, products, packaging, manuals, promotional/advertising materials, or for any other purpose except pursuant to an express written trademark license from Apple, such as a reseller agreement.

And talking about using NSImage constants is a bit misleading. Why? Because the NSImage constants, e.g. NSImageNamedMobileMe, are not there in UIImage. Why not? Because the iPhone developers agreement did not allow their use until today. You guys should have known you were heading for trouble on that alone.

I’m glad that RA managed to influence Apple to lighten-up on the use of Apple copyrighted images in iPhone apps, something previously not allowed. I agree that such a restriction was silly. Still, your troubles in getting your 1.0.1 update were largely of your own making as you were trying to push a string with Apple on an issue to which RA had no rights. You won the war-of-words–kudos.

But to other lesser-known iPhone developers, of which I am definitely one, the rule is…follow your iPhone (not Mac!) developers agreement and do not count on Apple changing its mind. If Apple tells us to change something in our app then consider which is more important, income or arguing.

By: John Thomson

John Thomson — Tue, 24 Nov 2009 22:49:06 +0000

Thanks for updating this.
I use a mac & PC.
i can’t get the iphone app to work with airfoil for windows via windows 7. Should I be able to?
Thanks,
John

By: Kevin Munoz

Kevin Munoz — Tue, 24 Nov 2009 19:52:49 +0000

I had considered buying the iPhone app, and other Rogue Amoeba Airfoil software, but I have decided against it. I cannot trust the future support and development of a company that has walked away from an entire platform, after a single incident. You write that “we don’t believe it makes good business sense for us to commit much in the way of resources to the iPhone.” I don’t believe it makes good consumer sense for me to commit much in the way of money to Rogue Amoeba. Good luck with your other customers.

By: Mike Ash

Mike Ash — Tue, 24 Nov 2009 17:01:51 +0000

garymca: Airfoil for iPhone has been on our minds for a while, but it's just not practical. We wrote a post about the reasons: http://www.rogueamoeba.com/utm/2008/12/12/thoughts-on-airfoil-for-iphone/ While that post is nearly a year old now, the limitations it discusses haven't changed at all.

By: garymca

garymca — Tue, 24 Nov 2009 11:27:18 +0000

I would like to see you produce an app for iPhone that does the reverse of Airfoil Speakers Touch. I want Airfoil for iPhone, so that music on my iPhone can be played wirelessly over speakers attached to my Airport Express, the same as what I can do with my laptop.