Showing posts with label App Development. Show all posts
Showing posts with label App Development. Show all posts

Wednesday, June 25, 2014

Quick thoughts on the Aereo judgment, more to come

I'll give a more full post imminently, but my initial thoughts

  1. The majority opinion is policy, not law. It's telling that they never once reference the prior precedent, Cablevision, except to note that it was the prior precedent. That means they're not giving any meaningful guidance, which is what you do when you're trying to reach a targeted result.
  2. Justice Scalia is 100% right: the Court's ruling replaces widely-accepted rules for service-provider liability with an improvised standard of "looks like cable TV".
  3. There is no reason to limit this reasoning to cable TV. Although the Court takes great pains to say it's not ruling on cloud computing or any other technology, I'm not talking about technology. I'm talking about a method of legal reasoning. If "looks like cable TV therefore is regulated like cable TV" is the test for determining the scope and ambit of a law, then why stop with cable TV? "Uber looks like a taxi therefore it should be regulated like a taxi and be forced to get medallions.". "Food trucks look like a restaurant therefore they should be regulated like a restaurant and be forced to provide restrooms."

Like I said, more to come, but especially #3 concerns me.

SOURCES:
Aereo judgment http://www.supremecourt.gov/opinions/13pdf/13-461_l537.pdf

Monday, October 29, 2012

How does the HathiTrust book-scanning judgment affect e-books and audiobooks?

Scanning copyrighted works and making them searchable on the Internet sounds to many authors like it shouldn't be legal. But on October 10, a Federal Court in New York released a judgment holding that may be. That judgment raises significant issues for authors, publishers, and consumers, giving new scope to fair use of copyrighted materials in the USA.

Thursday, October 25, 2012

"Is this the worst paragraph in your publishing agreement?"

The Passive Voice, a blog I follow that has tons of information for authors, has a really important post today entitled "Is this the worst paragraph in your publishing agreement?"

The advice in here is good for not just authors. App developers and film/TV producers should know about it too.

Wednesday, September 19, 2012

Four things app developers need to know about the new FTC mobile app marketing guide

On September 5, the FTC published its new guide to marketing mobile apps, and although it may not make any changes to the law, it will probably come as quite a surprise to many app developers.

The first points in the Guide deal with the general issue of misrepresentations. And although the language in the Guide is chatty, the points in there are all business. But they're also not hard to comply with, boiling down to one simple one: don't say things about your app that you can't prove to be true. This seems like common sense. Amazingly it's not. The FTC points to an app whose developers claimed it could cure acne. I'm not even sure how that could be possible. Apparently the FTC agreed, because they took action to shut it down.

But that much is easy. Where it gets a bit more involved is when the FTC turns its attention to privacy issues. The FTC is very concerned about privacy in the mobile app space. I'm even told they have mystery shoppers downloading apps and testing them out for privacy compliance issues. No surprise then that most of the Guide is dedicated to privacy. And the Guide contains three additional big points on privacy issues that app developers should consider:

Friday, September 14, 2012

Two easy ways to succeed on Kickstarter (and two reasons you should look for these kinds of projects)

Over the weekend, Ars Technica put up a quick post on old games getting rebooted through Kickstarter. They talk about how it's fertile ground for rebooting old games. Unfortunately, at least for creative endeavors, revisiting well-trodden ground may be one of the only profitable uses for it. But surprisingly this might be a really good thing for people looking to back Kickstarter projects.

As someone who is mentioned twice (obliquely) in the promotional video for one of the most successful Kickstarter reboots (when at Microsoft I worked on Shadowrun), I have a bit of a sentimental interest in this topic. It would seem that if you want to succeed on Kickstarter, try for one of two things:

Wednesday, July 25, 2012

When agents are better than lawyers, and vice versa

Agents and lawyers both negotiate contracts. They both seem to fill very similar roles. And they both want your money.

So how are you supposed to know whether you need one, the other, or both?

Oversimplifying the role of each of an agent and a lawyer:

Thursday, July 19, 2012

Four last things to remember for now about net profits clauses

1. If your publisher is doing deals with related parties, they have to charge what are called "arm's length" rates. A good way to show this is with an example. If your publisher is charging you a marketing fee  is using a marketing firm in the same corporate family, there's a really strong incentive for them to make the fee as high as possible. The "arm's length" rule says that they can only charge you the same fee that a company not in their corporate family would charge. If your publisher is charging fees against your book that you think are totally crazy, look for some industry data to see if you can use this to change their position.

Three common deductions that publishers and studios take, and tips on what to do in response

