One Publisher’s Experience with KDP Select

A mistake, pure and simple.

Back in December, I wrote “Amazon’s Bribe to Publishers: KDP Select and the $6 Million Fund,” a blog post where I discussed the Kindle Owners’ Lending Library and Amazon.com’s attempt to fill that library with books: the KDP Select Program.

The Deal

KDP Select offers Kindle format ebook author/publishers a chance to earn a piece of a monthly $500K or $600K fund. Enrolled books must:

  • Be available for sale on Amazon.com only. In other words, if you enroll a title in KDP Select, you cannot sell the same title as an ebook anywhere else. Amazon.com gets the exclusive right to sell your ebook on Amazon.com.
  • Allow Kindle owners who are also members of Amazon Prime to borrow the enrolled book for as long as they like for free.
  • Keep the enrolled title in the program for complete three-month terms. Once you sign up, there’s no getting out. And if you don’t turn off the automatic renewal option — which is enabled by default, of course — the book is automatically re-enrolled for another three months.

There are other “benefits” as well. For example, you get the option of making your book available for free to anyone on Amazon.com. (Imagine that! They let you give it away!)

The Bait

Compensation comes in the form of a share of the fund. Here’s how Amazon explains it; note the big numbers they use to make author/publisher mouths drool:

Your share of the Kindle Owners’ Lending Library Fund is calculated based on a share of the total number of qualified borrows of all participating KDP titles. For example, if the monthly fund amount is $500,000, the total qualified borrows of all participating KDP titles is 100,000, and your book was borrowed 1,500 times, you will earn 1.5% (1,500/100,000 = 1.5%), or $7,500 for that month.

So according to Amazon, although you’re letting a whole bunch of people read your book for as long as they like for free, you could still make $7,500 (or even more!) in a month on that book.

I Bit

My only ebook title at the time, Making Movies: A Guide for Serious Amateurs, was selling a few copies here and there on Amazon.com’s Kindle store, Apple’s iBookstore, and BN.com’s NOOK store. Not anywhere near enough to make me feel good about my first attempt at ebook publishing.

I thought for a while about KDP Select. I blogged about it. And I figured, what do I have to lose? So I signed up in December and even did a free book promotion for Christmas Day.

The Results

Over the next three months, I saw the following results:

Transaction TypeUnitsEarningsPer Unit Avg.
Sales at 35% Royalty2$2.80$1.40
Sales at 70% Royalty37$92.46$2.50
Free Book (Christmas Promotion)333$0.00$0.00
KDP Select Borrows10$18.40$1.80
All Transactions382$113.30$0.30

Let’s take a moment to analyze this. Here are the points that jump out at me:

  • Over a three-month period, the KDP Select program earned me a total of $18.40 for this title.
  • During the same period, regular Kindle earnings totaled $95.26. These are actually people who bought my book. I would have earned at least this amount if I had not been on the KDP Select program. I might have earned more if the 10 people who borrowed my book had bought it instead.
  • The average earnings per book borrowed was $1.80; the average earnings per book sold was $2.44 per book (that’s $95.26 ÷ 39).
  • Factoring in the free books, my KDP Program average earnings was less than 6¢ per book (that’s $18.40 ÷ 343).

Of course, this does not take into consideration sales that were lost because the book did not appear in buyer-preferred markets such as the Apple iBookstore and BN.com NOOK store. Based on sales figures before and after the book’s enrollment in the KDP Select program, that could be anywhere from 5 to 15 units per month.

So the KDP Select program earned me $18.40 and possibly lost me quite a bit more.

I don’t see any good from this at all. None. Do you? If so, explain it to me.

The Exposure Argument

A friend of mine who published his first novel on the Kindle platform enrolled his book in KDP Select about a week or two before I did. He and I had discussed it briefly via email before I dove in. He had the same “it’s worth a try” attitude that I did.

The other day, I contacted him with the following question:

How did your KDP Select deal go? Did you make any money worth talking about? I’m about to blog about my experience and was wondering what you thought about it.

His response:

Definitely no money worth talking about, unless that would be about $25! And no borrows at all. However, I’m letting it run for another 3 months. What has been encouraging is working with World Literary Cafe’s free promotion day, which runs through KDP Select’s free promotion days. That doesn’t bring in money directly but does at least bring exposure which has resulted in some sales and hopefully reviews at some point.

And that brings up an interesting point: exposure.

A writer who is just beginning to publish his work (such as my friend) has different goals than a writer who has been publishing her work for years (such as me).

Show Me the Money

I’m in it for the money, pure and simple. As print publishing dies and my existing titles no longer warrant revision, I need something to fill in the income gap if I expect to maintain the freelance lifestyle I’ve enjoyed for the past 20+ years. I need to create a book for a definable market and sell to that market at a price it’s willing to pay. In the ebook world, that price appears to be under $10 — more likely under $5. I did the math and realized that in order to succeed on this path, I need to build a library of long-lived titles and sell an average of 60-80 books a day. That’s why I was initially so disappointed in the sales results for my first book. It wasn’t even a drop in the bucket I needed to fill if I wanted to continue earning a living as a writer — which is what I’ve been doing for 20 years.

