
I posted the first beta version of PocketBible for our beta testers this afternoon. Hopefully it’s raining somewhere over this Memorial Day weekend so a few of them will get some testing done.
We don’t anticipate this to be a lengthy beta. We’re planning to ship with a short to-do list of features we’ll add in version 1.1 and 1.2 (and beyond). The important thing is to get the application out the door.
We’re currently planning to let you download PocketBible from the App Store at no charge. It will come with the KJV and the ability to create a download account at our site that will let you download all our free resources (ASV, DNT, YLT, etc. Bibles plus several commentaries and devotionals). And of course if you already have a download account at our site you’ll be able to download any existing titles you already own, even if you bought them for a different platform. So the cross-grade charge should be $0. We’re hoping you’ll be so thrilled with the price that you’ll buy more Bibles and reference books to help pay for the cost of development.
I hope to be able to post some quotes from the testers and some indication of our progress over the next few days as we prepare to submit the app to Apple for approval. Then we wait while they give it the once over. We’ll be letting everyone know by email and here at the blog when we see it at the App Store.
Thanks for your patience, and especially thanks to those of you who volunteered but who we had to turn away due to limits on the size of our beta testing group. We think you’re going to be pleased with the results.
Yahoo Pulls the Plug on Mobile Development for Platforms Other Than iPhone
Laridian VIP Ed Hansberry posts the following on InformationWeek.com: Too Many Mobile OS’s Limiting Development For Companies.
Ed writes, “…there are a bewildering number of platforms and variations within the platforms to develop for. Enterprises will take the easy way out and just stick to one platform and a precious few models. Software developers that are selling their apps will have to have enough penetration for each platform to make development worthwhile. Each platform requires its own development team or at least a dedicated development process that takes time away from other supported platforms…. While phone carriers may support six or more mobile platforms, I am not sure the software industry will.”
We’ve been talking about this problem for some time:
Ed makes a good observation: There are at least six major mobile platforms. What if there were six desktop platforms? The software industry would be a significantly different place as companies tried to solve the huge problem of cross-platform development, multiple-platform development, and having enough market on any one platform to justify the incremental cost of maintaining or entering the market on that platform.
One thing you can say about Windows: By dominating the market Microsoft makes it easy for developers on desktop platforms. You can focus your development on one operating system. If you make it there you can consider Mac if you have enough users to justify the expense. Once you’ve covered Windows you have 80%-90% of the market. Whether you go for the 10%-15% represented by the Mac OS is a big decision, but at least it’s the only decision you’ll have to make.
For those of us writing software for mobile platforms there’s not only the issue of supporting a large number of platforms, but there’s the fact that the relative mix of market share on these platforms changes over time. Palm OS used to be our largest platform. Today the Palm OS is dead. Palm and Windows Mobile used to dominate the market; today iPhone and Windows Mobile hold the dominant share of customers. Deciding how we allocate development time and money is an ongoing process that changes a couple times every year.
Meanwhile Apple doesn’t make it easy to develop for the iPhone. I am having a major problem with getting the XCode programming tools to talk to my new 3G iPhone. The information at the Apple developer site is insufficient, and the developer forums they provide have numerous questions identical to mine that have gone unanswered for months. When you call “developer support” at Apple you get a guy in Great Britain who admits he has absolutely no idea how to solve the problem because he’s not a programmer and knows nothing about programming. He points me to the documentation, which is what I’ve been following to get me into the predicament I’m in.
It’s actually encouraging to see a major company like Yahoo make the decision to abandon all other platforms but the iPhone. (Actually, they’re supporting other platforms through customizations to their Web-based products.) It makes it easier for us to consider similar options.