Subscribe to Updates

Click here to subscribe to new posts by email. We use Google FeedBurner to send these notifications.

Archive for the ‘iPhone’ Category

Serendipitous Programming

Posted on: July 27th, 2013 by Craig Rairdin 6 Comments

Today I’ve been working on a new feature for PocketBible for iOS and one thing led to another, and, well, I ended up implementing a feature I didn’t know I was working on, and didn’t realize how much of it was already sitting there, waiting to be exposed to the user.

So the new feature I thought I was working on is the ability to “rename” your highlight colors. That is, you’ll be able to assign a topic to each color. Then when you highlight a verse, instead of seeing a list containing “Khaki”, “Cornflower Blue” and “Hot Pink”, you’ll see “Salvation”, “God’s Love” and “Prophecy”. We’ve been wanting to implement this for a long time. While we were upgrading our cloud synchronization protocol over the last few months, I added the ability to sync highlight color names with the server and we took advantage of that in PocketBible for Windows Phone and Windows Store. The plan has always been to roll that into other platforms as we have the opportunity.

While looking through the code that shows you your list of highlight colors (which I’ll have to modify to show you your user-defined names for those colors) I stumbled into a bit of code that Jeff wrote years ago but then “commented out”. (If we have code that we’d like to retain for reference purposes but don’t want to actually have the computer execute, we turn the code into a “comment” so it will be ignored by the compiler but still be there if we want to see it.)

Those of you who have been with us for a while know that Jeff was my programming partner for 27 years before his death from cancer in May 2012. It’s been a bittersweet year as I’ve had to deal with his passing while surrounded and immersed every day in code that he wrote. I keep running into little things that remind me of him, make me want to give him a call to talk about a problem, or give me a chuckle. So it’s always interesting when I run into a piece of code like this.

What this particular piece of code did was add three additional highlighting styles to the list of colors you can highlight with. These are “underline”, “strikeout”, and “underline+strikeout”. Those look like this, this, and this, respectively.

Now, why would you ever want to strike out a verse? That’s a good question and takes me back fifteen years to the days of the Palm operating system when cameras were cameras, phones were phones, and “portable digital assistants” were all the rage. In those days, color displays were luxuries that cost money, size, weight, and battery life. So most of those devices had monochromatic screens.

On color screens, we could highlight a verse with a background color. But what could we do on these black and white screens? Since our text was coded in HTML, and since HTML offered simple styles like bold, italics, underline, and strikeout, we decided to use those. We ended up not using bold and italics because they could cause the text to re-wrap when they were applied, and in those days of wimpy processors, it just took too long and was disturbing to see. That left us with underline and strikeout, so that’s what we used.

As time has gone on, we’ve gotten to where we don’t even include these underline and strikeout highlighting styles in our programs. They’re not in PocketBible for iOS, and we weren’t planning on implementing them in PocketBible for Android. Unfortunately, some of you who were around back then and have sync’ed your highlights from your Palm PDA to PocketBible for Windows to our server and to PocketBible for iPhone expect to see those underlines. So we have to at least be able to display them if they exist, but we don’t let you create them (because we don’t want to proliferate a bad idea).

What I discovered today was Jeff’s original code for being able to create underline, strikeout, and underline+strikeout highlights in PocketBible for iOS. His comment said he had taken them out because the display engine (my code) didn’t support them. Sometime between then and now I implemented those highlight styles but we just never went back into Jeff’s code and turned those choices on.

On a whim, I enabled those lines of code and what do you know — they worked! That put me in the awkward position of trying to decide whether or not to leave them in. I never liked the idea of striking verses from the Bible, and even once you get over that, it makes the text hard to read.

About then it was time for dinner and I set the laptop aside to meet my wife and get something to eat. On the way there it occurred to me that we now have some better styling options that we had back in 1998. New versions of HTML with CSS support dotted and dashed underlines.

When I got home I spent about 30 minutes and implemented the styles you see here. These new styles replace the old styles rather than adding to them. So where you had strikeouts, you’ll have dotted underlines. And where you had strikeout+underline, you’ll have dashed underlines. I think this is a nice way of making your legacy data from your Palm days more usable and it gives you three more highlighting styles to use in PocketBible for iOS. (If you’re having trouble making out the dots and dashes, click on the screen shot to see the original size image.)

One of the cool things about this is that the underlying data storage and cloud synchronization already supports it. We’re not changing the data we save, but rather the interpretation of the data. So nothing changes in any of the other platforms nor on the server.