But I’m not in it for exposure. I have exposure. I’ve written and published more than 80 books, the vast majority of which are with major publishers such as McGraw-Hill, Peachpit Press, O’Reilly, and Macmillan. I support my books via a Website that gets about 1,000 hits per day. I’m occasionally interviewed on podcasts and video podcasts and have appeared numerous times at Macworld Expo. I may not be a “name brand” like some others who write the kinds of things I do, but I’m certainly quite a step up from those just entering this field.

Expose Yourself

My friend, however, is not in the same position. He’s new to writing novels and, as anyone who has done so can tell you, it’s extremely tough to break in. There’s lots of competition, much of it from best-selling authors that people turn to every time a new title comes out. It’s hard to get recognition for your work, let alone try to sell it when there’s just so much competition.

He’s doing the smart thing — the same thing I did years and years ago when I started out: he’s trying to build a name for himself. To do that, he needs to get his work in front of as many people as he possibly can. He needs his book read and reviewed, preferably with lots of stars and good comments. He needs to begin building a base of readers who not only like this first book, but will be anxiously awaiting his second. And third. Readers who will be willing to show support by paying to read his work.

And that’s why he sees KDP Select as something that might help him in the long run.

Is KDP Select Worth It?

In my mind, no. Definitely not. The exclusivity is enough to convince me that it’s not something I ever want to do again. After all, my third Maria’s Guides book, iBooks Author: Publishing Your First Ebook, is selling like crazy on the iBookstore. If I did an exclusive on Amazon.com, I’d lose out on all of those sales.

But for authors/publishers just starting out and trying to do the best thing for the long haul, it might be worth a shot. My friend seems to think so.

A Desert Flying Gig: Day Two

Cut short by a tragic disaster.

The second day of my job got off to a weird start. Although I was supposed to be at the client site at 8 AM, a family emergency had me driving toward Phoenix at 7:10 AM — the same time I should have been driving to the airport to get the helicopter. I wasn’t happy about this; it meant I’d be at least 3 hours late for work. Although my client was understanding, I wasn’t. The mission I was sent to accomplish — get two stranded people to Sky Harbor Airport in time for a 9 AM flight — was impossible to achieve in the time allotted. So not only was I going to let down a good client, but I was doing it for no good reason.

Fortunately, the two stranded people were able to make other arrangements. I was only 5 miles south of Wickenburg’s town limits when I got the call and was able to turn around. I arrived at the airport at 7:30. Even after removing the tie-downs, preflighting, hooking up the helicopter’s nosecam, starting up, warming up, and making the flight, I’d still be there within 15 minutes of my originally scheduled arrival time.

Nothing much was going on at Wickenburg Airport that morning — although there was a twin and a small jet parked in the jet parking area. I took care of business, made my radio calls, and took off to the west.

Along the way, I tried to notice things that I hadn’t noticed before — things I hadn’t included in yesterday’s blog post about Day 1. I realized that there weren’t nearly as many areas of carved water channels as I remembered. And I noticed cow paths. Other than that, there was nothing different, nothing to add to yesterday’s report.

I did a much better job bleeding off airspeed before coming into landing. The day before, I’d spotted an alternative landing zone that was must closer to the “town.” There were only two drawbacks that I could foresee: they were closer to the horse corrals, so I’d be more likely to frighten the horses, and it was much closer to the road, so I’d be more likely to stir up dust. I decided to give it a try.

Arrival at Robson's
This “nose cam” shot from my final approach shows my landing zone (on right, beyond cactus) and the whole town, including the hotel.

As I approached, I began having doubts about the clearance between my main rotor blades and a palo verde tree at the edge of the landing zone. It had certainly seemed like enough space when I walked past the day before. I knew that judging distances could be tricky when airborne and decided to trust my initial thoughts about the spot. I kept coming.

The dust started kicking up when I was still 50 feet up. Not exactly brownout conditions, but a lot more dust than I like to see. Out of the corner of my eye, I noticed two of the horses prancing around a bit as the dust cloud approached them. Not exactly panicking, but far from calm. I wondered if the dust would make it all the way into town.

Knowing that the best way to make the dust stop blowing was to get on the ground and throttle down to idle power, I expedited my landing. The spot I picked was level and firm. I cut the throttle and, as predicted, the dust stopped churning. By the time I was tightening up the control frictions, the horses had already calmed down.

I had plenty of clearance from all obstacles.

Parking, Day 2
My parking spot on the second day was much closer to town.

I shut down and let the blades spin to a stop while I removed the two back doors. My clients used the back seat area of the helicopter for their equipment and we worked with the doors off. I figured I’d make up for being 10 minutes late by having the helicopter all ready for them when they came out with the equipment.

Not that anyone came running out to meet me. They usually don’t.

I grabbed my gear and headed to the cafe. Along the way, I saw some familiar faces and was greeted with a few waves and hellos. Inside, I met with my main contact and explained the family emergency that had prompted my phone call an hour before. Then I grabbed a glass of orange juice and went out to track down the folks who would be installing equipment in the helicopter.

The Equipment Installation

The tech folks were based in another part of the long building that had been set up like an old fashioned soda fountain. Most of the people reading this probably never even saw the real thing — they just don’t exist in many places anymore. This was made with components taken from real soda fountains — countertop, simple round bar stools, ice cream bins, syrup pumps, blenders, malt dispensers. Most stuff dated from the 1940s through the 1960s. None of it was set up for use anymore; every cabinet and bin was used to store paper and brochures and gift shop items. There were a handful of booths, each of which were being used to stage equipment. The walls were lined with gift shop items, all of which had likely been there at least five years. Some of the items were older than me.

