Category Archives: Infinity Softworks

Writings on running Infinity Softworks. Lessons learned from over a decade of history.

My appearance on the Release Notes podcast

Posted on by

I was interviewed by the good folks over at Release Notes the past two weeks. In part 1 I talk about the how mobile was in the early days, how we marketed and sold applications, and our complicated relationship with Palm. Click here to listen to the first part (~37 minutes).

In the second part, I talk about the future, about the transition we have undergone as the mobile market has changed and expanded, and what drove us to reinvent powerOne. Click here to listen to the second part.

It was an honor to be on the podcast. A special thanks to Charles and Joe for having me.

Holding My Breath

Posted on by

We are so close to launching Equals now. Earlier this week I thought we’d be inviting a few people to try it out this week. And then Tuesday happened.

We finally got everything pushed up to the server, code that had been working perfectly for the last week or two on my Mac. Honestly, it was amazing! In five-six days worth of testing I only found a handful of issues, most of which were really small issues that were fixed in a day or two. There was no crashing at all.

Keep in mind this was a far cry from the prototype we worked on last winter. That prototype crashed constantly and the bugs were nasty. Rick spent three months tracking down and fixing four crashing bugs, all of which were non-repeatable and all of which were crashing on some systems and not others. To make matters worse, it always seemed to crash on the platforms where we couldn’t step through the code with a debugger. So when we ran the engine on our Macs and nothing crashed and things worked, we were both celebrating!

So we pushed to the server on Tuesday and the first thing I did, the first calculation I ran, crashed the server! The first thing!

I held my breath.

A little bit of panic set in. A little bit of depression, too.

We had clearly hit the high point on our rollercoaster called launch and was turning the corner to plummet back down into the pits. I hate this ride. Maybe it’s time to walk away. Maybe this is a sign from the gods that it isn’t meant to be.

Luckily I wasn’t in charge of finding and fixing the bug. So we sent off some feelers to the hosting company to see if there was a server issue we needed to know about and get some pointers on how to debug the issue. Wednesday night Rick narrowed the bug down to a third-party library we are using in the engine and Thursday night he found and fixed the problem. Meanwhile, I was tasked with “doing other things.”

I woke up this morning to a fixed and running engine, and suddenly the rollercoaster is going back up hill again and all is right with the world and we might be able to invite some people to try it out today anyway.

I’m breathing again.

Trials and Upgrades Won’t Save Independent Software Developers

Posted on by

Every six months or so a new round of discussions about how Apple is killing independent developers arises. Many argue that Apple has hurt independent developers by not allowing upgrade pricing and free trials. The belief is that this would help indie devs make a living because free trials raise prices and upgrades allow for an on-going revenue stream, one that pays for developers to continue improving their software.

Lately, this has become the latest thinking for why the iPad is not doing well. The thinking goes that there is little incentive for independent developers to write world-changing applications for iPad because there is just no money to be made, and without those world-changing applications the iPad languishes with few reasons to purchase. After all it is neither an iPhone nor a laptop, sitting somewhere in between without a truly compelling reason to purchase a new one every year. After all, I can consume content (news, movies, tv shows, etc.) on a three-year-old iPad almost as well as I can a current one.

I’ve long argued that, while Infinity Softworks has as good a reason to support trials and upgrades as anyone, it won’t make a difference to the independent developer today. It’s too little, too late. If there had been trials and upgrades in 2008 or 2009 maybe it would have made a difference (I’m still skeptical), but not today. It’s a matter of expectation and the realities of numbers.

Expectations

Customers are trained just like anyone else and the baseline becomes the expectation. Here in the United States we expect lights to go on whenever we turn on a lamp. When the electricity goes out it makes major news. Remember the blackouts in California just a few years ago? Yeah, that was huge news. People were frustrated and lots of ink was spilled (can we say that anymore?) talking about how this will be the future, rolling blackouts and other electrical grid problems caused by climate change and an increasing population.

Our expectation here in the States is that the electricity is available whenever we need it. That is not the case in other countries. We worked with a company in India a few years ago. It was often we had to postpone a meeting or adjust our schedule to accommodate their electrical situation. While it left us wondering, none of the developers in India blinked. Their expectation was that electricity was intermittent. Use it while you’ve got it, save and backup often.

Already in 2008, when the iPhone launched, the landscape for software was changing. More and more companies were becoming successful with web services, which necessitated subscriptions and advertising. There were fewer and fewer success stories of packaged goods, one-time priced products. Apple walked into the middle of this with the iPhone and shortly thereafter so did Google.

