Speaking of sandboxing, Reeder 2 for Mac (one of the best RSS readers) was forced to remove the option to be set as the default RSS reader from within the app. This is because a function on Yosemite is longer allowed in sandboxed apps but still works fine on 10.9 [1]
While it's not the end of the world, it's just plain annoying having to remove such a common sense feature. The consequence of this means that if you were to distribute a web browser via the MAS, you will not be able to ask the user to set it as the default web browser. That's just a subpar experience.
My hypothesis for the added restriction is that it might be considered a security hole for an app to just set itself as a handler, for say, http links.
The correct way to have handled this particular situation was to introduce a new entitlement and define what content types an app might want to handle, which will get reviewed by the MAS review team. Unfortunately, the solution [2] is: "There is no solution; it can't be done anymore in the sandbox."
I would add that something as complex as a web browser would be impossible on the Mac App Store anyway -- a sandboxed browser wouldn't even be able to open file:// URLs.
Berners-Lee's original web browser was developed on the NeXT (direct ancestor of OS X)... But if he wanted to take that 1991 browser and distribute it on the Mac App Store today, he would have to remove important functionality.
Impossible on the Mac App Store, but perfectly possible on the Mac. Which is the appropriate comparison. Tim's web browser wasn't released on the NeXT App Store, after all.
Well, yes, web browsers are possible on the Mac. They are probably the most commonly downloaded type of Mac app.
Which begs my original question: what good is a "Mac app store" that can't accommodate Mac apps?
Apple isn't alone in this, of course. The Windows 8 app store (Marketplace, or whatever it's called these days) is just as limited... But really, if the most apt comparison for the MAS is the Windows 8 store, that further illustrates just how badly Apple has blown it.
While it's not the end of the world, it's just plain annoying having to remove such a common sense feature. The consequence of this means that if you were to distribute a web browser via the MAS, you will not be able to ask the user to set it as the default web browser. That's just a subpar experience.
My hypothesis for the added restriction is that it might be considered a security hole for an app to just set itself as a handler, for say, http links.
The correct way to have handled this particular situation was to introduce a new entitlement and define what content types an app might want to handle, which will get reviewed by the MAS review team. Unfortunately, the solution [2] is: "There is no solution; it can't be done anymore in the sandbox."
[1] http://stackoverflow.com/questions/26241689/lssetdefaultrole...
[2] https://devforums.apple.com/message/1059008#1059008