I found the first tech almost immediately. He had a remote controlled camera head that he needed installed. It was part of a kit that included a 50-pound customized Pelican case containing a battery and some electronics. He configured and tested it while I waited, then showed me how he could control the camera head with his iPhone. Cool. We carried it out to the helicopter and found a good place for it on the front passenger seat. I got a few instructions about how to turn it on at flight time and we headed back to the soda fountain.

The antenna/radio guys were next. I watched them assemble and mount their equipment, tested occasionally to make sure it was mounted firmly, and picked up snipped wire ties as they dropped them in an effort to keep my landing zone FOD-free.

By 9:30 AM, the equipment was all set up in the helicopter to everyone’s satisfaction. For purposes of client confidentiality, I don’t share photos of their equipment or setup.

The Wait

Then the waiting began. The helicopter was just part of the testing process; there were vehicles and personnel vests to be configured, too. I knew from experience that this could take hours, but I hoped it wouldn’t be that long.

I took my camera out and began wandering around in the immediate area, shooting images of the few wildflowers that grew beside some of the old iron mining and farming equipment. It was a disappointing spring; wildflowers were limited to desert marigold, some brittlebush, and another yellow flower that might have been desert senna. There were also a few small pale purple flowers. The globe mallow were just starting to bloom. Hedgehog cactus should have been in full bloom, but I didn’t see any anywhere. Ditto for poppies.

Brittlebush
Heavy Metal

I spent about 45 minutes wandering around, trying to get good images. I’d run out of the house that morning without my tripod or monopod, so I set the camera for shutter speed priority and set the shutter speed to 1/1000 second. With full sun on yet another cloudless Arizona morning, there was certainly enough light. But I also got the narrow depth of field that I like when shooting flowers close up. The only disappointment was the lack of flowers to shoot. After a while, I began concentrating on all that old metal equipment.

I had a chat with the cowboy, who was messing with the hardware on the flagpole. I mentioned how I’d scared the horses a bit but they seemed okay. He told me to fly right over them. He and I both knew that the best way to get a horse used to some unusual noise or activity was to subject them to it until they began ignoring it. I had no real desire to overfly the horses, but was glad he’d offered it as an option. That direction was one of two possible “escape routes” if my landing started going south and I needed to do a go-around.

Not wanting to wander too far away from the techs, I returned to the soda fountain, found a table on the far side of the room, took out my laptop, and began reviewing photos and writing this blog post. I’d come prepared for a long wait.

I should mention here that although the place is off the grid, when this client comes, they set up a multi-node network that includes broadband Internet access. So not only could I compose a blog post, but I could check Twitter and Facebook and email. This was a good thing because my cell phone signal was very weak and 3G wasn’t really an option.

The Flight

At 11:30, it looked as if we might actually have a flight before lunch. I headed out to the helicopter and was surprised when two men I’d never seen before approached and announced they’d be flying with me. The reason I was surprised was because I knew one of the techs was planning to fly with me so he could monitor the equipment during the flight on his laptop — that was the usual procedure. But with the camera up front, I only had two passenger seats open in back.

What followed was some minor confusion. The tech told me we’d run the first flight as a sort of dry run for the actual tests, which would be done after lunch. He told me to take the other two men. So I briefed them, loaded them on board, and strapped them in. Then I started up and, during my warm-up processed, pushed the appropriate buttons on the camera equipment sitting beside me. A while later, I lifted off in a cloud of dust, made a 180° turn, and departed down the road, pushing the cyclic forward to accelerate as quickly as possible to clear the dust.

My job was to keep maintain a line of sight with the SUV on the road below me and the main building back in town. My passengers would monitor internet connectivity in the helicopter — yes, we were set up as a WiFi hotspot.

The flight lasted about 15 minutes. The biggest challenge was flying slow enough that I didn’t blow past the SUV and need to keep circling. There was just enough wind coming into the back seat headset mics to force me to turn off the voice activated intercom.

I watched the SUV pull off the road and make a U-Turn. I circled slowly, 500 feet above them. Then my phone rang. It was the tech back at the base, calling me back. They were done with this first test.

I headed back, leaving the SUV behind and landed in my spot. The dust cloud really was outrageous. The wind was blowing at about five mph from behind me — yes, I made a tailwind landing — and the dust kept getting blown into the town area. It didn’t go as far as the cafe, but it did seem to go as far as the soda fountain. No one had complained, though. I think they liked having the helicopter closer, where it was quicker and easier to get to than my old landing zone.

I let my passengers get out while I was still shutting down. Then, since it was already after noon, I headed back to the cafe, where I knew Rosa would have one of her excellent lunches. I found a seat among the techs and one of the long table and soon had a barbecue beef sandwich, cole slaw, and chili in front of me. During lunch, we talked about helicopter and the cherry drying work I do in Washington in the summer. That led to other conversations about weird helicopter work and weird helicopter flights.

I was just finishing desert when my contact stepped into the cafe. She had her phone against her ear, but she was addressing everyone in the room when she said calmly, “You guys might want to move your cars. The hotel is on fire.”

The Fire

We all cleared out of the building and into the street out front. I was expecting to see a thin trail of smoke coming from the building. Instead, the top right of the three-story building was engulfed in flames at least 10 feet high. Guys started running toward it while I ran back into the cafe, not willing to see what was happening. Rosa was there, looking at me, and I told her what was happening. She ran out to look and I followed her.