What I think is special about this — even though it’s not a life-changing feature — is that Jeff left it behind and it only took a little extra work to make it useful. And I like that all the infrastructure both for storing the new highlight styles and displaying them was already there.

Tomorrow I’ll get back to work on naming your highlight colors. But this was a nice little one or two hour detour to give us an unexpected new feature in PocketBible.

PocketBible 2.0.6 Available on the App Store

Posted on: October 31st, 2012 by Craig Rairdin 14 Comments

We’ve just been notified that our latest update to PocketBible (version 2.0.6) has been approved by Apple. It should become available in the App Store over the next 24 hours.

We apologize for the delay getting our iOS6-compatibility fixes into PocketBible. We ran into a couple of issues getting our update past the Apple approval process. In the end, being forced to address those issues caused us to find a couple tricky bugs that wouldn’t have turned up otherwise. But the whole process ended up taking longer than we wanted.

The complete list of new features and bug fixes is below, but a couple are worth highlighting. First, this version adds support for the Greek New Testament. You should find the SBL Greek New Testament in your list of downloadable books in “Add/Remove Books”. There are instructions in the built-in Help for enabling the Greek keyboard so that you can do searches in Greek.

Several bugs introduced in iOS 6 have been circumvented. In particular, you may have noticed PocketBible would only read the first verse on the screen to you when you asked it to start reading. This has been fixed. And it’s not really a bug, but PocketBible will now take advantage of the full height of the screen on the iPhone 5. (This wouldn’t have been a problem except that Apple “lies” to our app when we request the size of the iPhone 5 screen, apparently to maintain compatibility with apps that aren’t as clever as PocketBible by making them think they’re running on an older device.)

I believe we’ve finally fixed the problem of books and voices disappearing when memory runs low. Apple changed the way they do this a couple of times over the last year or so and kept defeating our efforts to preserve our files. We think we have it figured out now.

Finally, PocketBible now requires at least iOS 5. The latest version of the development tools only produces ARMv7 binaries and there are no ARMv7 devices that don’t support iOS 5. We’d like to support older versions of the operating system, but we’re limited by what the development tools support.


What’s new in this version?

  • Support for the SBL Greek New Testament including display, searching and copy/paste.
  • Added “Find Selection” to the Selection menu. Rearranged the Selection and Context menus to put more frequently used items closer to the top.
  • iOS 6 compatiblity including:
    • Fixed a bug where PocketBible would stop after one verse when speaking the text
    • Addressed rotation issues
    • Added 4″ Retina launch image and support for the full height of the new iPhone 5 screen
  • Bug fixes including
    • Fixed a bug in certain books with images where they did not appear when “shrink to fit” was selected
    • Changed the way text is selected to address sluggishness on devices with Retina displays
    • Fixed a problem that manifested in ZIBBCNT and HBH where images in tables were not shown if “shrink images to fit” was selected.
    • Made sure the built-in KJV, Help, and Welcome documents plus downloaded voices all get marked as “do not back up to iCloud”.
    • Related to the above, downloaded books and voices were moved to a folder that should not be purged under low memory conditions.
  • Set the minimum iOS version supported to 5.0.

PocketBible for iOS users: What can Advanced Features do for you?

Posted on: September 11th, 2012 by Michelle Stramel 8 Comments

If you are using PocketBible 2 or later for iOS, here are some good reasons to upgrade to Advanced Features and how to do it.

Why upgrade?

The Advanced Features available for PocketBible on the iPhone, iPad or iPod touch offer some handy additions to the basic features of PocketBible.

You can watch an overview of the Advanced Feature Set below:

Tabs (or tabbed panes) are especially wonderful on the iPad. I keep 5 tabs open on my iPad and each tab contains a specific type of book so the headings display category of book (i.e. Bibles, Commentaries) rather than book abbreviation. When you mix different types of books within a pane, PocketBible shows the abbreviation for the top book instead of the category. Tabs make it fast and easy to move from my Bible to a commentary or other type of book and get the information I need to understand what the Bible is saying.

Autostudy is very useful to me because I often compare Bible translations when I read the Bible. If I particularly like or, conversely, don’t understand a verse, I want to see how it is translated elsewhere. Autostudy will put that together in seconds–all on one page. It will do the same for information from other types of books as well – commentaries, dictionaries, etc.. You can get more details on this feature in our article: Have you discovered Autostudy?

