Subscribe to Updates

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

What’s in the Pipeline?

Posted on: October 10th, 2016 by Craig Rairdin 80 Comments

We often get asked about what we are working on. While you can be sure we are always working, and that our work probably involves some version of PocketBible, we understand you may be interested in a more detailed explanation of what is going on behind the scenes. It is in that spirit that we are going to try something new with an occasional post on what’s in the pipeline for apps and books.

You’ll notice we don’t talk about release dates. We’ve been in this business for a long time and have learned that our best-laid plans often go awry. In fact, in the software business, that’s the rule rather than the exception. So we don’t spit into that wind nor tilt at those windmills. We’re pursuing the goals you see below at our best pace and will release new books and updates to our apps as soon as they’re ready.


  • PocketBible for Android – Working on minor bug fixes and improvements, releasing minor updates as needed.
  • PocketBible for iOS – Version 3.4.0 is current. Currently working on a major re-write to support scrolling of the text (in addition to the current paging mode) and simplifying highlighting, bookmarking, and text selection. This will be version 4.0.
  • PocketBible for Mac OS X – Working on minor bug fixes and improvements, releasing minor updates as needed.
  • PocketBible for Windows Phone and Windows Store – Working on a universal version of the app for Windows 10.
  • BookBuilder for Mac OS X – Working on minor bug fixes and improvements, releasing minor updates as needed.
  • BookBuilder for Windows Desktop – Working on minor bug fixes and improvements, releasing minor updates as needed.


Here’s what our editorial team has in the queue for you (not in any particular order):

  • Additional volumes of the Ancient Christian Commentary Series (IVP)
  • Fixing typos and tagging issues in several titles
  • Additional Greek NT resources
  • NIV Exhaustive Concordance
  • Tree of Life Version (TLV)

Disclaimers: All this is subject to change in priority, feasibility, copyright licensing, etc. That means we reserve the right to never release these features or books. We are sharing with you the current plan which is written in sand, not stone. Also, just because something is not on this list doesn’t mean we are not considering it. Finally, we are open to your requests, suggestions and comments!

PocketBible for iOS Alpha/Beta Testers Needed

Posted on: May 16th, 2016 by Craig Rairdin 9 Comments

PocketBible iOS IconI’m looking to increase the number of  testers we have working on PocketBible for iOS.

PocketBible version 4 is still in what we might call “alpha” stage, where it is ready for some outside testers but is not feature-complete. This new version is a significant re-write of the currently shipping 3.4.0. New features have been added and existing features have been re-implemented in completely different ways. The most significant of these is the way text is displayed and scrolled. The touch zones are gone (for the most part), the text can now be continuously scrolled (rather than paged), and text selection is different.

Here’s the list of what’s new so far:

Early build showing toolbar icons, verse selection, and selection toolbar.

Early build showing toolbar icons, verse selection, and selection toolbar.

  • Continuously scrolling book text. Uses the built-in webkit HTML rendering engine for books instead of our custom HTML renderer.
  • Text selection works differently. Press-and-hold to select a verse (Bibles) or paragraph (other books). Selection toolbar is displayed in place of the old built-in iOS menubar. Tap to select additional verses/paragraphs.
  • Changed order of highlight colors on the list of colors so that your three most recently used colors are at the top. Moved the highlight eraser to the top of the list of colors (after the most recently used) so that it is easier to find.
  • Added the ability to search notes to the iPhone. Previously only available on iPad.
  • New WYSIWYG note editor replaces the need to type HTML tags to get text and paragraph styles. Notes are still in HTML and you can still edit the text directly to insert tags, but that is all manual now.
  • When viewing an image in full-screen mode (double-tap on an image in a book), the app may download a higher resolution version from our website if one is available.
  • Added the option of textured backgrounds.
  • All new button images (toolbars, etc.) throughout.
  • New font/size picker uses the “spinner” control instead of a “slider”. Significantly easier to use.