It was the most amazing thing. The fire spread at the rate of about one room per minute, moving right to left across the top floor of the hotel and then down. The rental cars parked at the base of the building were smoldering; as I watched, the hood of one burst into flames. I could feel the heat of the fire from the end of the main building. Guys who had tried too late to retrieve belongings from their hotel rooms were turned back while a handful of other guys ran back toward us holding scattered possessions in their hands. Thick black smoke climbed into the sky. Huge sheets of the hotel’s metal roof lifted into the sky like aluminum foil.

The Fire
The hotel at Robson’s just minutes after the fire started.

And there was nothing we could do. There were no hoses, no water spigots. It was clear from the start that the hotel was a goner, but the intense heat began to spread the fire closer to us, into the wind. The dry wood frame of a nearby building caught fire. Then another on the other side of the hotel, right beside one of the caretaker homes.

Hotel Fire
In less than 15 minutes the whole building was on fire and the fire was spreading. The truck in this shot was lost; no one could get near it.

The local fire department showed up just as another row of buildings caught fire. They’d brought two tanker trucks filled with water. They drove up the street as far as they could and got to work. One firefighter came toward us and told us to clear out of town.

In the background, we could clearly hear the sound of the rental car fuel tanks exploding.

The firefighters concentrated their efforts on the buildings that could still be saved, mostly to prevent the spread of the fire. I think that if they’d arrived ten minutes later, the whole town would have been lost.

We gathered in a group near the entrance to the town while additional firefighting equipment rolled in. My client had already gone through their list of participants. No one was missing. One guy had been burned running from the fire after retrieving some of his belongings. He’d used his arm to shield his head from the heat and his arm had gotten what were probably second degree burns. No one else was injured.

We all realized that if the fire had broken out at night, people would have been killed. It just spread so quickly.

It was obvious that the event was over. They began making arrangements to leave. At least six cars had been lost; they’d need to carpool back to Wickenburg and Phoenix. They came out to the helicopter and pulled their equipment off. I put the doors back on and prepared to leave.

Back in town, the hotel had been reduced to a single floor of burning rubble. One of the tanker trucks rolled out of town, empty, while another one rolled in.

The Flight Home

I took off in one final cloud of dust. But rather than head right back to Wickenburg, I circled around the back of the townsite to see if the fire had spread into the desert. After all, the wind was blowing that way. I was very surprised to see several other wooden buildings quite a distance away from the hotel completely burned to the ground and still in flames, obviously ignited by sparks. I paused just long enough for the helicopter’s “nosecam” to get a shot, then banked away to the east and headed back to Wickenburg Airport.

Aerial Shot of Fire

The flight back was uneventful. I didn’t pay much attention to my surroundings. I was feeling stunned and saddened by the loss of the old hotel. I knew the original owner would be heartbroken when she found out.

I also knew that it was the end of an era out in Aguila. The hotel would not be rebuilt; without it there wasn’t much to attract the groups that the owners needed to make it financially feasible. My client would not likely return; it was too far away from the closest overnight accommodations in Wickenburg to be convenient. I might not ever work for them again.

It was a hell of a way to end a job.

A Desert Flying Gig: Day One

The first day of a gig for a regular client doesn’t go exactly as planned.

The initial request for nearly a week’s worth of work for a regular client came about two weeks ago. I checked my calendar; it was wide open. I penciled them in. Then I reminded my contact that I’d spent far more time waiting than flying during the last two jobs I’d done for them. I couldn’t keep the helicopter offline from other work for them unless I flew at least as many hours as I waited — or charged a waiting fee.

She got back to me the same day. It would be two days: just Tuesday and Thursday. And she’d get back to me with the exact times I would be needed so I could plan my days accordingly.

I felt good about that. I’d been flying for the client pretty steadily for about four years — perhaps four jobs a year. The work was unusual and rather challenging at times. A friend who filled in for me once when I wasn’t available said he’d never do it again. That may have been partly because it’s in a remote place out in the desert about 20 flying miles from my home in Wickenburg. My friend lives in Phoenix.

Of course, my helicopter doesn’t live in Wickenburg anymore either. It spends part of its life in the Phoenix area, 30 minutes away by air or an hour away by car. There isn’t enough business in Wickenburg to keep it there.

But this client doesn’t mind paying me to bring it up to them and I’m usually glad to get the work.

I got an update via email the next day. It outlined a schedule that would have me there from 8 AM to at least 3 PM on Monday through Thursday. I felt doubtful as I entered the times for each day on my calendar.

I brought the helicopter up to Wickenburg on Sunday. I’d topped off the tanks in Phoenix and they were still full enough that I wouldn’t need more fuel.

I parked it on one of the two west end helispots that had been painted at one end of the jet parking area at my request nearly ten years before. Back then, there were five helicopters operating regularly out of Wickenburg: a LifeNet medevac helicopter based at the airport, my little R22, and three Hughes 500 models owned by three guys who lived in town and had more money to burn than I did. Since then, LifeNet moved out of town, I’d graduated to an R44 and then moved the helicopter out of town, a Hughes 500C moved out of town, and a Hughes 500D was sold. With the addition of a little Schweitzer 300, there are only two helicopters left in town. I could tell you more about the slow death spiral of life in Wickenburg, but it really isn’t worth wasting words on.

