Live data from Hacker News

Updated Microsoft Store App Developer Agreement: New Revenue Share

blogs.windows.com

101–110 of 113 posts

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#101

Earlier quoted context omitted.

Fraud reduction is largely irrelevant on non tangible products though, especially when licenses can be revoked online.

Chargeback fees to credit cards are still massive (even if you "win" the dispute)

Those are negotiable and even stripe and Braintree only charge $15.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#102

Earlier quoted context omitted.

Fraud reduction is largely irrelevant on non tangible products though, especially when licenses can be revoked online.

Chargeback fees to credit cards are still massive (even if you "win" the dispute)

Microsoft is probably big enough to negotiate really good terms for themselves.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#103
post #13
post #6

I feel like given the circumstances, Microsoft should probably make distribution free and collect no revenue, at least until the platform becomes popular. There are costs to targeting the Windows platform, especially if you're doing things their new preferred way (UWP). Primarily a slow, difficult to work with development kit. Lots of mysterious crashes that you can't do much about, lots of leaky abstractions over CO…

Are there any stats on how successful / unsuccessful their store is?

I had to request refunds on half of the apps that I purchased because they disappeared or completely ceased functioning?

I only bought items on the Windows Store because I had a few $25 Windows Store vouchers as well.

They stopped selling Music around January 2018?

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#104
post #34

Nice move! I hope that Google & Apple will reduce their 30% tax someday..

I think this system would work well for game platforms too, such as Steam. A big point of contention for Steam is, how much the platform does for advertising your game. By having two separate taxes depending on how the game was found, you can have the best of both worlds. If you do your own brand building and advertising, then those sales get a better cut, while the platform can also get their cut for the advertising…

Steam already relinquishes their cut if the game is bought via a third party retailer. It costs nothing to generate or activate Steam keys outside the Steam store.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#105

I'd be interested to take the pulse of HN: When you are looking for a new Windows app, does opening up the store even cross your mind? I nearly always go to a web search + download first. Or if it's something dev-centric I look at scoop or chocolatey. The Windows Store is far, far behind in my mindshare. There are a few glimmers of hope though. Python has begun to distribute via the store which is cool. And the Linux…

I've started to install stuff from the store when it's awailable in the past year. Stuff like WinSCP is great - it's always current, it's 1-click, and developer also got some money from me for the effort.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#106
post #73

Desperation move. Microsoft is probably looking at its internal Store numbers and realizing it is a failure. I guess this is the final attempt. We'll see if it works.

They were talking about this change in 2017, and actually said it will come in 2018,so they kind of actually took too long to implement this.

That said, I'd say the Store is not breaking any records. It looks like their reaction to that is to allow other stores on Windows while taking a step back and concentrating on being a good platform.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#107
post #2

Here's how the new payment structure works: > When Microsoft delivers a customer through other methods (tracked by an OCID), such as when the customer discovers the app in a Microsoft Store collection, through Microsoft Store search, or through any other Microsoft-owned properties, then you will receive 85 percent of the revenue from that purchase. > When there is no CID or OCID attributed to a purchase, in the insta…

That sounds about right, although 5% (or 15%) is a pretty good deal IMO for worldwide payment processing, installer and update distribution, DRM, and their built-in tools like crash reporting, push notifications, analytics, affiliation, and attribution.

>...and their built-in tools like crash reporting...

I'm assuming you mean if it has Azure Analytics packaged into it? Otherwise, I've never heard of WER (read: Watson) being available external of Microsoft; which could have been (and still could be, plausibly) a huge trove of information (if we're talking purely on a bug trends for various devices/flavours perspective).

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#108

Earlier quoted context omitted.

PayPal has established the absolute rock-bottom industry-floor of 2.9% + $0.30 for payment processing + fraud reduction. Fraud reduction accounts for the majority of that percentage. Patreon has established that they will completely go out of business at 5%. Steam is taking 30% and Epic is taking 12%. Salaries, servers and regulation are expensive. Microsoft offering 5% is a steal.

> PayPal has established the absolute rock-bottom industry-floor of 2.9% + $0.30 for payment processing + fraud reduction. This is neither unique to PayPal or the actual floor. 2.9% + (roughly) $0.30 is pretty much the standard across all public facing credit card processors like PayPal (and their subsidiary Braintree), Stripe, Amazon Pay, Authorize.net, and more. I have heard rumors Stripe offers rates as low as 1.8…

The actual cost for credit/debit card processing is interchange itself, which averages to ~1% for grocers & about 2% for everyone else if your doing north of $200k a year in volume. High risk industries like cruises, concerts & similar will pay close to 5% (or more), as when the event doesn't pan out, all that cash will need to be refunded.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#109

Earlier quoted context omitted.

It’s insanely good deal. MSFT has to be losing money on that.

What? How? Of the services on offer, only payment processing has significant cost to Microsoft. Things like crash reporting are solved problems whose cost should be approximately equal to the cost of hosting the data.

Even if Hosting many terabytes of data and paying for thousands of terabytes of downloads worldwide was free, people aren’t. It takes people to build and maintain hundreds of store fronts, localize them in dozens of languages, run marketing programs, provide support, developer tools, etc, etc, etc.

Re: Updated Microsoft Store App Developer Agreement: New Revenue Share

#110

Earlier quoted context omitted.

That sounds about right, although 5% (or 15%) is a pretty good deal IMO for worldwide payment processing, installer and update distribution, DRM, and their built-in tools like crash reporting, push notifications, analytics, affiliation, and attribution.

> ...and their built-in tools like crash reporting... I'm assuming you mean if it has Azure Analytics packaged into it? Otherwise, I've never heard of WER (read: Watson) being available external of Microsoft; which could have been (and still could be, plausibly) a huge trove of information (if we're talking purely on a bug trends for various devices/flavours perspective).

If you're registered on their developer portal, you can upload public symbols (exports only) of your builds and receive stacks & problem signatures of any matching WER dump. I work for a small-to-mid-sized infosec company (with no special Microsoft partnership) and we've gotten WER crash reports of our UI component this way.
Post reply on HN