There’s a recent post from Dermot Daly of Tapadoo making the argument that if you don’t update your iOS app to fit iOS 7’s new design, it’s going to be an insta-delete.
I think someone needs to take a deep breath and calm down.
In 2009, Peter Hosey wrote Warnings I turn on, and why. It remains an excellent explanation of why certain warnings, off by default, are a good idea to use. In it, he mentions the use of “treat warnings as errors” and calls it “hardass mode.”
One of the topics during the Reverse Q&A Panel at CocoaConf Columbus last weekend was how people felt about the Mac App Store and selling apps on it. Now that Apple is enforcing the sandbox requirements, some Mac developers have stopped selling on it and others are considering it.
Here’s a tip I picked up last night at our local Cocoaheads meeting: if you have a lot of RAM in your machine and a decent chunk of it is not currently in use, create a RAM disk and mount it at ~/Library/Developer/Xcode/DerivedData.
Paid upgrades in Apple’s App Stores has been a topic of some debate since the App Stores launched. Wil Shipley stoked the fires back in March, arguing that the Mac App Store needs paid upgrades:
Right now developers selling through the Mac App Store face a lose/lose choice: either provide all major upgrades to existing customers for free (thus losing a quarter of our revenue), or create a “new” product for each major version (creating customer confusion) and charge existing customers full price again (creating customer anger).
If you’re considering syncing Core Data to iCloud in your app, Drew McCormack of The Mental Faculty has a terrific series of articles discussing the difficulties he encountered while adding support for it to Mental Case.
I spend most of my development time split between Rails and iOS. Each offers a rich API that makes building projects much more productive and enjoyable. There is one place, however, that Ruby clobbers Objective-C: testing.
Now that Apple has released the complete set of WWDC 2011 videos to registered developers, those of us who couldn’t make it to the conference have the opportunity to hear about all the new, shiny stuff coming in Mac OS X 10.7 and iOS 5.
Marco Arment lays out the arguments against Apple’s new in-app purchase requirements for iOS apps:
This is partially defensible: Apple’s promotions in the App Store certainly bring a lot of people to apps, and it’s all happening on their hardware and platform. But if someone wants the Wall Street Journal app and finds it by searching for “WSJ” in the App Store and selecting it directly, who really brought that customer to the app?
Much has been said over the last 2½ years about the App Store and places where Apple is failing third-party developers. Many things have been fixed, but unfortunately, many more have been neglected or only partially addressed. On January 22, 2011, the App Store surpassed 10 billion downloads. Let’s assume 1% of those are paid and Apple only takes the minimum 29¢ for each one. That’s still $29 million. Apple needs to do a lot more to earn their 30% cut.