BlackBerry Alliance Program An Insult To Developers

RIM rolled out their new Alliance Partnership program this week and it’s just another sign, to me anyway, that RIM is missing the boat. Before I could write my own blog post, though, Ronen Halevy over at BerryReview.com wrote everything I was thinking (here and here).

Here it is in short: RIM’s historical focus on enterprises has caused short-sightedness on the part of consumer efforts (and by consumers I’m referring to everyone not in Fortune 2000 companies and government). Instead of developing the software to cater to consumers, it seems, they completely defer any consumer relationship to the carriers and hope for the best. The examples are everywhere:

  • Why do OS updates come from the carrier instead of RIM, and why do we have to go find them rather than those updates being pushed to us?
  • Why isn’t BlackBerry’s App World pre-installed on devices and why doesn’t this service work over wifi on the devices that support it?
  • Why do enterprises get RIM’s impressive BES software for syncing with mail, contacts and calendars but consumers get the poorly created and implemented BIS implementation which doesn’t even support push email?

And now we have the new Alliance Program, as if the old one wasn’t bad enough. The old program was pay $2,000 per year to get pre-release software, a couple of devices, a cheap BES system, and access to the BIS-B wireless sync protocols. It also included tech support with your own technical guru.

For two grand, I thought we would get marketing, too, but every time RIM had a chance to help us out, they passed on the opportunity.

Now comes the new program. For the price of $2,000 plus thousands more to buy 45 participation points, we get the same benefits we had before. So the price is higher and we have to jump through more hoops than writing a check. We get points by getting people to buy BlackBerry’s, sending company reps to RIM’s dev conferences, and writing case studies.

Personally, I’m insulted. This program isn’t about us, the developer and what we can bring to RIM and how RIM can help us be more successful. It’s about what RIM can get out of us. Instead of rolling out a program that gives us better placement on the web site, elevates our standing in the App World Store, and helps us promote to the vertical markets that buy our software, we get no additional benefit for more cost.

To me, it’s just another shining example of how focused on enterprise RIM really is. The $2,000 badge of honor from RIM and access to technical support means something to enterprise developers. For consumer markets, it’s no help.

I really hope RIM gets their act together. They really have developed amazing devices for those who care more about communication than infotainment. And given their dominance in enterprises and government, they have a great opportunity to win the prosumer markets that a product like FastFigures is focused on.

A Weekend Without the Internet

My wife’s father and aunt grew up in Northeast California, almost at the Nevada border. It’s high desert country, lots of cattle and farming. The largest town in the area, Alturis, has a population of 3000. The nearest McDonald’s is in Klamath Falls or Susanville, each one and a half or two hours away.

We drive down every year over the Labor Day weekend. My wife, her brother and her aunt still own some property in a private area there and over that weekend is the property owners meeting. It’s a very pretty area. We saw deer running down Main Street. Lots of birds and pine trees.

But what we didn’t have was an Internet connection. My cell phone had EDGE network access, so I kept up to speed on the rest of the world, but I couldn’t get my laptop to connect to the motel’s wifi.

I intended to get some work done while we were there but almost everything I do depends on the web now. I write apps for the web, I write documents and do spreadsheets on the web. I’m used to being able to do a search when I need to, check email, Tweet and read news.

I did plan ahead, just in case, bringing a business book to read. At least in my work life, I’m really dependent on the Internet. Back home in Portland, Oregon, I never have a problem. I have some connection the entire time. But in the country it’s a different matter entirely.

Oh well. It’s good to check out occasionally.

A New Perspective on Fund Raising

Starting a company is a giant science experiment. We develop a series of hypotheses and test them in as controlled a way as possible, making changes to the hypotheses as we go.

Generally, those hypotheses fall under a number of basic categories:

  • Product X solves ______ problem.
  • Product X has ________ customers.
  • Product X will make money by ______.
  • and so on.

If a company is successful in answering these questions, they tend to grow big. And those that can’t answer the basic ones don’t grow at all (or very little).

In the 12+ years I’ve run Infinity Softworks, I’ve observed more than a few stupid ideas get a ridiculous amount of money. I thought large amounts of funding at an early stage of a company’s life — even $500,000-$2 million — was the wrong approach. Too many companies spent beyond their means or used it to grow a business before they knew what business they were in.

But I now believe I was wrong. Early stage funding is not intended to grow the business; it’s intended to answer the hypotheses. And by focusing on answering the hypotheses, it positions the company for growth.