Would you like to have the program read the Bible to you? The Advanced Feature Set adds the ability to do this but you will need to make one more purchase of a voice (at $1.99 each) to take advantage of that ability. PocketBible voices are synthesized which means they are electronic and therefore won’t take up as much space on your device as an “audio Bible”. I have found this feature extremely handy for keeping up with my Bible reading in the car, as I clean the house, on a run — time that might otherwise be wasted can be reclaimed for a good purpose.

If you like to copy passages from your reference or other type books, you’ll want the Advanced Features as they allow you to do just that. And if your printer supports AirPrint, you’ll be able to print from the program.

Advanced Features were enhanced with the release of PocketBible 3 and now offers these additional capabilities!

  • A new Journal feature lets you add comments to PocketBible that are not connected to a specific book.
  • You can now rename your highlights colors. For example, you could change the label for salmon to love and use your highlights as categories for specific types of verses.
  • Change the behavior of the touch zone nagivation. The most common customization is to use swipe up and down for page changes instead of swiping left and right. Other customizations are possible.

How to upgrade

If you are already using PocketBible 2 or later on your iDevice, adding these new features is straight-forward:

  1. Purchase the Advanced Features at our web site for $4.99 (it is also available in-app for $1.00 more). Add a Voice at the same time if you think you want to use that feature. I prefer Tracy but our best-selling voices are Heather and Ryan.
  2. Go into PocketBible on your iOS device and choose the Menu button and Buy/Apply Upgrade (if you’ve already purchased at our website, you’ll just be applying). Choose Add/Remove Voices to download a Voice if you’ve purchased one.

You’re all set!

If you are still using PocketBible 1.4.7 (or earlier) for iOS, follow our 3 Steps to Move from PocketBible 1 to PocketBible 3 on your iOS device.

Why Are My Books Being Deleted?

Posted on: August 8th, 2012 by Craig Rairdin 7 Comments

Lately we’ve been seeing an increasing number of reports of the iPhone or iPad deleting PocketBible books to make room on the device for newer apps, music, or content being downloaded to the device. The assumption seems to be that PocketBible is doing something “wrong” and we need to fix it. It can be argued, however, that PocketBible is following the rules but a) the rules are not what you think they are, and b) the rules keep changing.

When the memory on your iOS device gets close to being full, the operating system looks for files it can delete to make room for whatever it is you’ve asked it to store — usually pictures, music, videos, apps or other large files. This makes the books you download for PocketBible vulnerable to deletion (just as your other data is vulnerable when you download PocketBible books onto a relatively “full” device). To get around this, we originally stored your books in a folder where the operating system promised not to delete them.

When iCloud came out and users started backing up their devices to the cloud, all those files started filling up Apple’s servers. Apple was concerned about the volume of data it had committed to store, so they contacted developers and asked us to move our files into folders that were not backed up to iCloud. Included in the list of files that should be moved were any files that could either be re-created the next time the program ran, or be easily downloaded again. This included PocketBible books.

While it would’ve been easier for Apple to just buy more hard drives for their servers, we agreed to move our files as requested. What they didn’t explain at the time was that by moving the files to the suggested folders, they would be subject to deletion as the device approached its memory capacity. After receiving some complaints, we contacted Apple and they told us how to mark files so they would not be purged even though they were in a folder that is normally purged when the device is low on memory. This solved the problem for a while.

It appears, however, that Apple has released an update that ignores the “do not purge” flag on our files and deletes them anyway. They are now saying we should move the files back to where they were before, but mark them as “do not backup”.

This is a consistent pattern with Apple. New releases of the operating system break small things that were working in previous versions. Rather than fixing the OS, Apple asks all its developers to modify their programs. Since they’re Apple, they can do this and get away with it.

One of the problems we face at Laridian is that making changes to an app and re-submitting it to the App Store for approval is a tricky proposition. Last time we did it, Apple rejected the app not for anything that had changed, but for a feature that had been in the program for the last five or six versions that they had previously approved. It took us three months and three more submissions (each time following the instructions they gave us to assure that the program was more likely to be approved) before Apple finally approved the app.

So we don’t submit PocketBible for re-approval without making sure we’ve included all the changes we might want to make for the next several weeks or months because it is a potentially lengthy process. Right now, we’re in the middle of some changes to PocketBible for Windows, Android, and iPhone to support some new features. We’d prefer not to do multiple submissions and so are hoping to complete these new features before uploading a new version to the App Store.

