This afternoon I uploaded PocketBible for iPhone version 1.0.0 to the App Store.
Now we wait.
Apple says it will take about two weeks. We’ll see. I know that uploading took me only 15 minutes, but that was after spending hours trying to find the right combination of options NOT to choose and titles I was NOT allowed to use for the program. So I’m not going to be surprised if approval takes longer than two weeks.
In the meantime we have a lot of work to do on the Web site to get it ready for the release. We’re going to try to make some changes to the way our e-commerce works at the same time. Hopefully we won’t break anything important.
I previously posted several videos of PocketBible in action. So if you’re curious, take a look at those.
One of the last things to come together was the program icon. We went through three major themes before finding a last-minute idea with promise. Our first idea was to lift the Bible icon from our Windows Mobile app. But when we looked at the 60 or more Bible apps on the iPhone, it seems over half of them had the same idea. So we were afraid we’d get lost.
So then we went with a version of our company logo. That had some fans, but suffered from being not very scalable as we release new programs (i.e. we only have one company logo but we expect to have more than one iPhone app). Plus it was boring.
While this was going on we had an artist work on a “Bible in a pocket” icon. The beta testers weren’t crazy about that one.
One of our testers is a fellow developer. He turned us on to his icon designer, who had the idea to used stained glass as a theme. We weren’t crazy about this at first but then I found a stained glass artist in Minnesota who had done some very contemporary looking work for a Lutheran church that seemed like it might work. We contacted the artist (Nicholas Markell) and he was willing to work with us. There were some interesting copyright issues, but Nick was a very reasonable guy and was pretty knowledgeable on the topic and we were able to work through those very painlessly.
So the program icon and splash screen (shown here) are based on a stained glass window entitled “Baptism of Jesus”. While the baptism of Jesus has little to do with our program, a little creative reinterpretation makes it work well. The Holy Spirit, represented here as a dove, illuminates the Scriptures for the believer. The water represents the “living water” (John 4) of the Word of God that gives eternal life through the cross, which is in the background of the image. Across the surface of the water runs the “scarlet thread of redemption” that ties the Bible together from the first verse of Genesis to the last verse of Revelation.
In addition to the obvious symbolic significance of this particular work of art, there’s the bigger symbolism of stained glass in a Christian context. Beyond its obvious beauty, stained glass windows served a valuable purpose in churches: They taught the stories of the Bible to a largely illiterate population. For many people in medieval times, church windows were their Bibles.
We like the meta symbolism of the medium of stained glass representing the Bible, and the specific symbolism of this piece as it relates to studying the Bible with our program. And besides, it looks really nice on the iPhone.
It’s unlikely we’ll hear any good news until the program is approved. We’ll pass along any bad news we receive just to keep you informed. Until then we have plenty to do to get ready. We appreciate all your kind words and prayers.
One of our PocketBible beta testers spotted a picture of Jeff in a Laridian pullover with me in a Laridian polo and asked if he could purchase Laridian apparel anywhere.
PocketBible for iPhone Beta 2 (Finally)
It’s been a long six weeks since we released Beta 1 of our native version of PocketBible for iPhone. At the time I said we were expecting the beta period to be short. Needless to say I was wrong.
A Wrench in the Works
Two major things happened to really slow us down. First, we have been really struggling to get adequate performance out of our code to allow you to be able to smoothly scroll through the Bible like you would a Web page in Safari on the iPhone. Safari has the advantage of being able to render the entire page. Once that is done, scrolling around on it — even zooming in and out — is pretty easy with the features of the iPhone OS. In our case, however, we can’t render the entire Bible while you wait. We have to load it into memory in pieces. Unfortunately, computers can only do one thing at once and while it was busy loading the next chunk of text it needed to display, the scrolling would get clunky. It wouldn’t keep up with your finger motions.
We actually got to the point where it was working pretty well. We were loading text in a separate thread and drawing during otherwise idle times (say, while the graphics processor was busy animating the motion of the text). But then we installed the OS 3 SDK and things fell apart.
We couldn’t afford to take the time to figure out how and why the new version was causing us problems. Suffice to say that the particular functionality we were taking advantage of was rewritten for version 3, and in so doing the handling of touch events changed in ways that may not be significant to some applications but were significant to us.
As a simple example, when you’re tracking a touch event, the system can send you a “cancel” message. This means the phone is ringing or some other event has happened and your program needs to stop what it’s doing and let something more important take over. Well, with version 3 we’d be happily tracking a touch event and suddenly we’d get a “cancel” message. It seems the system was watching the touch events and had decided that the touches weren’t doing anything it cared about, so it told us to cancel our handling of those events. We could’ve ignored the “cancel” message (knowing it was just the OS trying to take over touch handling) but since the “cancel” message also means “really — the phone is ringing — you need to stop right now” we couldn’t afford to make that assumption.
Anyway, the end result was we threw out about six months worth of work and in about a day I coded a replacement that doesn’t depend on a lot of fancy background threads, idle-time drawing, or system touch event handling. The new user interface is simple, practical, and best of all — it’s done.
As if That Wasn’t Enough…
So as we’re recovering from that crisis, the 3GS is released. Now, when you’re developing for the iPhone there are some strict procedures you have to follow to install your program on your phone. Apple wants to make sure all program distribution happens through the App Store, so they limit how many devices you can install your app on outside the App Store. Every time we distribute a beta version (or even one of our own builds we do internally and install on our own phones) we have to identify exactly which phones it will run on. Apple lets us install on no more than 100 devices outside the App Store.
To manage this, developers maintain a list of “unique device ID’s” (UDIDs) in their account on the Apple Web site. Each phone as a UDID that uniquely identifies it. We ask all of our beta testers for their UDIDs and enter those at the Apple site. When we distribute a new build we request a certificate from Apple that contains all the UDIDs we want the program to run on.
So as I was saying, the 3GS was released. Jeff bought one for us to test with. A bunch of our beta testers bought them. So anticipating the release of Beta 2, I started collecting all these new UDIDs so I could update our account on the Apple site and create the new distribution certificate with everyone’s new UDID in it. I got about half way through entering them and the site told me I couldn’t enter any more. It said I had already used my 100 devices.
I only had 82 devices in my list. Turns out when you change someone’s UDID it counts as a new device. I had added 85 devices, deleted 3, and made 15 changes. When you delete a device you don’t get its “slot” back, so from Apple’s perspective the total was 100.
After several email, support forum, and telephone conversations with Apple and other developers, we concluded that we were out of luck. We had to wait until our annual program renewed on July 12. At that time, Apple said our device count would reset. We could delete all our devices and start over. But once we started adding devices, we were stuck with those for a year.
One thing that meant is that we couldn’t have 82 beta testers. We needed to cut the list dramatically. I wanted to get down around 40 testers. That would allow us to add some people over the next year and have room for device upgrades. We should be able to struggle through until Apple figures out that its developers aren’t trying to rip it off; we’re just trying to test our software.
So last week we sent out an email “firing” about half our testers. It wasn’t pleasant, but we had to do it. I think we have a pretty good group left. I can tell they’re good because I disagree with them most of the time. It’s good to be challenged to look at things a new way, and these folks are definitely keeping us honest.
Beta 2 Features
There are some notable features in Beta 2 that the testers will be looking at over the next week or two. These include:
What’s Next?
There will be at least one more beta version before we submit PocketBible to the App Store. We’ll post an article like this one when Beta 3 is released, and another article when we send PocketBible to the App Store.
Once submitted, it will take a while for Apple to approve it. They might send it back and ask us to make changes. There’s no way of knowing how long that process will take. Sometimes it takes just a few days or a couple weeks. Other times it takes six months by the time you make all the changes they want and submit version after version for review. We don’t anticipate it will take that long but we have no way of knowing.
Any Bibles or books you buy today for any platform will be accessible from PocketBible for iPhone.