Day 1

I was at the airport first thing Monday morning, untying the helicopter’s blades, doing a preflight, and getting ready to go. It had dropped into the high thirties overnight and was in the 40s at 7:15 AM. The sun had just come up about a half hour before. I could feel its warmth through the cockpit bubble as I settled into my seat and got ready to start the engine.

Six seconds of priming after a night out in the cold — that was my estimate. I gave it just that, then pushed the starter button, holding the mixture knob ready to push in. Seven would have been better, I realized as I coaxed it to life. The engine caught; I pushed the mixture to full rich; I turned on the switches for the clutch, strobe, and alternator; and I modulated the throttle to keep the engine RPM as close to 55% as I could while the tightening belts tried to drag the engine down. The blades started to spin. The belt squealing sound I’d grown accustomed to on every startup for the past seven years faded and ceased. I brought the throttle down a bit and the RPMs settled to just under 60%.

I turned on the radio and GPS. A twin had come in while I walked out to the helicopter; it was parked in front of the terminal building, effectively blocking any other aircraft that might want to come into the jet parking area. Probably just a drop off or pick up. I punched my destination waypoint into the GPS. The clutch light went out and I brought the RPMs up to 68% for warmup.

Warming up an R44 means waiting for all engine gauges to be in the green. Oil temperature can be a bit slow on a very cold day — the kind of day when the oil drips off the dipstick life taffy when you check it. It wasn’t that cold and the oil temperature was in the green quickly. That left the slow gauge: cylinder head temperature (CHT). The gauge was new; I’d replaced the old one after one too many flights with it sticking in the cold position longer than just a minute or so. As a Part 135 operator, everything on the helicopter has to be in full working order, so having a finicky gauge was not an option. It cost $466 for the gauge and labor to replace it. The new gauge indicated warmup a lot quicker than the old one ever did — even when new. On a cold day, it cuts 2 to 3 minutes off my warmup time.

Another twin — a sky something? — called turning downwind as I throttled up to 75% RPM, did a mag check and a needle split. All good. I checked the doors to make sure they were closed and loosened the friction on the controls while scanning the sky for the arrival. Then I got on the radio and made my call:

“Wickenburg traffic, helicopter Six-Three-Zero-Mike-Lima on the west end helipads departing to the west. Looking for the downwind traffic.”

I caught sight of him rather low as he spoke: “We’re abeam the approach end of runway Two-Three. There’s a Columbia about ten minutes behind us.”

“Zero-Mike-Lima has you in sight. Departing to the west.” I’d picked it up into a hover as I spoke and turned 90 degrees to scan for other traffic. Then I just pushed the cyclic forward and took off.

The twin called final a minute or so later. Then the Columbia came on the radio, 15 miles west. I reported just leaving the airport, westbound, and that I’d stay at or below 3,000 feet, which would put me no higher than 600 feet above the ground. If the Columbia was that low, I was probably the least of his problems.

The sun at my back, I aimed for a tilted mountain range I could see off in the distance. The flight was over very familiar ground. A few hills, a few cattle tanks, some cattle. A ranch outpost with a small dirt strip. No homes, no paved roads. The kind of land that shocks city dwellers the first time they see it. Especially when they realize how vast and empty it is.

The desert was flat for most of the way, reminiscent of the sea floor that it had once been. The ground was a light sand color, studded with creosote and mesquite bushes. In some places, thin winding channels had been cut into the desert floor by the movement of water after heavy rains; they looked like so many varicose veins scarring the landscape. I’d once overflown this area after the remnants of a hurricane had dumped eight inches of rain in a day; several inches of standing water had reflected sunlight back into the sky, mile after mile.

I kept about 400 feet above the ground for the first ten miles or so. There were power lines up ahead — tall towers with multiple strands of thick wires that were remarkably difficult to see sometimes. I didn’t like to fly low until I passed them. Once they were behind me, I dropped 200 feet, skirting over the desert at 110 knots. Here and there, a rock outcropping rose 50 feet or so off the sandy desert floor. Tall saguaro cacti threw long shadows in the early morning light.

Desert

Ahead, I saw my destination — a rag-tag group of weather-worn wooden buildings at the base of the tilted mountain. Completely off the grid, it had been built years ago on the site of an old mine as a mining museum.

Number 7The original owner was apparently obsessed with collecting old mining and farming equipment — I can’t imagine a larger collection anywhere else in the world. It’s mostly heavy metal stuff made of iron so thick that even the rust can’t hurt it. White numbered boards precariously attached to some of the more interesting items serve as reminders of the walking tour visitors were encouraged to take.

But there’s more than just old mining and farming equipment. There’s a row of buildings set up as an old western town with a wooden boardwalk. A cafe, “opera house,” print shop display, blacksmith display, and firehouse complete with circa 1950s firetruck makes up the downtown. There’s a chapel overlooking the desert and a huge, three-story hotel at the far end of town. The whole place is powered by solar cells and a diesel generator.

The place changed hands and is now leased to an outfit trying to run it as a western destination. Trouble is, no one wants to come there. Even with horses and a real cowboy, there’s not enough to attract even the most hardcore western enthusiast. They’d rather see the Grand Canyon or Sedona or stay in a Phoenix resort. The place mostly plays host to marriage encounters run by church groups in small cities throughout central Arizona.

