+/- $0.60 after PayPal's cut.
Flat fee or percentage?
... Approx 33% per transaction.
[Edit] - Since my apps are only $1 at this time, I am unsure if there's a max (i.e., 33% up to $10, etc.).
Ouch. Not cool PayPal. Not cool.
If you think that's bad....
I recently participated in Autodesk's
Portathon event, which was a lot of fun, and I got paid handsomely for each app I published (
4 of 5 apps max, per developer).
When all was said and done, they wanted to pay us via PayPal (
which I was aware of from the outset), and I had to jump through some (
albeit worthwhile) hoops in order to receive direct deposit. The only issue with the latter, was that their 3rd party payment company took a percentage in addition to my banks $19.00 fee for international payments (
even though Autodesk said they wouldn't do that). I still ended up with a great deal more of what I earned, than had I used PayPal, so it all worked out.
Back to the thread topic; as a developer, my only issues are that I just wish they'd leave formatting alone.
I submit an app pages content with my app submittal. It has paragraph formatting within it's HTML, and some app pages maintain it, other seem to remove it. Some of the developer links (
like to my homepage, etc.) 'show' fine, but are linked improperly. I check the back-end content I uploaded and it is correct.
Worst IMHO, is that I submit an app .bundle in accordance with the criteria, and what I receive back for final review prior to having an update 'go live' is different than what I submitted, but they don't bother to inform me of what changes they've unilaterally, and inconsistently made to each-and-every-single app (
I have 4 pending updates). Some examples of the changes I mean, are that they've renamed directories in my app's .bundle, they've modified my PackageContents.xml file - and I don't mean just adding additional header content for the apps store purposes, they've added XmlAttributes, and even added Command XmlNodes, and XmlAttributes to demand-load an event-based plug-in that is supposed to execute at Initialize().
As a developer I find each instance of this not only frustrating, but confusing... It seems like each app reviewer does what they want, and inconsistently at that. All of my apps are similarly structured for simplicity, and seemingly what's fine in one app is not in another that implements similar functionality (
basic context menus, nothing advanced at all). I want to provide quality app content to would-be customers, just as I do for my daily work supporting users here.
If I've done something incorrectly, point it out, offer guidance, and I'll learn... Unilateral, and unannounced changes to something I am ultimately responsible for according to prospective customers is frankly unacceptable... Ultimately, this is why I've delayed multiple app updates, which I submitted late last year, between now having to go through each one-by-one to determine what, if anything, has changed, and then address the merit individually, documenting my comments, etc. and re-submitting to Autodesk for review. Having started a new job +/- 60 days ago, with substantially greater responsibilities, I've simply not made the time for this, let alone dig into SincPac with Jeff (
I feel bad for both, but need to get to a plateau first).
/rant