The expectation die was already cast, however. When the iPhone launched, apps were priced with a virtual ceiling of $10. That was the price of the first game and many of the first applications. A few years later Apple launched their Office-suite of apps (Pages, Numbers, Keynote) at $10 per app and then free. In customer’s minds, a very polished, professional application from a well-known developer for an iPhone or iPad was $10 at most. From anyone else that premium price was $5. Sure there were a few niches where the developer could still get more but those were far and few between. The expectation was that apps were somewhere between free and $5. In 2009 we experimented, raising the price of our top 5 finance app from $5 to $10. Our sales completely disappeared.

That expectation, for iOS and Android, has lived on now for eight years, cementing itself in the mind’s of app buyers. It is unlikely that would change with trials and upgrade pricing, especially when most categories readily have at least a half dozen alternative applications to choose from.

The Role of Scarcity

In 1998 we launched our first application for PalmPilot, a financial calculator called FCPlus (later renamed to powerOne Finance). We charged $39.99 for the application in those days, a high but not outlandish price for a handheld software title in the late ’90s. Average prices for Palm software was $10-20 per title. We priced at $39.99 because our only competitor, Landware’s Financial Consultant, was the same price.

Read that again: our ONLY competitor. There were not ten alternatives. The expectation was that a good software financial calculator for Palm OS would run a buyer $40 (or more). But even $40 was cheap by desktop software standards. Other products in the Windows calculation space were hundreds of dollars and even hardware calculators cost more.

We can’t say the same today. There are no less than 20 alternative financial calculators in the iOS App Store. While demand expectation of low prices remain, the plethora of undifferentiated competition puts pricing pressure on the supply side of this equation as well. And let’s face it: it is nearly impossible to differentiate when you have only a few screenshots, a description (that no one reads) and a few reviews to go on.

Software’s Changing Face

In the late 90s/early 2000s I had a theory that the price of software for mobile would remain at about 10% of the price of desktop software titles. After all the price of mobile hardware was about 1/10th the price of desktop computers and the screen real estate was about 10% of a typical monitor. Again, expectations, this one dictated by its relativism to other computing systems.

A typical Windows application was somewhere between $100 and $400. A typical Palm or Pocket PC title was $10-$40, right about 10%. The price of a desktop computer was $2000-$4000 while the price of a PalmPilot, by 2001 or so, was $100-$400, or roughly 10%.

Soon thereafter, though, laptop and desktop prices fell. Now a high-end, high-quality laptop can be had for $1500 with Windows laptops as low as $500. And software prices have fallen alongside. Apple used to charge $100 for its desktop Office suite, which became $20 per title then free. A $400 Microsoft Office suite became $80.

It isn’t stopping there, though. In 1998 when I wanted to understand the software business I looked to Microsoft, Adobe and Intuit. Each sold their software one-time with upgrades. Now, not so much. All three are moving to subscriptions and Intuit just announced it is trying to sell all their products that don’t have subscription pricing.

The Financial Reality

My problem is not that it hurts to try trials and upgrades, my problem is that there is too much hope in a solution that won’t pay off. The reality is that smartphone and tablet software pricing is so low that even trials won’t help us. If a premium application is $5 today, what do trials buy us? If we can raise the price at all (too many substitutes as discussed above), can we raise the price to $10? How about $20? A typical paid app in the store will generate a few thousand downloads over the course of a year. In the financial category, 10 units per day is able to keep you in the top 50 paid apps in the category, which is not an easy task to accomplish these days. That’s the equivalent of 3650 units per year. We’ll use 5000, a 33% premium, instead to make the math easier:

  • 5000 units × $5 – 30% = $17,500
  • 5000 units  × $10 – 30% = $35,000
  • 5000 units  × $20 – 30% = $70,000

Even the $20 price is definitely not enough to support even a single developer in most of this country. But what about adding upgrades? From my days selling one-time with upgrade products on platforms that supported it, I know that roughly 10% of the customer base would upgrade to the next release:

  • 5000 units  × 10%  × $5 – 30% = $1,750
  • 5000 units  × 10%  × $10 – 30% = $3,500
  • 5000 units  × 10%  × $20 – 30% = $7,000

So year 1 is $70,000 gross, year 2 is $77,000 gross. And that’s gross revenue! None of the expenses of running a business are taken out yet. While these might be great hobbyist revenues, they still don’t mean enough money to inspire a team of people to write incredible software that changes how people use iPads.

To make a full-time, independent software business work in the United States, I estimate (based on experience) that we need to generate roughly $150,000 per year per employee before expenses. Adding trials and upgrades, frankly, aren’t going to get us there.

Duck and Weave