In addition, there are a few smaller changes, some of which are removal of little features that are less convenient given the new way of displaying the text, while others are user interface enhancements:

  • New launch image background color.
  • “Split Screen” on iPhone without Advanced Feature Set is now just a toggle. Screen is either split (two panes) or not (one pane). Used to show you a list containing “1” and “2” from which you could choose.
  • When selecting number of panes, the current number of panes is indicated (previously you just saw a list of numbers).
  • Got rid of the brightness control. iOS does a better job of this than we can do, so just use the system screen brightness.
  • Title bar and tool bar are always visible since there is no longer a way to display them on request (i.e. no touch zones).
  • Images are always shrunken to fit the width of the pane.
  • iPad Toolbox expansion arrow now floats over the pane so that it is always visible even when keyboard is present.
  • Removed the “HTML helpers” from the plain-text note editor. Use the WYSIWYG (“rich edit”) note editor instead.

This is just where we are as of today. We are still adding features. I’d just like to get a few more people looking at the program as we go.

The alpha version (currently designated 3.9.x) installs alongside the currently shipping version so that it won’t interfere with your current working verson of PocketBible. You can create a new customer account when you register the alpha version if you don’t want to expose your “real” notes/highlights/bookmarks to the testing process.

We have some very specific rules for signing up to test. If you don’t follow these instructions I will discard your application.

  • You need to be able to accurately find and send me your “unique device ID” (UDID). Note that there are old utilities for doing this that will give you a wrong result. If it starts with “ffff”, it’s wrong. Here’s a simple explanation of how to find it using iTunes, along with a Web-based tool that works well if you want to try that instead:
  • Tell me what version of iOS you’re using and what kind device you have. You must be running iOS 8 or later.
  • Send this info to with the subject line “iOS Beta”. You should also use this email address if you use to send your UDID.

I will try to respond to each person who applies. Apple limits the number of testers we can have, so I may have to reject some of you. Or I might not. That UDID thing tends to eliminate a lot of people, so we may not get many volunteers. :-)

If you’ve been testing with us over the last few months already, there’s no need to re-apply.

I will pull this article when I get enough testers, so if this article disappears, we’re full.

Thanks for your help!


PocketBible 1.2.0 for Mac OS X Available

Posted on: March 28th, 2016 by Craig Rairdin No Comments

We released an update to PocketBible for OS X today primarily to address some issues that came to light with the release of Deluxe Bible Maps and Timelines. While we were in there we made a few other little adjustments.

The main difference you’ll see is when viewing large images. Previously, large images would bleed off the right edge of the pane, requiring side-to-side scrolling. This worked fine but it made it hard to see the whole image. Version 1.2.0 resizes images so they fit in the width of the pane. If you make the pane wider, the image is re-sized to fit.

Perhaps of more interest are a couple little behavioral tweaks I’ve been meaning to make for a while. First, Advanced Feature Set owners will notice that I’ve extended the hover behavior so that hovering over a Bible link in your notes will show the verse in a pop-up preview window. This is the same behavior you already have for links in books. You’ll also notice that the preview pop-up now uses the same font and size as you have selected for your books instead of using the default font and size provided by OS X. For those of you who like larger print, the small print in the preview pop-up was kind of hard to read.

Second, I’ve added a separate color and underline setting for Strong’s numbers. This allows us to display Strong’s numbers in a slightly lighter shade of the text color so that they’re still readable, but don’t interfere as much with reading the text. And being able to turn off the underline just makes the text look cleaner.

Finally, I’ve made some changes to how we handle the clipboard when you copy an image. Previously we put both the image and an HTML image tag on the clipboard. This allowed programs like PowerPoint that understand images to get the image directly while permitting programs like our note editor to get the same image in the form of a snippet of HTML. Unfortunately, we discovered that the HTML version was confusing a number of other programs (in particular, the Office apps), causing some to refuse to paste and others to go through some kind of weird, paranoid security dance. Hopefully this will work better.

Installing PocketBible to a New Device

Posted on: December 26th, 2015 by Michelle Stramel 9 Comments

Are you the happy recipient of a new phone or tablet? Or a new Mac or PC? Congratulations! Here is what you need to know to get PocketBible on it!