Here's three of the most popular or egregious deductions from book and film deals:
  1. Distribution fees. Although there are always costs involved in shipping product, many times the distribution fee in a contract is determined as a fixed fee or percentage, such as "20% of gross profits". I'll let you decide whether this kind of calculation is based on actual costs of distribution. If it helps to figure this out: often the distribution company is a related party to the publisher. By the way, the same thing often happens with marketing fees: they are calculated as a percentage of profits and aren't usually tied to actual spending.
  2. Overhead. Basically this represents salaries and other internal costs to your publisher. Publishers often try to pass through the cost of editors, accounting staff, lawyers, and other employees. Some even want to charge a fee for things like photocopies, long distance phone calls, and office rent. You'll see this as a percentage of your profits, which is a clear signal that it's nothing to do with the work they've actually done on your project.
  3. Interest. If your publisher is paying you an advance, then that's money out of their pockets. If you read the advances and royalties post then you may recall that you don't get paid any royalties until your publisher recoups the advances. Some publishers also charge you interest on the advance; most film and TV studios will do this. So if you get a $15,000 advance and 10% royalties with a book whose wholesale price is $10 but 10% interest, then you don't get paid on copy 15,001. It takes another 1,500 units: you get paid at unit 16,501. Same thing for the marketing and distribution charges: some publishers allocate money to a project and then charge a interest against it even though the money isn't spent yet.
If you see these things, try these responses:

Wednesday, July 18, 2012

Why net profits can mean no profits: learn how to protect your money

Net profits clauses are almost a dirty word these days, but they didn't start that way and they don't have to be. It really comes down to the way they're written.

Taking net profits used to be something only big names got. One of the first people to take a net profits clause in a contract, if not the first one, was Jimmy Stewart in 1950. His version of the net profits clause would have worked similarly to the way these work today: talent and creators agree to take less money in advance but they get additional funds if the project makes money. The thinking is: if the project is a success then everybody wins, and if not then everyone loses less.


But as time went on that last statement became less and less true. Today there are often clear winners and losers in a net profits situation. And the publishers and studios do their best to make sure they're not the losers.

Tuesday, July 17, 2012

Understanding advances and royalties clauses, and two things to think about when deciding to take them

Getting paid is great, but getting paid over and over is even better. Or is it? Payments over time are a bit more complex, sometimes a lot more, than a flat fee. But at the end of the day they break down into two buckets:
  • Royalties
  • Advances on the royalties
You might see a contract say that you'll get $1,500 advance on signing against 10% net royalties. Let's use that as an example. Here's what that means:
  1. On the day you sign the contract, your publisher/studio/whatever will give you a check for $1,500. You can cash that, it's yours. But...
  2. Effectively, you've borrowed money from yourself. That $1,500 will be paid back from your royalties. If your book (for example) wholesales for $10, let's assume there are no deductions (which is a HUGE assumption and I'll come back to that), then you're making $1.50 per unit sold. So you don't get paid until you've sold at least 1,000 units ($1.50 x 1,000 units = $1,500).
  3. At unit 1,001, you start getting $1.50 per unit sold.

Monday, July 16, 2012

Four steps in determining whether a flat fee is right, and three things to consider

In a previous post (http://bit.ly/P4CUUb if you missed it) I discussed the issues that might lead people to take flat fee deals. Now it's time to talk about how to calculate flat fees and whether a flat fee structure is right for you. I'm sorry, but there will be math today...

In the book world it's actually pretty easy to figure out whether a flat fee is a good deal:

Friday, July 13, 2012

Show me the money: what you need to know about getting paid

If you're creating valuable content, you may someday want to get paid. And that means you'll need to know something about how payments are structured in entertainment contracts. I know, this could be tedious. But when we get to talking about money, and especially in future posts when I go into net profits clauses, knowing the basics will be really important.

Oversimplifying drastically, there are two basic types of payments:
  • Flat fees
  • Payments over time (royalties and advances)
First I'll talk about flat fees. Then I'll cover royalties and advances.

Wednesday, July 4, 2012

App developers: if you sell into the EU and don't think about these four things, you'll hate yourself in the morning

For European app purchasers, July 4, 2012 may be their software independence day. (Okay, I admit that was horrible. I couldn't resist.)

Long story short: in the USA, if you download software, the developer has the right to restrict you from passing your download to someone else. Your app can be tied to your phone or your tablet and it's a violation of the license to sell the app to someone else. Until today, that was the case in Europe too. But after a lawsuit brought by Oracle against a company called UsedSoft, a sort of marketplace for buying and selling licenses for downloaded software, things are different in the EU. And for everyone from app developers to authors to musicians, this is a big change.