Feed on
Posts
Comments

Corporations will not create internal Windows Phone 7 applications unless they have a way to restrict deployment of their apps to controlled list of registered phones.  As it stands today, it is not possible to do private deployments.  The next version of Windows Phone 7, known as Mango, aims to change that.  Microsoft previewed the upcoming changes to the Marketplace at their web conference (Mix11).   There will be three areas to deploy apps: Public Marketplace , Private Marketplace and Beta Marketplace. Be sure and read the details below but be aware:  Private Marketplace as envisioned by Microsoft is not the much anticipated Enterprise Marketplace.

It’s still early times, Mango will not ship before September 2011, so realize that the details many change as we get closer to ship date.

Public Marketplace

Let’s start with the current marketplace offering. In Mango terms this is called Public Marketplace. To deploy an app to the phone currently you must do one of the following.

Developer Account:  Sign up for a developer account at AppHub ($99 USD).  Unlock your developer phones and sideload the app.  Limited to 10 sideloaded apps on the phone at any one time.

Jailbreak: Find a way to jail break your phone, then side load apps.

Public Marketplace:  Sign up for a developer account at AppHub.  Upload your app to the AppHub server.  The app will go through the certification process and if approved it is published to the marketplace.

Public apps are available for anyone with a phone and can be discovered by searching the Zune Marketplace.  The apps must pass certification before being published. 

Beta Marketplace

Currently if you want to test a new WP7 app you email a few of your developer friends and ask them if they will sideload your XAP onto their phone.  The new Beta Marketplace will make testing pre-release apps easier.

With Beta Marketplace you solicit testers for your upcoming release. These users can be company employees, or they can come from from the general public. If they volunteer they must provide you with their LiveIDs.  You can have up to 100 testers per beta marketplace.  The developer adds the tester LiveIDs to the beta marketplace and sends an invitation email to the tester. The invitation email includes a deep link to the beta XAP. 

Tester must login to Zune before they can install the beta application. If they are not on the approved list, they will not be able to install the application.

This is good.  The tester does not have to be a developer, doesn’t have to an unlocked phone and Microsoft controls the whether they can install the application.

Each beta marketplace is open for 90 days and then is automatically closed.  Though not stated by Microsoft I believe you can create more than one beta marketplace( to add more than 100 users). Obviously you can create other beta marketplaces as you release improved versions of your beta app.

Since you are releasing a beta, Microsoft doesn’t require the app to go through certification.  That means you can upload the XAP and instantly have it available to your tester community.

Private Marketplace

Some would call this the Enterprise Marketplace.  I’d say that they need to listen to what Microsoft said at Mix11.

"It is not an enterprise software distribution mechanism, by any means, but it is a way of distributing applications and games to a set of users "  -Todd Brix

The only difference between a Private and Public marketplace is the ease of discoverability to the general public.  Because the app in not listed in the Zune marketplace, you cannot search and find the app. Therefore, in order to distribute the app you must send a deep link to your intended audience. 

Other than the discoverability difference your app is handled the same as a public marketplace app. It must pass certification. It can be updated to a new version and users will automatically received update notifications.  You can create a free or paid version of your app. 

You can share the app deep link with friends, magazine writers, bloggers etc. and they can preview and use the application.  Since the app is certified, you can easily change it to public at a later time. 

Enterprise Marketplace

Microsoft has not announced an Enterprise marketplace yet.  That hasn’t stopped some people from assuming that the Private marketplace is the enterprise solution however. In fact I made the same mistake when I was live tweeting the Mix11 event this week.

Here is what make Private marketplaces unsuitable for enterprise distribution.

Private by obscurity

You give your users a deep link to the the application that takes them to the install page.  The app is not listed in the Marketplace, or findable through marketplace search. But if they share the deep link with with another phone user, then that friend can install that app too.  My guess it that the community will figure out how to find private deep links within days of the release of Mango.

No access control: 

Any phone user can install your application, provided they can find the deep link.  There is no way to restrict access to a set of users, like in the beta marketplace.