First an important reminder – you never have to re-purchase any Laridian Bibles or books when you move to a new device. You may have to re-install a new version of PocketBible and download your books again but that is all FREE and we’ll try to make that as painless as possible with the tips in this article.

Install Guide by Device Type

Find your device type in the list below and follow the instructions from there:

  • iPhone/iPad/iPod touch (iOS) – go to the App Store from your device and search for PocketBible Bible Study. Download the free app and register it using your existing Laridian ID (or email address on file) and password. Tap on the Menu icon and choose Add/Remove Books. Go through the list of your books (should include all your previous purchases and free books) and tap on any you want to download at this time (you can always return to this list and download more later). Hit UPDATE at the top of the page to start the downloads.
  • Mac OS X – you can download PocketBible for Mac directly from our website. Go here to download and here for detailed directions. The first time you open PocketBible on your Mac, register using your existing Laridian customer information. Then you can select Cloud Library from the Books menu to download your past purchased books.
  • Android OS – go to the Google Play store on your device (or Amazon App store if you prefer) and search for PocketBible Bible Study. Download the free PocketBible app. Register using your existing Laridian account information. Tap on the Dove icon and choose to Download Books. You should see your previously purchased titles along with all free books. Tap on each book you want to download (you have to do this one at a time). Check out our Android OS videos at our Youtube channel for some tips on using PocketBible for Android.
  • Kindle Fire – we are still working with Amazon to get our Android version of PocketBible to show up in the Kindle Store. In the meantime, follow the instructions at this link to download PocketBible from our site and install as a 3rd party app. HDX owners you can watch a video of how to install.
  • Windows Phone – Microsoft hides most of the free apps on their app store even if you search by the exact name of the program. The best way to find PocketBible for Windows Phone is to select a link on our site, like this one. Download the free PocketBible app for Windows Phone and install it. Register using your existing Laridian account information. Choose the Cloud Library from the menu. Tap on any title to download. Open downloaded books from the Device Library.
  • Windows Surface or Windows 10 – Like the Windows Phone Store, Microsoft hides most of the free apps for Windows. The only way to find apps is if you already have a link to them. You can download PocketBible here. It’s free. Run it, then register using your existing Laridian account information. Choose the Cloud Library from the menu. Tap on any title to download. Open downloaded books from the Device Library menu.

If you have personal data (i.e. notes, bookmarks, highlights) to transfer from an older device, first sync the data from the old device to our server (you can do this manually if you haven’t been doing it automatically), then enable automatic synchronization on your new device. Do a manual sync the first time to make sure you have all the data.

One final note – Advanced Feature Sets are sold separately for each operating system. So, for example, even if you own the Advanced Feature Set for your iPhone, you’ll still need to purchase the specific Advanced Feature Set for your Surface Pro or Mac OS X. However, if you own an iPhone and iPad, since they are the same operating system, you only need one copy for both devices.

PocketBible 3.4.0 for iOS Available at the App Store

Posted on: November 3rd, 2015 by Craig Rairdin 2 Comments

PocketBible iOS IconApple approved PocketBible 3.4.0 on Monday. The motivation for this update was support for iOS 9 multitasking (“Split View”) on the newer iPads. Of course we took advantage of the update to roll out some new features and enhancements at the same time.

Version 3.4.0 adds Passage Actions to the main menu. This gives you a way to copy, share, or print a verse or passage without actually going there first. I use this to grab verses to insert into sermon notes without losing my place in the Bible.

A number of features were added for new users to ease them into the admittedly complex PocketBible navigation methods (such as swiping from right to left to turn a page, just like a book and just like every ebook app). A new Welcome to PocketBible slideshow is triggered when the program is launched without having previously been registered. It introduces the basic functionality of the program. And the navigation overlay has been enhanced to remind you that you can also swipe instead of tap to navigate.

Version 3.3.7 eliminated the need to purchase voices to take advantage of audio features of the program, but introduced a bug that made it impossible to choose between two voices in the same language. Version 3.4.0 fixes this issue. We also discovered that iOS 9 voices speak more slowly than the same voices in iOS 8, so we changed the default rates and gave you more rate choices if you’re running iOS 9.

You can read the full list of new features, enhancements, and bug fixes when you download the update from the App Store. Or, you can read it below.

What’s Next?

Next up will be a fairly significant update to PocketBible that I’m tentatively planning to call PocketBible 4. We think the new version will be easier to use and will introduce some new features in the Advanced Feature Set that will make the AFS more valuable for those of you who choose to purchase it.

You should note that we plan to raise the price on the AFS at some point in this process, so now is the time to upgrade if you haven’t already. You can do so from within the app, but it’s cheaper to do it on our website. After purchasing the AFS on our site, just choose Buy/Apply Upgrade from the menu in PocketBible to enable the advanced features.


  • Support for iOS 9 multitasking (Split View)
  • Added Passage Actions to the main menu for easily copying or sharing any verse or range of verses without first finding the passage and selecting it in the text.


  • New Welcome to PocketBible slide show for new users.
  • Touch zone overlay now shows swipe direction in addition to the functions of each touch zone.
  • Add Share to the press-and-hold menubar to give quicker access to sharing selected text.
  • Leave the Note Viewer open on the iPhone when following an external (Web) link. Makes it easier to get back to where you were.


  • Show iOS 9 voice names so that you can choose between two voices in the same language and locale.
  • iOS 9 voices are slower than iOS 8 voices were. Changed the rate options for iOS 9 so that voices sound more natural at the “normal” rate.
  • Make sure status bar background and text colors gets set correctly.>
  • When copying/sharing text, do not include the “Note” marker at the beginning of a verse that has a user-created note. Also, do not include translator’s footnotes.
  • Don’t use the Context menu Share submenu for non-Bibles, as it will have only one item in it. Just do Share Selected Text directly.

Greek New Testament Available for PocketBible for Android

Posted on: November 2nd, 2015 by Craig Rairdin 4 Comments

As you may know, Laridian offers the SBL Greek New Testament for PocketBible on all platforms except Android. This was due to lack of decent Unicode support in Android before 4.4.

Now that we’re at the point where most of you are running Android OS 4.4 or later, we decided to go ahead and make the SBL Greek New Testament available for this platform. You’ll find it in your list of available downloads when you go to Download Books in the app.

If you’re running an earlier version of Android, you can still try installing and using this book, but you will find little rendering problems depending on your version of the operating system. We can’t do anything to fix these. And users of 4.4 and later may also discover little rendering issues but we’re not aware of anything major.

Thank you for your patience as we waited for the OS to mature. :-)

PocketBible and Android OS 6 (“Marshmallow”)

Posted on: October 12th, 2015 by Craig Rairdin 8 Comments

[EDIT: These problems have been fixed. If you’re having trouble with OS 6, make sure you’re running the latest verson of PocketBible.]

We are in the process of fixing some problems that keep PocketBible from running correctly under the latest release of Android OS.

The core of this problem is our valiant attempt to continue support for older devices for as long as we can. Both iOS and Android OS tend to be advanced without due diligence paid to compatibility with older versions of the operating system. Here at Laridian we’ve been long-time believers in not abandoning versions of operating systems that our users are still running. However, the practice of our industry is to drop support for devices older than about two years (the length of the typical cell phone contract) and since the companies that create the operating systems also create the tools we use to develop PocketBible, it is often impossible to do anything but go along.

Android OS 6 is incompatible with certain features of PocketBible that are there to support pre-4.x devices. We’re in the process of removing support for those operating systems and will release an update as soon as possible. In the meantime, there is no work-around short of not installing OS 6.

PocketBible for iOS 3.3.7 Approved by Apple

Posted on: October 1st, 2015 by Craig Rairdin 3 Comments

PocketBible iOS IconPocketBible for iOS, version 3.3.7 was approved for distribution in the App Store this afternoon. You should be notified when it is available to you.

New Features

The new iPhone scrolling toolbar makes more features instantly accessible without accessing the menu. Flick the toolbar left or right to slide the toolbar and reveal more functionality. We’ve added direct access to your list of notes and highlights, the Settings menu, and other features that were previously only on the iPad toolbar (which is larger and therefore had more room for more buttons).

There’s no longer any need to purchase voices to use the audio features. The Advanced Feature Set now uses built-in iOS voices and allows you to set pitch and rate of speech. The program will automatically remove any of the old voices it finds to free up space.

We’ve made it easier to share Bible verses to Twitter, Facebook, and other social media. Select your text then choose Share from the Context menu. Now, one problem that most people don’t realize is that Facebook recently changed its policies so that apps cannot pre-populate your status text. This policy is enforced through the Facebook app. So if the Facebook app is installed, your verse text will not show up in the status field when you choose to share on Facebook. Instead, either remove the Facebook app (!) or simply use “copy” in PocketBible to copy to the clipboard, then paste into the Facebook app. We agree this is, well, dumb. But, hey, it’s Facebook, right?

You can now include links to websites in your notes. These links may not be honored on other platforms if you sync your notes, but they will work on the iOS version on all your devices.


The free version of PocketBible now supports text selection for copy and other operations. Previously, only entire verses could be selected.

Searching for selected words, or doing a dictionary look-up of a selected word is easier. After selecting text, you’ll find “Find” and “Look Up” on the menu bar (along with “Copy”, of course). It’s the same number of taps as before, but it is easier and quicker to find.

Advanced Feature Set users will notice the confusing Selection Actions menu is gone. The functionality of that menu has been integrated into the Context menu. Instead of listing every operation separately (“Copy Selected Text”, “Copy Selected Verses”, and “Passage Action”, for example), we only list the “actions” (“Copy”, “Highlight”, “Share”, etc.). Under those we give you a choice of what you want to act on (“Selected Text”, “Selected Verses”, “Passage”, etc.). This makes the context menu shorter and easier to navigate. In some cases it adds a tap, but the overall improvement in usability is significant.

Bug Fixes

A number of bugs and misbehaviors were addressed. None of these were show-stoppers but some were annoying. For example, the go-to-verse buttons on the iPad in landscape orientation were too small, and the download progress bar would sit at zero until 100% of the book was downloaded.

What’s Next?

Next up we’ll be looking at two major tasks: First is evaluating the best way to support the multitasking features of the new iOS 9 devices. Best case, it will require a little additional programming. Worst case, it will require a redesign of major portions of the program. It’s not clear yet where we’ll fall on that spectrum. Second, we’ll be bringing a couple features of the Mac version into the Advanced Feature Set of the iOS version. We’ll have more to say about that soon.

Laridian Website – Server Migration Post-Mortem

Posted on: August 5th, 2015 by Craig Rairdin 10 Comments

Update – Aug 5, 2015 – We discovered that the sync server wasn’t running, so you weren’t able to sync your user data even after the DNS changes propagated. This has been fixed. If you had trouble synchronizing your notes, highlights, and bookmarks, try again.


This article will mean very little to most of you but some of you might find it slightly interesting.

I don’t like to get off a perfectly good horse midstream. Windows Server 2003 and SQL Server 2000 have been serving us well for a very long time. But Microsoft discontinued support for  Windows Server 2003 last month and that means no more security updates. As a result, our next PCI security scan was doomed to fail, which doesn’t mean your personal data would be at risk (any more than passing the PCI scan protects the data), but it doesn’t make for good PR.

(PCI is the Payment Card Industry and the scan is required to meet their card security standards. Laridian doesn’t store your card data so the requirements for us are pretty light. You’re at significantly more risk when you hand your card to the clerk at Target, and we all know from experience that even though they passed all the security scans it didn’t do them much good.)

Upgrading to Windows Server 2012 and SQL Server 2012 meant physically moving the contents of our servers to new hardware, and as long as we were doing that, we decided to shop around for better pricing. We found it at, which offers the type of dedicated server solutions that we need. And they do it for half the price of the company we had previously been with.

Laridian maintains several large databases. These contain your customer account, your transaction history, all the user-created data you’ve sync’ed to the Laridian Cloud, and the downloadable files that make up our books and Bibles. In addition to those we have a couple others for in-house purposes. Because SQL Server 2000 is past end-of-life, those databases could not be imported directly into SQL Server 2012. We had to first import them into a SQL Server 2008 instance, then import that to SQL Server 2012. The good news was that having done that, the databases functioned exactly the same. In fact, we were able to simply point the old website to the new database, and it would work just fine.