In the meantime, if your memory usage hovers around “full”, be proactive and remove some PocketBible books that you don’t absolutely need. It’s not that hard to simply re-download books as you need them. I regularly show up at church on Sunday morning and realize all my books are gone because I’ve been removing and re-installing PocketBible during testing. It’s simple enough to grab the Bibles and dictionaries I regularly use on Sunday morning while we’re singing our opening hymns so they’re there for the sermon. I can pull down my commentaries later as I want to use them.

While you’re doing that, we’ll work on yet another update to where your books are stored. And hopefully Apple will approve. :-)

3 Steps to Move from PocketBible 1 to PocketBible 3 on your iOS device

Posted on: August 7th, 2012 by Michelle Stramel 5 Comments

Are you still using the first version of PocketBible on your iPhone, iPad or iPod touch? If so, we highly recommend moving to PocketBible 3 so you can apply program updates as they are released; we won’t be updating PocketBible 1.4.7 further.

Before we explain how to make the move, check your version number in PocketBible by tapping on the Menu button and selecting About PocketBible. If it PocketBible 1.X.X, keep reading.

  1. Step One: Go to the App Store on your device and search for PocketBible (all one word). Download the program. You’ll notice that the new program has the same icon as your old PocketBible program. If you get confused, follow the tip above to check which version of the program you are in.
  2. Step Two: Delete the old program…wait! Don’t do that yet if you have been adding notes, highlights, bookmarks or tracking reading progress that you want to save. First, read the instructions (click link and scroll to the section Moving Your Notes, Highlights, Bookmarks and Daily Reading Progress to the New Program) to transfer your data. Then delete the old program.
  3. Step Three: Re-download your books. Go into the new program and register if you haven’t already encountered that. Be sure to use the email (or Laridian ID number) and password associated with your existing Laridian account. After registration, tap on the Menu button and choose Add/Remove Books to re-download your past purchases. All your books can be downloaded in one fell swoop if you tap on each book you want to download and then tap on Update at the top of the page.

Why the extra steps? Normally, when you update a program, you just go into the App store and it tells you an update is available. PocketBible will work that way again once you download the new version. If you want to know the “why” you can get it from our initial post on this new version.

Anything else to know? Yes (but it is optional). Once you install PocketBible 3, you can also purchase and install an Advanced Feature Set for $4.99. If you purchase the Advanced Feature Set, you can add a Voice or two to the program and listen to the Bible or any book. Voices are synthesized and sell for $1.99 each.

PocketBible for iPhone tip: Viewing images

Posted on: January 20th, 2012 by Michelle Stramel No Comments

If you are using PocketBible 2.0.3 (or later) on your iPhone or iPod touch, you will find it much easier and more enjoyable to view images than with previous versions. This is especially handy if you own our Bible Maps or one of our study Bibles or reference books that offer detailed charts or lists (i.e. ESV Study Bible or Ryken’s Bible Handbook).

In PocketBible 2.0.3 (and later), you can double-tap on an image to blow it up in a window where it can be zoomed and scrolled. It works best to go into Settings and mark it to “fit images to the screen,” then just double-tap the image when you want to view it in detail. If an image has links in it, those links are “hot” in the zoom view. Most images do not have links, but the maps in our Bible Maps product do.

PocketBible 2.0.3 Now Available on the App Store

Posted on: November 22nd, 2011 by Craig Rairdin 12 Comments

We just heard from Apple saying that 2.0.3 has been approved. You should already be seeing the update in iTunes on your device. We recommend everyone grab this update, as it fixes a few little problems. It also adds a couple of small enhancements that should make the program more enjoyable to use.

If you’re still running 1.4.7 or an earlier version you need to follow the instructions here to get this new version. Version 2.0.3 is not an automatic update to 1.4.7 or any 1.x.x version of PocketBible.


Double-tap on any image to blow it up in a window where it can be zoomed and scrolled. This is handy for maps and some of the detailed charts that appear in some study Bibles and reference books. It works best to go into Settings and tell it to fit images to the screen, then just double-tap them when you want to view them in detail.

If an image has links in it, those links are “hot” in the zoom view. Most images do not have links, but the maps in our Laridian Maps product do.

Books and voices are now marked as “non-purgeable” as they are downloaded. We got some reports that iOS would delete your books if it needed space for another app. This can be disturbing when you discover that books you spent a long time downloading are suddenly gone. By marking these as non-purgeable, Apple promises us they won’t delete them.