I surmise that the business of being an independent developer is much like the job of an NFL running back. The backs job is to find the holes left by the 400 pound lineman and charge through them.

As mentioned in 1998 we launched our first Palm title: FCPlus financial calculator. A year later Palm came to us and basically told us to give them a financial calculator free or they’d go get one from our only competitor. Microsoft at that same time had launched PocketPC and included a financial calculator. Palm needed one, too¹.

We really had no choice. Relying on the fact that Palm just wanted to check a box that said “includes free financial calculator” we created a Lite version of FCPlus, gave it to Palm to bundle and then sold upgrades to the full Pro version for $19.99. (Remember, the full price was $39.99). These bundling deals worked quite well for us, actually, and we eventually developed a product specifically for bundling (powerOne Personal), which was included, at its peak, with nearly 80% of all handhelds sold. The traffic derived from those bundles accounted for 75% of our revenue.

The 400 pound lineman created a hole and we, the 200 pound running back, had to find a way to charge through.

On To The Future

The business of software keeps changing. We need to change with it. As much as we all think it will solve our problems, yearning for a world that has passed us by won’t help. Trials and upgrade pricing are from an era gone-by. They aren’t coming back and, if it did, it wouldn’t have the financial impact we all wish it would.

If we want to thrive, let alone survive, we are going to have to change with the industry. Again, I look to Microsoft, Adobe and Intuit. Their future is clearly subscriptions. Is that our future too?

—

¹ Yes, the company was that horribly run after Donna, Jeff and Ed left to form Handspring.

Introducing DEWALT Mobile Pro for Android

Posted on by

I am proud to announce that we shipped DEWALT Mobile Pro for Android last week. It is available from both Google Play and Kindle Appstore.

While the basics are the same, a wonderful scientific and unit calculator, a few free templates and a number of additional packs that can be purchased in app, the Android version has been completely re-written from scratch using some of the technology we’ve developed for Equals. The app itself is much cleaner and, hopefully, much simpler to use.

If you are interested in where we are taking our products, you might want to take a look. Even if you don’t have an Android or Kindle device, there are multiple screenshots available to review. And if you do have an Android or Kindle device, please download the app and give it a nice review!

“Mobile First Cloud First”

Posted on by

Ben Thompson’s Mobile First post is an interesting read and his perspective is always fascinating. (I pay $100 per year to be a member. I can’t recommend it enough.) It’s not the post itself that has me thinking, though, specifically, it’s footnote #4:

Microsoft’s “Mobile First Cloud First” strategy makes much more sense now, no?

Here’s the thought: can you really be mobile first without being cloud first? Mobile first means everything you do is different because people have a computer in their pockets all the time. (And by people, I mean all people on the planet in the next few years.) What enables mobile first, though, is that every one of these devices is connected to the cloud, and its the cloud that lets us connect outside the device.

So can you have one without the other?

I think a lot of us indie developers have tried for years to be mobile first without being cloud first, and I think that is part of the reason it has been so hard to make a living. Infinity Softworks is a perfect example of that. It came to be in the mobile era. I wrote my first apps for PalmPilot and later Windows Mobile, and we have made the bulk of our revenues over 18 years from selling apps for mobile devices.

The first generation of our products were fixed. It had a certain number of bundled calculations and that was it. But that was okay. The devices were underpowered and completely disconnected from the Internet.

The second generation of our products had some bundled calculations but also allowed customers to write they own. They were still on disconnected devices, though. Yes, you could email a file but that is a far cry from being Cloud First. Again the devices were largely disconnected though, at least they were until 2007 when we wrote a BlackBerry version, and then 2008 when we could write for iPhone. Over the past few years, though, those connections have only gotten better and more pervasive. Our apps have not.

Even to this day powerOne is primarily a stand-alone application that has very minimal connection to the outside world. The only cloud connection it has at all, besides emailing results and formulas, is an in app library of calculations you can download from, but even that is buried at the bottom of the home screen in a tiny button. It’s hardly front and center in the product.

These first two generations were Mobile First, but neither one was Cloud First. Over time, as the devices have gotten better and faster connections, our revenues from powerOne have waned. I’m thinking there’s a connection.

A few years ago we set to work on the third generation of our products (a little at a time). We started out writing mobile apps but about a year ago we switched and started developing the web version first. While I didn’t have words for it at the time I sensed that the cloud was important to making a sustainable product and that by developing a web version first it would help us shift our mental framework.

Now we think in terms of systems rather than mobile apps. For the first time I believe we are thinking Mobile First Cloud First, and I believe it will have a huge impact on our fortunes.