Let me pause for a minute to say this: We cannot build PocketBible 1.0.0 for iOS anymore. Not only would the resulting program not even come close to working on iOS 8, it would fail in the compilation and linking process. PocketBible 1.0.0 was released in September 2009, just six years ago.

Contrast that with the code that runs on our website. In 1998, we contracted with Jomax Technologies — Bob Parsons first Internet company, before he founded GoDaddy — to create our e-commerce site. There is a significant amount of code dating from 1998 still running on our site, especially on our back office site, which is where we generate sales reports, create new product pages, and define priority codes. This code is running unaltered seventeen years later, accessing a database that has been in continuous use for all those years.

When you hear me complaining about the unnecessarily rapid pace of development from Apple (and other companies who drive our industry) and how they create problems due to their lack of regression testing and backwards compatibility, this is what I’m talking about. Because Microsoft knows it would be a huge problem to break millions of websites, they go out of their way to continue to support the technologies on which the internet is built.

But I digress…

This move took place over about a four-week period. (I actually thought it would take twice that long.) The first step was to move the system we use for source code archival (SourceGear Vault). This was necessary because we use Vault to maintain the website. We check code out of Vault, make our changes, and check it back in. Vault populates the website folders from the files we check in. It would be most convenient if we could continue to do this the same way on the new website.

Because we were running Windows Server 2003, we couldn’t upgrade to the latest version of Vault, which requires Windows Server 2008. And because we were running such an old version of Vault (version 5) we couldn’t upgrade to the latest (version 8) directly. We had to first upgrade to version 6, which upgraded our database, then upgrade to version 8, which upgraded it again. With Vault working on the new server, we were able to move software development and book production to the new server within about two weeks.

Prior to moving Vault we had captured a snapshot of the websites and databases and were running those on the new server for testing. This allowed us to do a quick test to verify that the Web pages themselves would run under Windows Server 2012 and IIS 8. They worked just fine.

Next, we knew that during the transition to the new site there would be a period of time while DNS changes were propagating during which we would have to access the new database from the old website. We ran some tests that verified this would work.

Last, we had to build the Laridian Sync Server Service code with Visual Studio 2015 and verify it worked. It did.

At this point we spent a couple days locking down the firewall settings. We had a period of just a few hours when we had an open SMTP (email) server that was exposed to the outside world. I was shocked by how quickly the spammers discovered it (by literally rifling through IP addresses and sniffing for servers). We worked with SingleHop to quickly lock that down.

Now we just needed a procedure to follow for getting a final copy of the database moved to the new host. The problem was that we couldn’t be writing to it while it was being moved, which meant shutting down all commerce, account updates, product registration, and user-data synchronization for some unknown period of time. SingleHop estimated two hours to move the database, but suggested we allow three. I allowed four. (It took five.)

Once we knew what needed to be done, we picked a convenient date and time to do it. We were able to configure much of the code to just shut itself down at 8AM CDT the day of the migration. So, for example, the code to do synchronization of user data from PocketBible for Windows would still be there waiting for connections, but starting at 8AM (7:30, actually) it would return an error code to the client saying that the site was down for maintenance. By automating that process, it meant there were fewer manual actions that needed to be taken in the moments before the migration began. In fact, by the night before the move we were down to where it would take only ten check boxes and about 3-4 button clicks to completely bring Laridian to a stop for the two, three, or four (or five) hours it would take to move the database.

The morning of the move, I discovered SingleHop had left themselves logged into a server, which blocked me from getting in to click on two of my ten check boxes. I asked them to do that for me, which was not a problem. Then I discovered that the person who I was told would be doing the migration hadn’t been told about that fact until 30 minutes after the migration was to have begun. He was rousted out of bed or wherever he was, and started moving the databases.

With that small hurdle overcome, and with the website having automatically stopped processing new transactions to the database, I was able to get in and make three lines of code changes that it took to point the old website to the new database server. That was really all I needed to do during the time while the database was being exported from SQL 2000, imported to SQL 2008, exported from SQL 2008, and imported into SQL 2012.