Note that while we retroactively mark your existing books as non-purgeable, and that we mark books and voices as non-purgeable as they are downloaded, we do not mark existing voices as non-purgeable due to the complexity of the file structure for voices. If you operate on the edge of available memory and want to make sure your voice files get marked as non-purgeable, you should delete them with Add/Remove Books, then download them again.

If there’s only one book open in a tab, we use that book’s abbreviation as the title for the tab rather than using the book’s category (“Bibles”, “Commentaries”, etc.) as the tab title.


On iOS versions prior to 3.2, there were controls to allow you to turn on the tabbed interface even if you didn’t own the Advanced Feature Set. Unfortunately this didn’t really give you the full features of the tabbed interface because the rest of the program would get confused by the fact that you had tabs turned on but did not own the Advanced Feature Set. This version fixes that by hiding those controls.

Printing, emailing, or texting the selected text could crash or do nothing. This has been fixed.

We believe we’ve fixed a problem in which the text window was offset right and up so you could see the gray background behind the text window. This only happened to some users and only under certain circumstances. We could only duplicate it on one of our iPhones. It wasn’t related to which version of iOS you were running or which type of device you had (though I think we only saw it on iPhones and iPod touch devices, not iPads). What it was related to was the version of the development tools we used.

Turns out Apple swapped out a portion of the compiler that converts our Objective-C programming code into the machine code that runs on the phone. The new compiler apparently generates flawed code. (Compare to what happens when an inexperienced translator flubs up the translation of a speech at the United Nations. The original speech is fine but the translation doesn’t say what the original speaker said. That’s what happened to our code. Our code was correct by Apple’s translation of it made the device do something different.) We fixed it by turning off all the special optimizations that the compiler can do for us. Hopefully another programmer will be able to demonstrate this bug in some simple way so Apple can fix it. We were never able to do it reliably, so we couldn’t report it.

As I said, everyone should install this update. You don’t need to re-download your books or voices, nor do you need to sync your personal data after you update. This is just a normal program update that won’t affect anything you’ve downloaded nor any of your notes, highlights, or bookmarks.

PocketBible 2.0.2 Available on the App Store

Posted on: October 21st, 2011 by Craig Rairdin 14 Comments

We’ve just been notified that our latest update to PocketBible (version 2.0.2) has been approved by Apple. It should become available in the App Store over the next 24 hours.

This update mostly affects people at either end of the range of supported iOS versions. For those of you still running some version of iOS less than 3.2 (primarily those of you with first-generation iPod touch devices running 3.1.3) you’ll finally get to see what PocketBible 2 looks like. Both the initial release and the 2.0.1 update had problems that prevented them from running on those devices. We had been relying on our development tools to tell us if we were using features of iOS that were not present on those older devices. Unfortunately, it turns out they are very silent on that issue. We’ve learned our lesson and have “downgraded” an old iPhone to 3.0 for testing. (Previously we were limited to running 3.2 in the iPhone emulator.) As a result we’ve been able to identify the issues that were preventing PocketBible from running on 3.0 and 3.1 devices.

On the other end of the iOS version spectrum we ran into an interesting bug in iOS 5. When we put verses on the pasteboard (that’s “clipboard” everywhere else but in Apple Land), we always store both a plain-text version and an HTML version. This allows applications that understand HTML to paste nicely formatted text, including superscripted verse numbers, words of Christ in red, and bold headings. Simpler applications expecting only plain text have the option of requesting just the plain text from the pasteboard.

When an application pastes data from the pasteboard, it specifies what format it wants. Unfortunately, in iOS 5, when an application asks for the traditional “utf8-plain-text” that has worked in all iOS versions since the beginning of time (OK, since iOS 2), the operating system will not give it the “utf8-plain-text” version of the pasteboard text, but instead will substitute something else — in our case, the HTML text that is also there. Since the pasting application neither expects nor understand HTML, it treats it as plain text and pastes it, tags and all, into your document.

To get around this, we have to add a third form of the text to the pasteboard, which is identified simply as “text”. This version is identical to the more correct “utf8-plain-text” that has worked on previous iOS versions. Doing this tricks iOS 5 into supplying plain text to apps that request it, so that pasted verses no longer include HTML tags.

On the subject of iOS 5, it introduced some new fonts and some new ways of identifying old fonts. Since iOS makes it very difficult to determine if a font provides the bold, italic, and bold/italic versions that PocketBible requires, we use a somewhat fragile technique to try to make that determination by looking at the names of the fonts. This didn’t work exactly right in iOS 5. The result was that Helvetica Neue was displayed as condensed and bold, and both Optima and Hoefler Text were missing from the list of available fonts. This has been fixed and the code reinforced so that hopefully it will do a better job identifying fonts in the future.

Some of you have had the unfortunate experience of selecting two or three verse and when you ask PocketBible to highlight the selected verses, it highlights the rest of your Bible. This happens when the end of your selection is right on the little gap between paragraphs. This is fixed in version 2.0.2 so that your entire Bible isn’t highlighted when you only want to highlight a couple verses.

Finally, probably because of the load that PocketBible 2 has put on our servers, many of you ended up with corrupted book files. Since PocketBible can’t read the file (the were corrupted during download) it can only identify the book by its 8-character alphanumeric file name. So you would see a message that “0065001d.lbk” was damaged, but there was no way to know what book that was so that you could re-download it. This message came up every time you ran PocketBible. The new version deletes damaged books automatically so that you won’t be nagged by warning messages.

For all the complaining we do about the App Store approval process, this update was approved in about 24 hours. Hard to complain about that!

PocketBible 2.0.1 Approved by Apple

Posted on: October 12th, 2011 by Craig Rairdin 19 Comments

We’ve just been notified that PocketBible for iOS version 2.0.1 has been approved. This is essentially an update that tries to squash the inevitable little bugs that show up in any x.0.0 version.

Some of you were completely unable to run PocketBible at all. Turns out if you weren’t running a relatively recent version of the operating system, PocketBible would display its splash screen then immediately exit. This has been fixed. We were all somewhat surprised we hadn’t found that problem before releasing the program, since it was trivial to reproduce once we set our minds to it. We get used to our programming tools warning us when we try to do something that’s not available in older versions of the OS and don’t always test for compatibility as thoroughly as we could.

Some of you were surprised to hear Heather or Ryan or one of our other voices start reading the Bible to you when you hung up after a phone call. Turns out if you paused PocketBible’s synthesized voice instead of stopping it, then any interruption would restart the reading. That was an easy fix once I figured out what was going on. Sorry if it caught you at an inopportune time.

This brings up an interesting point: You probably didn’t realize that the “mute” switch on your iPad or iPhone is only a “suggestion” to the device. You might think you’re turning off the sound, but you’re not. Apple treats the iPod app and other apps that play “foreground” sound (such as PocketBible) as immune from the effects of the mute switch. They believe you only intend to mute background sounds from games, key clicks, and that kind of thing when you flip the mute switch. Hmmm.

A couple of you reported that you only had two panes/tabs on your iPhone after upgrading to the Advanced Feature Set, instead of the advertised five panes/tabs. It could be fixed by exiting the program and re-launching. We were able to find the problem and fix it so you won’t have to do that in the future.

While printing out one of my own sermon notes I discovered the Autostudy CSS settings for ordered and unordered lists were overriding my list types. So my nice outline with roman numerals and upper/lower case letters was displayed with all arabic numerals. I made a change to the default CSS so this won’t happen.

Some of you were able to crash the program while doing a “Paste to Email” or “Paste to Text” operation. When we looked at the code, it looked like it should always crash, yet it never crashed for us and it didn’t crash for many of you. So this is one of those cases where we’re not sure why it ever worked at all. Nevertheless, it’s fixed in 2.0.1.

Finally, we got a nice note from Apple saying they were concerned about the effect our Bibles and books would have on the amount of data backed up to their new iCloud service. Data that can be re-downloaded from our server, they said, should not be stored in a directory that is automatically backed up. We see it the other way. We think you’d like to have your entire PocketBible library restored when restoring from a backup set, without having to separately log into our server (and any other server for any other program you might have with ebooks or other downloadable data). We read the developer documentation as “suggesting” that we don’t do that, so after considering the suggestion we decided to leave it the way it was.

However, Apple seemed really concerned about the few dollars this might cost them in additional hard drive space for iCloud, and given that they’ve gone through some tough times lately we decided to help them out. Version 2.0.1 automatically moves your books to a folder that does not get backed up to iCloud. So if you ever have to restore a backup, you’ll have to log into your account on our server and re-download your books. Just don’t everyone do it at the same time. :-)

PocketBible 2 for iOS Now Available in the App Store

Posted on: October 4th, 2011 by Craig Rairdin 65 Comments

By the time you read this, PocketBible 2 for iPad, iPhone, and iPod touch should be available in the App Store. It introduces several new features and a new pricing scheme.

Quick Summary for the Horribly Impatient

PocketBible 2 is called “PocketBible” in the App Store. It is a free download. PocketBible 1 (“PocketBible FREE” in the App Store) is no longer available in the App Store. YOU MUST DOWNLOAD THE NEW POCKETBIBLE FROM THE APP STORE IN ORDER TO GET THE ADVANCED FEATURES MENTIONED BELOW. Some of you are trying use the feature set upgrade on the old PocketBible FREE 1.4.7. That won’t work. You must download the new PocketBible from the App store in order to get the advanced features mentioned below. There’s a link to PocketBible 2 in the next paragraph.

Click here to download the new version of PocketBible. (NOTE: Do not skip this step!)

The free version of PocketBible 2 has pretty much the same features as PocketBible 1.4.7 (one exception is described below). To get the new features, you need to purchase the “Advanced Feature Set” either at our website ($4.99) or through In-App Purchase inside the app ($5.99).

After you purchase the upgrade at our website, go to “Buy/Apply Upgrade” inside the app to apply the upgrade and enable the advanced features. You must provide your Laridian login credentials during this step so the program can find your purchase on our website.

If you have notes, highlights, bookmarks, or devotional reading progress you want to preserve, you need to move that data to your new copy of PocketBible using the process described below (and also in the built-in help). To get your Bibles and books into the new version, you need to simply download them using Menu > Add/Remove Books.

All PocketBible users should switch to the new version even if you don’t upgrade to the Advanced Feature Set. The old version of PocketBible will not be updated and has been removed from the App Store.

New Features in Free Version

The free version of PocketBible 2 has essentially the same features as PocketBible 1.4.7. The only significant new feature in the free version is related to expanding the Toolbox. In version 1, the expanded toolbox covered the Bible text. When we first implemented the expanding Toolbox, we figured it would be a temporary action. However, we’ve found that we prefer to have the Toolbox expanded while entering notes, and it’s inconvenient to have to collapse it to view the BIble text. So now PocketBible moves the active pane to the empty space above/below/next to the expanded Toolbox. And if the keyboard obscures part of the pane, the pane is shrunk again to fit in the available space.

All PocketBible users should switch to PocketBible 2. Version 1 has been removed from the App Store and won’t be updated. To make sure you get the latest bug fixes and updates, you should make the switch now to version 2 even if you’re not planning to purchase the Advanced Feature Set. This unfortunate circumstance is the result of the way Apple has us sign and identify applications.

Advanced Features

To access the advanced features in PocketBible 2, you need to purchase the “Advanced Feature Set” — either inside the app for $5.99 or directly on our website for $4.99. Advanced features include:

  • Automatic verse studies. Select a verse and PocketBible prepares an HTML or plain-text document chock full of information about that verse from your Library. This file can be viewed from within PocketBible, transferred to your Windows or Mac computer through iTunes, printed using AirPrint, or copied and pasted to an email. Each Verse Autostudy report includes:
    • The text of the selected verse from all your Bibles (you choose which ones)
    • The text of the selected verse with Strong’s numbers (if you own one of our Bibles with Strong’s numbers)
    • The definition of each English word in the verse from all of your dictionaries (you choose which ones)
    • The definition of each Strong’s word number from your Strong’s dictionaries (you choose which ones)
    • Commentary on the verse from all your commentaries (you choose which ones)
    • Cross references from the Treasury of Scripture Knowledge (if you have it installed)
  • Automatic word studies. Select a word and PocketBible prepares a similar HTML document, this time with information about the selected word. Each Word Autostudy report includes:
    • Definition of the selected word from all of your dictionaries (you choose which ones)
    • A summary of search results from selected Bibles (you choose which ones)
    • A list of related Strong’s numbers (original language words translated to the selected word)
    • Definitions of the related Strong’s word numbers (you select which Strong’s dictionaries)
  • Synthesized voices read any Bible or book to you. Purchase a voice from a selection of six English and three Spanish voices, and PocketBible will read to you! Works with any of your Bibles or other books, does not require an internet connection once the voice is installed, and takes only about 50MB-75MB (compared to
    4000MB for a pre-recorded audio Bible). Start a playlist of hymns and have PocketBible read to you from the Psalms for an inspiring time of daily devotions. Or have PocketBible read while you do other tasks on your iPad. No other mobile Bible program can do all that.
  • New tabbed view. Both iPhone and iPad now support up to five panes (iPhone was previously only two panes) and you can choose to view five full-screen tabs instead of splitting the screen into panes. Just select a tab to view the books open in that tab.
  • Automatically open all your books into tabs. PocketBible will open Bibles, commentaries, dictionaries, devotionals, and “other” books each into their own tabs for easy access to your entire library.
  • AirPrint support (iOS 4.2 or later). Print Autostudy reports, passages, or selected text to your AirPrint-capable printer.
  • Improved text selection. Drag through any text to select it. Copy, print, speak, or perform other operations on the selected text. Uses familiar iOS interface components (such as the magnifying glass and lollipop-shaped “drag handles”). (This seems obvious but we had to implement them from scratch as Apple doesn’t expose those components to developers, so it seems worth mentioning.)
  • Highlight selected verses. Highlight more than one verse at a time by dragging through any portion of the verses, then select “Highlight selected verses”. You can’t highlight portions of a verse, but you can highlight more than one verse at a time.

Apple Changed the Rules

As many of you know, Apple now requires that ebook apps like ours must not link to a website for add-on book sales, but must use Apple’s In-App Purchasing (IAP) capability and pay Apple 30% of each sale for doing little more than processing a credit card (which costs them about 3%). Amazon responded to this by entirely removing all links to their website from their Kindle app. We opted to implement Apple’s IAP but at a slightly higher price to offset Apple’s fee. (You’ll pay on average about 17.6% more for a book you buy using IAP vs. purchasing direct on our site, which results in us splitting the 30% fee 50/50. The proof is left for the reader.)

This would have very little consequence except that PocketBible 1.4.7 was created in a way that prevented it from ever using IAP. As a result, version 2 could not simply be a new version of the existing “PocketBible FREE” application. Instead it had to be a separate product. This is confusing for those of you upgrading from version 1, but should not be a problem in the future.

Moving Your Notes, Highlights, Bookmarks and Daily Reading Progress to the New Program

Since PocketBible 2 is a different program than PocketBIble 1, you will need to move any notes, highlights, bookmarks, and daily reading progress that you want to keep from PocketBible 1. Again, this is only necessary if you have data you want to preserve. To do that:

  • Launch the old version of PocketBible. Verify it’s the old one by looking at the version number at the bottom of the menu. Next to “About PocketBible” it should say “1.x.x” (the latest version is 1.4.7).
  • Choose Menu > Manage My Data.
  • Enter your Laridian login credentials and select either “Sync My Data With Server” (if you’ve been sync’ing your data with the server in the past) or “Back Up My Data To Server”. Note that if you have been keeping your data in sync with the server and you know it is up to date, you can skip this step.
  • When that is complete, exit PocketBible and launch the new PocketBible program.
  • Verify you are in the new PocketBible program by going to the bottom of the menu. Next to “About PocketBible” it should say “2.0.0” (or later).
  • If you have not yet registered, do so now. (You’ll see “Register PocketBible” near the top of the menu if you haven’t registered.)
  • Choose Menu > Manage My Data.
  • Enter your Laridian login credentials and select either “Sync My Data With Server” (if that’s what you did in version 1) or Restore From a Backup (if you used “Back Up My Data To Server” above). If you are restoring from a back up, you’ll be presented with a list of backup sets. Find the section labelled with the name of your device followed by “com.laridian.PocketBible” and choose the top item from that list (the most recent backup).
  • When that is complete, you have transferred your personal notes, highlights, etc. to PocketBible 2. You can remove the old PocketBible program from your device and download Bibles and reference books into PocketBIble 2.

Some Screen Shots

Here are some quick screen shots to give you an idea of some of the new and improved features.

Bible text now moves out of the way of the expanded toolbox, making it easier to take notes and follow along in the text at the same time.

New text selection method that lets you select any text. Also note the tabbed interface. Choose “Open All Books” to open your books into categorized tabs. (Advanced Feature Set)

Here I’ve finished selecting the text and the menu appears. The old “context menu” is still available by selecting “Menu”. To get options that apply to the selected text, choose “Selection Actions”. (Advanced Feature Set)

Selected text can be copied to the pasteboard, printed, emailed, sent by text message, spoken (if you have a voice installed) or looked up in a dictionary. (Advanced Feature Set)

Select “Autostudy Verse” from the context menu to quickly find everything in your library about a particular verse. You can do a similar study on any word. (Advanced Feature Set)

©2015 Laridian