Summary

I’m really excited about the Beta marketplace as it makes it easy to test and share applications with a list of users.  I don’t see much benefit from Private marketplaces yet, perhaps I don’t understand the use case for them.

I’m severely disappointed that Microsoft hasn’t produced a better enterprise story.  I hope they are waiting until later in the Mango lifecycle to share there plans for real enterprise deployment. 

Here is a table that summarizes the differences between the proposed new marketplaces.

Details Public Private Beta
# of Users Unlimited Unlimited 100
App Price Free, Paid Free, Paid Free
Lifetime Forever Forever Closed after 90 days
Updateable Yes Yes No
Publicly Discoverable Yes No No
Access Control None None Restricted to published list of Live ID’s
Certification Required Yes Yes No
       

8 Responses to “Mango adds Beta and Private Marketplaces to Windows Phone 7 and neglects Enterprise”

  1. Scott Bussinger says:

    One use case for a private marketplace is vertical market apps. Perhaps you have an app that interfaces with a particular medical records system. Being discoverable by the general public makes no sense as the app would be of no use to them and it’s likely to just collect a bunch of negative reviews (or support calls) from people who don’t understand what it’s for. The medical records vendor could promote the app to their users on their website via a deep link. In this context, both free and paid applications make sense.

    But I agree that private marketplaces are not likely to used all that much.

  2. [...] seront disponibles : un public, un privé et « beta ». Comme l’explique Walt Ritscher, Microsoft compte sur chacun de ces Marketplaces pour se rapprocher des développeurs mais aussi et [...]

  3. Tiago says:

    Hi,
    Just added Enterprise marketplace request on wp7dev uservoice, based on this post.

    http://wpdev.uservoice.com/forums/110705-app-platform/suggestions/1735593-enterprise-marketplace?ref=title

  4. Brian Jimdar says:

    Private marketplace is all you’ll need and here’s why:

    Security is based on authentication not access to client bits. Anyone can get access to an email client and point it at a Company’s mail server, but they can’t read my email because they don’t know my password.

    Security based on restricting access to download IS security through obscurity.

    Just as you expect that the community to find a way to figure out how to discover private app links, I would similarly expect the community to quickly discover how to download apps from any future “Enterprise Market” that is delivered. As an Enterprise App developer you will then have to consider security assuming that malicious users will have access to your bits.

    If the only difference between the private marketplace and some other “Enterprise marketplace” is a download restriction that you do not trust, then there is no effective difference.

    So even if there is some future announcement about “Enterprise Marketplace”, I don’t think it’s likely to be used all that much.

  5. [...] The private distribution model has been signalled as a let down for enterprises. This post details the perceived shortcomings: http://blog.wpfwonderland.com/2011/04/15/mango-adds-beta-and-private-marketplaces-to-windows-phone-7... [...]

  6. Ijimeko says:

    You do know that the Private and Beta marketplaces are for the Enterprise market, right? Todd Brix is saying that because of lack of some key Enterprise concerns (identity federation, security, etc.), not because it’s not Enterprise.

    Let’s say you were developing a set of internal training courses for your company as apps to train your sales people on your new product. You want to test the app and gain feedback for 30 days on the Beta marketplace before finalizing and releasing to the regular Private marketplace for all your sales folks to download. SCORM tracking would be for your company’s LMS only. That’s what these two new marketplaces are to be used for.

  7. Burton says:

    am I missing something or couldn’t an enterprise app simply require a login? would it fail certification or something?

  8. j says:

    The article doesn’t state whether or not the beta apps expire with the beta marketplace. I know devs don’t want their apps in beta forever, unless they’re Google, but my curiosity leads me to this question: of the beta apps don’t expire the. Can’t the beta marketplace be used as a temporary enterprise marketplace, At least for a small division/dept.? The people that can see or download the app are controlled. No one else can access it. Also no approval from Microsoft is needed. It seems to be everything wanted in an enterprise marketplace except the expiration, the limitation on users, and the inability to update apps. But at least it would be a short term workaround.