And my client.

My client has connections to the owner and has been using the place as a headquarters for corporate retreats and product testing. They invite clients, they show off their products. And they ask me to come on out to help them test their products.

I won’t go into detail here. Let’s just say that they produce high-tech wireless networking equipment with a specific non-consumer application. They mount stuff in my helicopter and I take their techs flying while they study computer screens and read off packet information. Sometimes we do photo flights. Sometimes I give people rides.

I crossed the only paved road along the way and started slowing down when I was still a mile out. I didn’t bother checking the wind; I knew it was dead calm. I’d land in a dirt spot beside the mile and half dirt road that came in almost a straight line from the paved road to the “town.” It was about a quarter mile from the town’s gate and I knew I’d walk the distance several times over the next few days. I’d purposely worn comfortable walking shoes.

I still had too much speed as I came in for my final approach so I overshot it, dumping the collective and pulling back the cyclic to bleed off all that extra energy without dropping out of the sky. When I felt comfortable with my speed and angle of approach, I turned toward my spot. I knew dust would fly when I got close to the ground, but I also knew it wouldn’t be bad — yet. Only after several hours of ATVs and Tahoes driving on the dirt around the helicopter would the dust be loose enough to really start flying. Then the whirling dust on each takeoff and landing would take just a little bit more paint off my rotor blades. Before the end of the year, my main rotor blades would likely have to be repainted for the third time at a cost of roughly $1,500. It was something I wasn’t happy about; a cost of doing business off-airport, out in the desert.

I landed on the far north end of the landing zone, which I knew from experience was level. A small dust cloud rose and then descended as I touched down and reduced the throttle back to 68%. The nose of the helicopter pointed toward town; the tail pointed away, where it was less likely for people to be walking.

As the engine began cooling down, I made a note on my duty log sheet with the Hobbs meter time. It had taken 3/10 of an hour to get there — a mere 18 minutes. By car, it would have taken nearly 45 minutes.

A truck headed toward me from town. It was the cowboy who managed the place. He waved and kept going.

After two minutes, I cut the throttle to idle and flicked the clutch switch to disengage the belts. The blades started to slow. Thirty seconds later, I pulled the mixture and the engine died. I pulled off my headset and waited for the blades to stop on their own. No sense in using the rotor brake if I wasn’t in a hurry.

It was 7:40. I was 20 minutes early.

At Robson's

I grabbed my bag with my iPad and a few other things in it and made the first walk into town. By then, the temperature was already in the 60s and it felt good to be walking outdoors on such a fine morning.

I realized something was not quite right when I walked into the cafe, the usual base of operations. Normally, the place would be buzzing with my clients staff members and guests finishing up a buffet breakfast. But there were just two people seated at a table and I didn’t recognize either one. The woman who runs the place greeted me and told me “they” were making themselves breakfast because Rosa, the cook, wasn’t there until noon. I peeked into the kitchen and saw four people from my client’s company gathered around the big commercial stove. I smelled bacon.

I made myself some instant oatmeal and grabbed a glass of orange juice. After a while, the four men came out of the kitchen with hearty breakfasts in hand. They settled down at the table beside mine and started to talk.

I waited for a break in the conversation. “Is it just you four?” I asked.

“Yeah,” one of them said. “I’m surprised to see you here. Did you fly out?”

“Yes. They told me you’d need me at eight o’clock.”

The four men exchanged glances. “We’re not flying today,” the guy who’d originally spoke said. “We’re just here for setup. They know the routine. We fly out on Sunday night and set up the network on Monday morning. Everyone else arrives later today. We’ll fly tomorrow.”

Somehow, I wasn’t surprised that someone had screwed up.

“I’m sorry you came out here for nothing,” he said.

I shrugged. “I just did what I was told,” I said. “It’ll be on my bill.”

We all had a good laugh over that.

I finished my breakfast, bussed my plate, and said goodbye. Then I made the long walk back to the helicopter.

Flying back into the sun, I had to put on my baseball cap to keep the sun flickering through the main rotor blades from being a serious annoyance. This time, after crossing the power lines, I dropped down and joined up with the railroad track that runs between Wickenburg and Aguila. I followed it, low-level, reminding myself again and again that at 110 knots, I didn’t need to worry about a train coming up behind me. Two miles short of the airport, I pulled up away from the tracks, made my radio call, and crossed the hills separating the railroad from the airport. I crossed the runway low level and landed at the fuel pumps to top off my tanks before putting it away for the day.

At least I hadn’t spent the day waiting.

more to come….

An Objective Comparison of Ebook Distributors

What I’ve noted so far.

I published, through Flying M Productions, my first ebook in October 2011 and have since published two others. (Learn about all of these titles here.) I went mainstream on all of the ebook distributions, choosing Amazon Kindle (custom mobi), Apple iBookstore (epub), and Barnes & Noble NOOK (epub). With about five months of sales and reseller experience, I thought it was about time to share my observations of these three platforms.

For each criteria, I provided a grade and notes to back it up. Remember, this is based on my experience with just these three books. For the iBookstore, I do not include my experience with iBooks Author-generated books in the table; that’s discussed briefly at the end of this post.

