![]() I want people to choose the app that best serves their needs. I’ll just buy the official one.” That’s okay. No doubt we would lose some sales, but I suspect we would earn just as much or more.Īt a certain price point, 2 FDX Reader becomes expensive enough that a buyer comparing the two apps might decide, “Screw it. If their app costs $20, ours looks like a bargain at $10. Psychologically, whatever price Final Draft chooses for their app will become the new baseline. We’re not bringing in enough money to pay Ryan what he’s worth, let alone Nima. Honestly, the only reason we can make and support FDX Reader is that I make a good living as a screenwriter. That shouldn’t be a radical idea, but the race-to-bottom pricing of the App Store has conditioned buyers to think that anything more than 99 cents is too much. In general, I think prices for good software - particularly specialty software like screenplay readers - should be high enough that companies can earn money developing and supporting these apps. If Final Draft Reader is good, I want it to succeed. Probably, but I don’t think that’s a worthy goal. Wouldn’t staying at our current price - or going even lower - pull more sales away from the official Final Draft app? As I wrote in December, I suspect we’ll raise our price once their app comes out. Meanwhile, we’re currently priced at $4.99. What to chargeįinal Draft hasn’t announced their price yet, which has led to speculation on Twitter about how much they’ll charge, with guesses ranging from $19.99 to $49.99. Our FDX Reader is universal and works on the iPhone (and iPod Touch) as well. Perhaps the biggest difference between our app and the official one: Final Draft’s Reader only works on the iPad. They’re going to be answering a lot of emails on this topic. In our case, it’s because we can’t decipher Final Draft’s old, proprietary binary format. fdr either - and at least half of our support emails come from users confused why we don’t. I suspect many users will be disappointed that Final Draft Reader apparently only supports. Page breaks aren’t part of the file, but rather an internal calculation. We come very close with FDX Reader, but we’ll never hit them exactly. One advantage: Final Draft Reader should be able to exactly match page breaks (and page numbers) with the desktop version. The question will be whether the official app does enough things better. Production drafts (colored pages, locked pages)Īll of these things are useful.So the question now is how to position our app vis-à-vis the official one.Īt least on paper, their app does more than ours: In fact, the only reason we made our app is because we needed to read Final Draft files and their app didn’t exist. Their app is a lot like our app, FDX Reader. After a long gestation, Final Draft has announced that their official iPad app, Final Draft Reader, will be available for sale next week.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |