'Installed' apps, the Mac App Store, and you
#1
Posted 07 January 2011 - 12:00 PM
#2
Posted 07 January 2011 - 12:13 PM
#4
Posted 07 January 2011 - 12:37 PM
#5
Posted 07 January 2011 - 12:40 PM
busterpkeaton, on 07 January 2011 - 12:13 PM, said:
Have fun with that.
#6
Posted 07 January 2011 - 12:41 PM
#7
Posted 07 January 2011 - 12:50 PM
Think about how Apple has rarely used serial numbers to unlock your application. Now, they simply use your Apple ID to control how you install your applications thru the App Store. I think it is brilliant but, at the same time, I miss the ability to have the installer "backed up" somewhere else.
#8
Posted 07 January 2011 - 12:56 PM
busterpkeaton, on 07 January 2011 - 12:13 PM, said:
As a developer, I do not feel that Apple has wrung any control from me. I have the option, for some of my software, to voluntarily cede a small amount of control in exchange for other benefits of store distribution. Nobody held a gun to my head and said I had to put the subset of my software that's standard applications in the store.
#10
Posted 07 January 2011 - 01:22 PM
#11
Posted 07 January 2011 - 01:34 PM
busterpkeaton, on 07 January 2011 - 12:13 PM, said:
Ewe go GRLFRND!
KTHNXBY!
#12
Posted 07 January 2011 - 01:39 PM
For those who may be curious, the command path for lsregister is now:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -dump
#13
Posted 07 January 2011 - 02:21 PM
#14
Posted 07 January 2011 - 03:34 PM
mournac, on 07 January 2011 - 02:21 PM, said:
Sure. In pursuit and maintenance of a high-quality user experience. Software that uses undocumented (and thus subject to change) APIs will and should get rejected. But they don't have the resources to police esoterica like the strength of licensing algorithms any more than any other retailer does. They wouldn't have gone live with 20 apps apps this week if they were doing that, and they'd be earning a much higher cut than 30%. QA is a bugger.
What Apple can do (and does) is give developers the tools to do things right. They can't force developers to use those tools and can't viably validate it in the general case anyway. It's the developer's responsibility and the developer's loss if they don't.
As a developer, I have very little tolerance for coders who cut corners on things that are trivial to do right in the first place, and no sympathy for the ones who get bitten strictly by their own laziness. (I do not exempt myself. No one has yet critiqued my software more aggressively than I do.)
This post has been edited by bastion: 07 January 2011 - 03:39 PM
Help












