4 ms·
The App Store is two parts -- there is the developer facing part where you publish into it and the consumer facing portion for discovery right? Apple's mobile
by rkalla 15y ago
The App Store is two parts -- there is the developer facing part where you publish into it and the consumer facing portion for discovery right?
Apple's mobile and Mac App Store work this way. Amazon's app store, google marketplace, etc. etc. I think the concept of an app store implies "developer and consumer-facing pieces".
Maybe I'm missing the point you were making?
I think it's a really progressive look at software development to include the deployment/sales part of deployment directly into the IDE.
I imagine the ecosystem around Java would have been considerably different if 12 years ago NetBeans (and later Eclipse 1.0) had shipped with a Sun-managed client app store right out of the gate.
Remember the whole idea behind commercial Java Beans and Applets for sale? That might have actually worked had there been a central repository for all that with sufficient discovery tools.
Combining the app store and execution container idea all into one is just the next step of services like Google App Engine, Heroku and Elastic Beanstalk I think.
10 years ago the idea of App Engine would have seemed silly, now it's common place and hugely desired. 10 years from now, having a deployment container that doesn't directly help me sell or market my app... well that might seem like an inconvenience to me as the developer.
- justincormack 15y agoApple got the customers first, that drove developer demand not a lot of people using XCode, was what I meant. Sun could have had a market, it is true, but if it had been via the IDE they could have lost to to IBM with Eclipse. It makes no sense tying these in, when there are standard application containers that are IDE independent.
- rkalla 15y agoGotcha, thanks for clarifying. I agree the demand has to come from the consumer end first no matter how hard devs push out.