The last step of the move was to make the DNS changes required to point everyone to the new server. It was at this moment that our registrar (GoDaddy) decided to make buggy changes to their website that kept us from changing our zone file. After two or three hours of attempts, we were finally able to get those changes made.

In the end the move turned out to be easier than I thought and was significantly less time-consuming than I had anticipated. I’m sure we’ll discover small things that are broken, but the major functionality of the new servers appears to be working.

Thank you for your patience during the move.



Laridian Website – Planned Outage

Posted on: August 4th, 2015 by Craig Rairdin 3 Comments

The server migration we did this morning (Tuesday, August 4) is complete as far as we can tell. The last phase of it is changing the various DNS records for our various sites so that they point to the new server. That has been done, but it takes time for the changes to DNS to propagate throughout the Internet.

Until that time, you’ll see a yellow marquee banner across the top of pages at and you won’t be able to sync your user data. If you see the yellow banner, the site will be slow because it’s talking across the wire to the database server instead of having it located “right next door” on its own subnet in the same building. Once the DNS change finds its way to your machine, you’ll be back up to full speed at the new site.

I’ll write up a little post-mortem article for the techies among you just for fun.

If you have problems with our site that don’t fix themselves by Wednesday, August 5, drop us an email at

Reason for the Outage

Laridian operates services on a variety of servers located at more than one hosting company. From time to time we move these services to new locations either to enhance their capability or to save money or both. We are generally able to do this in a way that minimizes or eliminates downtime. In this case, we are moving our database server, which stores almost everything of importance at Laridian including your customer account, transaction history, user-created data (notes, highlights, and bookmarks), and all our books.

It wasn’t possible in this case to make this transition without actually stopping all updates to the database, copying the data to the new server, and restarting it at its new location. During this brief time, we couldn’t do any operations that cause the database to change, or we risked losing those changes (i.e. they would get written to the “old” location after the database has been moved to the “new” location).


Once this whole process is complete, we expect enhanced performance of the website, sync service, downloads, and other related services. Security of all of these services will be increased. And despite the more powerful hardware on which this will all be running, our costs will be lower. This will allow us to continue to produce Bibles and reference materials at prices at or below what you’ll find elsewhere.


2:45PM Remaining DNS changes complete.

1:35PM Laridian Cloud sync services are back up. The IP address for synchronization has changed, so you may continue to get the “maintenance” message (or not be able to connect at all) until DNS changes propagate to your server. This could take up to 48 hours but in our experience most of you will see the change within a couple hours of it happening (which was actually a couple hours ago).

12:00PM Domain registrar is up and down. We have been able to make some DNS changes, but not all.

11:15AM Our domain registrar chose this time to go down. Of course. This isn’t a big deal, it just means that the sites will be slower. Once we can make DNS changes, the websites and the database server will be on the same subnet. Until then, the websites have to talk across the wire to the database, which means they’ll be slower. The worst part of this is that user data synchronization (Laridian Cloud) can’t be brought back up without changing DNS. We don’t anticipate this will take long.

10:45AM Commerce, product registration, account updates, and Apple App Store in-app purchase downloads are back online. The only thing currently offline is the Laridian Cloud (user data synchronization).

PocketBible 1.x.x for iOS users: If you got a message while trying to sync that said “You’re running a very old version of PocketBible“, it’s because you’re still using version 1.x and we’re currently on version 3. To upgrade, first sync (not just backup, but sync) your user data with the server after this maintenance is over. Then search the App Store for PocketBible. The program is free. Download and run it. Register using the same customer ID and password as you have been using, then turn on automatic synchronization under Manage My Data in the menu. The program will pick up your notes, highlights, and bookmarks and you’ll just have to download your Bibles and reference books.

8:30AM Migration officially started.

8:00AM Commerce, account update, PocketBible 2.x/3.x sync service, and other related services disabled.

7:30AM PocketBible for Windows and PocketBible 1.x sync services disabled.

©2016 Laridian