CriteriaKindle StoreiBookstoreNOOK Store
Ease of PublishingA
It’s very easy to get into the Kindle Direct Publishing program and publish books.
C
Apple’s iTunes Connect program requires a lot of paperwork and acceptance of agreements that are often updated. Its interface for publishing is surprisingly unintuitive (for Apple). It requires a unique ISBN for every book sold.
B
Getting into the B&N Pubit program is relatively easy, although there is an approval process that takes some time. Its online book submission process is easy.
Publisher SupportD
Publisher support is nearly non-existent. It’s difficult to send questions. Most questions are answered with a “canned” response. Often, I’m told my question needs more research, but an answer never comes.
D
Publisher support is handled primarily through a menu-driven help system that’s poorly designed. It can take more than a week to get an question answered and it’s usually with a “canned” response.
n/a
I have no experience with B&N’s support system.
Ease of Creating Acceptable DocumentsB
I convert from epub to Kindle using the Kindle Previewer app. This usually goes smoothly the first time around, but it does require that conversion.
C
Apple is extremely particular about formatting and unusual characters in ebook files. For example, it doesn’t like uppercase filename extensions or spaces in file names. This often requires a lot of digging around in epub format files to fix problems. To be fair, I could probably improve my templates to prevent some of the problems I encounter.
B
BN.com accepts just about any epub I send, as long as it isn’t any larger than 20 MB (which I think is too restrictive.)
Appearance of EbookC
The Kindle format inconsistently formats bulleted lists and font sizes and completely ignores some formatting. As a result, my books are not usually formatted as I’d like to see them.
A
My iBookstore books usually look very good. Apple is true to all epub formatting.
B
My NOOK books usually look very good, although I sometimes notice instances where formatting is ignored.
Speed of Review ProcessA
Amazon consistently makes my books available for sale within 24 hours of posting.
D
There is no consistency in the speed of Apple’s review process. I had one book appear within an hour of posting while I waited a week or more for others.
B
B&N consistently makes my books available for sale within 48 hours of posting.
SalesA
In most instances, Amazon sells the most books.
B
Apple sells reasonably well — unless a book has an unusual amount of appeal to Mac users, in which case, it sells best.
D
B&N’s sales are sluggish and rather disappointing.
RoyaltiesD
Amazon offers the worst publishing deal. To get 70% royalties, you must price the book between $2.99 and $9.99. The 70% commission rate is only available for books sold to certain countries. All sales to other countries earn just 35%.You must also pay “delivery fee” based on the size of your book file for all books sold at the 70% commission rate. Amazon enforces price matching, so if your book is available for a lower price elsewhere, Amazon will arbitrarily lower the price of your book in the Kindle Store. And don’t even think of getting into the KDP Select Program; that’s something else I need to blog about soon.
A
Apple offers the best publishing deal: 70% flat rate on all books. No hidden costs, no exceptions to the 70% rate.
A
B&N also offers a good publishing deal: 70% flat rate on all books.
Sales & Royalty ReportingC
Amazon’s reporting system is inconsistent and confusing, although it does have up-to-the-minute sales figures. Amazon’s staff does not reply promptly (or at all) to sales/royalty report questions. Reports seem to indicate book sales at unauthorized prices, making me wonder whether Amazon is ripping me off.
A
Apple’s reporting system is updated daily. Reports can be viewed its iTunes Connect website as well as in an extremely well designed iOS app.
B
B&N’s reporting system is minimal but accurate.
Final GradeB
The only reason Amazon gets such a good grade is because it sells a lot of books. Its royalty structure sucks, but I can still earn more there for most titles than anywhere else.
B
Apple’s fair royalty rate and reporting help it score well, but its disappointing sales figures and inconsistent review process keep it from getting a better grade.
C
B&N is a nice platform, but low sales keep it from getting a better grade. In all honesty, if it weren’t for the fact that publishing there was so easy, I probably would’t bother.

Of course, it remains to be seen how well my iBooks 2 interactive (enhanced) books do on the iBookstore, since Apple is taking so damn long to approve them.

Do you have any experience with any of these publishing platforms? If so, what have you observed? Share your thoughts in the Comments for this post.

The iBooks Author Gamble

Taking a chance and not liking what I see so far.

iBooks IconIn late February and early March, I spent about 2 weeks porting my existing 242-page iBooks Author book to iBooks Author software for publication as an iBooks 2-compatible interactive (or “enhanced”) ebook.

Moving over the text wasn’t a huge deal — mostly copy and paste, followed by the application of styles I’d created or modified for my custom iBooks Author template. But rather than simply copy and paste the 100+ screenshots that are part of the print, epub, and Kindle format books, I decided to rely on videos to tell the story. So I spent most of that time recording a total of 3 hours of original video content based on the numbered step-by-step instructions in the book. I also used the Gallery widget and created an illustrated Glossary.

The final book turned out to be 150 pages and 1.3 GB in size. And it looked awesome (if I do say so myself) — the perfect example of how a iBooks Author could be used to create how-to content.

The Waiting Begins

Final Count
It took 55 days for this book to be approved by Apple.

I submitted the files to Apple via iTunes Connect on Sunday and began waiting for approval.

Monday, Tuesday, Wednesday, Thursday — I spent the week waiting. It’s now Friday and I’m still waiting.

In iTunes Connect, the book’s status remains:

Book In Review. This book is currently being reviewed for quality assurance.

A New Week brings New Developments

Final Count
It took 75 days for this book to be approved by Apple.