So how much money does a company need? The answer is enough money to run the hypotheses and prove that there’s a business that deserves more funding (or can grow from revenues). I underfunded Infinity Softworks with our latest endeavor with web, iPhone and FastFigures, and put ourselves in an interesting position as our first hypotheses proved false.

This leads to obvious second question: where does the money come from? Is it internally funded or does a company raise capital from angels and VCs and others? That answer is it depends. I have a good friend who runs Creative Algorithms, a husband and wife team creating apps for smartphones. They’re able to run their hypotheses out of their own pocket and, given the size of the business they are trying to grow, it wouldn’t make sense to raise funds. I, on the other hand, raised funds. The size of the experiments — coupled with the business potential — required it.

The New Business Model Axiom

I believe strongly that the web — and the traditional PC and mobile app businesses that it touches — is going through an evolutionary process. Many of the old business rules are broken — things like how to market, how to charge, the value-price relationship (more expensive means more value). Ten years ago we could make a connection and say “such-and-such a product was marketed and sold this way so we will have success by doing the same.” But now that is no longer true. Everyone’s trying to figure out these new rules from scratch.

As we move FastFigures forward, soon overtaking the core capabilities we offered in our powerOne applications and then turning our attention to the new and exciting features we have planned, this disparity between the way we used to do it and the way to do it now are hitting home.

So I asked for help. And Albert Wenger at Union Square Ventures was kind enough to provide some clarity. My first question was regarding the so-called freemium model, where some features are available for free and some features cost money, and where to draw the line between the two. I was also struggling between companies that seem to go without charging customers and some that charge right away. Albert gave me excellent advice:

As a general rule I would say if your business has a network effect, i.e. more users make the service more valuable to each user, then you should worry primarily about adoption and about pricing later.  If that’s not the case then you want to get pricing in place right away.  It is best to charge for those features that will discriminate between business users who can charge to a business credit card and everyone else.

This is simple and straight-forward, dare I say an axiom for the internet age. If there are two customers — consumer and business — then businesses will pay subscriptions and consumers won’t. So the portion of the service that attracts consumers should be free for them to use and (potentially) monetized some other way, whether that’s advertising or virtual land or  transaction fees or something else.

I find this enlightening. It encapsulates so many of the web businesses I see more succinctly than I have ever seen it before. Thanks, Albert!

Palm Pre, FastFigures and powerOne

I have had a steady drip of requests since the Palm Pre launched for a webOS version of our software. I wanted to take the opportunity to talk about the platform, what I think Palm is doing right and wrong, and relate that to our own software products FastFigures and powerOne.

First, let me say that I like what Palm is doing with the Pre from a developer perspective except one major flaw. A year ago I wrote a post on the recipe for beating Apple and highlighted three things that the company needed to do. Palm has nailed two of the three:

  1. Build a beautiful, touchscreen device.
  2. Make it synchronize with web-based applications.
  3. Focus on offline use of web-based applications.

Palm is flubbing #3.

Palm has built their platform so that all applications are written in CSS (the page style), HTML (the content) and Javascript (the interactivity), the core languages of the web. But these three languages are intended to handle the user interface, or client, side of the equation.

What’s missing — and what Palm insists it doesn’t need — is the underlying technology that handles the business-side of web applications. Developers use a multitude of server-side technologies to do this, including Ruby on Rails, PHP, .net, and Python. Most mobile platforms use either C or Java to handle the business logic.

Palm insists it doesn’t need anything. And this is a major mistake.

Our software requires the business language to run the engine that performs all the calculations. Javascript won’t do primarily because of security and speed issues. In addition, insisting on using Javascript for business logic flies in the face of everything I learned about how to do web development.

Palm’s perspective is that applications that need business logic should interface with the web, such as Google’s search engine. Except an application like ours works best when the calculation is resident on the device, not because the calculations are better but because our customers don’t trust the Internet connection with their devices. There are just too many holes.

So what do our customers do when it comes to the Pre? They can either use the Classic emulator, which we don’t officially support but seems to run our software without a problem according to customers who have tried it, or use the web-based version of FastFigures at http://www.fastfigures.com/mobile. Either way, if you want our products on Pre, please drop us an email so we know.

And hopefully in the future, Palm will realize their mistake and give us a business logic language to work with. For now, though, I won’t hold my breath.