I’d already committed to converting my Making Movies book to iBooks Author format. Because the video for that book already existed — I used video clips taken from the example movie — the creation process was much quicker. I figure I put a total of 10 hours into the conversion process. I submitted it today.

And that’s when I discovered two things:

  • Apple no longer allows submissions of books created with iBooks Author 1.0 (or 1.0.1). It requires the latest version, released the other day, iBooks Author 1.1, which includes support for the new iPad. My iBooks Author book was created with the previous version. Is that what’s holding up approval?
  • A warning appeared on screen when I attempted to upload my 233 MB book, telling me that Apple recommends that books be no larger than 200 MB because some users might have trouble downloading a larger book file. My iBooks Author book was considerably larger than this. Is that what’s holding up approval?

Of course, there’s no way of knowing. Apple’s iTunes Connect/iBookstore support is absolutely dismal. If you ask a question, you’re lucky to get a response in less than a week — if you get any response at all. And that response is likely to be “canned” — in other words, boilerplate text possibly chosen at random by the support person who handled your request.

Rejection Could Be Painful

And nagging away at the back of my mind is a blog post by Seth Godin where he reported that his book had been rejected from the iBookstore because it contained links to printed books on Amazon.com.

While my book doesn’t contain any offensive links — at least I don’t think it does — what if Apple decides to reject it because it’s too big? In the wrong format? They don’t like my videos?

All I can think of is the hours and hours of work I put into that edition, possibly wasted on the whim of some reviewer at Apple.

Apple Needs to Get Serious

Today I read a blog post on TUAW about the antitrust lawsuit the U.S. Department of Justice is apparently mounting against Apple. In it was this line:

Apple says that it wants to sell as many ebooks as possible, which is totally believable since the company is still a relative bit player in the ebook market.

From where I sit, I don’t see Apple being very serious about this at all. If Apple were serious, it would have a much better process in place to review and approve iBookstore submissions. After all, you can’t “sell as many ebooks as possible” if dozens or hundreds of them are stalled in the approval process day after day for a week or more. It wouldn’t be rejecting ebooks because it doesn’t like the links they include. And it certainly wouldn’t generate frustration and dissatisfaction among content creators — the people actually creating the books they supposedly want to sell.

Call Me an Idiot

I’ll beat a few of you to the punchline by admitting that I look like an idiot.

Back in January, when everyone was voicing outrage over the iBooks Author EULA, I wrote a blog post that told people they were basically worrying about nothing. In response to concerns about the approval process, I said:

I see Apple’s approval process as a GOOD thing. Right now, there’s nothing stopping anyone from publishing any crap they want as an ebook and distributing through services like Amazon Kindle. This is a far cry from publishing as we’ve known it, where only authors and works approved and edited by an experienced, professional publishing company team would be published. Apple’s review process helps weed out the crap and make its library of content more valuable to iBookstore shoppers. While some folks might be fearful that Apple will not approve their work, I’m not — and you shouldn’t be either. People who can turn out quality work should have nothing to worry about as far as the approval process goes.

Now there is some concern over Apple using this power to censor content. For example, perhaps they refuse to publish a book that says negative things about Apple or its founders. (Remember how they pulled all of a certain publisher’s books out of the Apple Store after they published an unflattering biography of Steve Jobs some years back?) I’m not terribly worried about that, but I do admit that it is a possibility. Obviously, if there are documented examples of Apple not approving something that should be approved, I’d be willing to revisit this point. For now, however, I don’t think it’s an issue.

Yes, I’m an idiot.

I didn’t realize that Apple’s approval process had the potential to be slow and unfair.

I naively assumed that Apple was concerned with quality — after all, isn’t that what’s holding up my book: a quality review? And quality didn’t worry me because I know I can create quality work.

But what if it’s some other criteria that Apple’s reviewers are concerned with? Something other than links to Amazon.com? File size, file format. Or, worse yet, something I can’t fix? And how will I know? When will I know?

Every day that book isn’t in the iBookstore is a day that I — and my partner, Apple — don’t sell any copies.

What to Do?

What’s the right answer? The right approach?

Well, I can tell you one thing for sure: I’m not going to waste another second of my time assembling yet another title in iBooks Author and submitting it to the void via iTunes Connect.

Instead, I’ll wait — as if I have any other option — and see approach. And I’ll use this experience to guide me for future submissions created with iBooks Author.

Got any iBook Author/iBookstore stories you want to share? Comment on this post.

March 19. 2012 Update: It has now been more than two weeks since I submitted my first iBooks Author-created book for approval to the iBookstore. I am still waiting for approval. This is not a good sign, folks. If you’ve already gone through the approval process, please take a moment to tell us how long it took. And if you’re waiting, please let us know how long you’ve been waiting. I’ll update this when (or if?) my book is approved.

March 28, 2012 Update: I finally heard from Apple about the first book I submitted. It had a number of trademark-related issues that needed to be resolved. I wrote about them here.

May 1, 2012 Update: While I was traveling, my iBooks Author book was finally approved. I believe the final count of days until approval was about 55. I removed the count up timer. My Making Movies book has still not been approved. I feel completely idiotic that I actually believed my books would be reviewed within a week.

May 23, 2012 Update: My Making Movies book was finally approved. I believe the final count of days until approved was 75. The last 3 weeks was spent nagging Apple to explain why it was holding back the book for metadata issues without putting a “ticket” on it.