PocketBible for Windows Progress Update #2

More Rewards Distributed

The 2021 editions of the PocketBible Library Collections are being released coincident with this status update. If your reward package included the Bronze, Silver, Gold or Platinum Library, you’ll find those books are now in your account. The special Diamond Edition for those at the higher contribution levels has also been distributed, though of course it’s not available to the public. You can download any new books from these collections using the Cloud Library feature in PocketBible.

Note that the 2021 editions contain some Bibles that are not compatible with the current Windows versions of PocketBible, particularly The Passion Translation, World English Bible with Strong’s Numbers, and the Spanish Nueva Biblia de las Américas. These will work in PocketBible on other platforms.

Note further that the collections include the very recently released 2020 edition of the New American Standard Bible. The publisher has said we can continue to offer the 1995 edition, but we need to refer to it as “NASB1995” and call the new version “NASB”. Since the Windows versions can’t be updated to use the new abbreviation for the 1995 edition of the NASB, you will end up with two Bibles both called NASB. In the Windows Desktop version you could potentially have 4 tabs labelled NASB, NASB, NASEC, and NASEC (the latter two being the NASB with Strong’s Numbers). You’ll find if you hover over the tab you’ll be able to see which one it is. In other places where you’re choosing from two versions with the same abbreviation, you’ll see that “1995” or “2020” has been added to the title so you can tell which one each is.

Diamond Edition Contents

Because the 2021 Diamond Edition is not available to the public, there’s not an easy way to see what it contains. This collection, which was offered as a reward for those who contributed $720 or more to the project, contains everything in the 2021 Platinum Edition plus:

A Hebrew Word for the Day
Ancient Christian Commentary Series
Bible Reader’s Companion
Bible Teacher’s Commentary
Dake Study Bible Notes
Ephesians: Reformed Expository Commentary
Gospel Transformation Bible Notes
Greek New Testament Collection
Knowing the Bible Series
Maclaren’s Expositions of Holy Scriptures
Preaching the Word Series
Systematic Theology Study Bible Notes
The Good and Beautiful Community
The Good and Beautiful God
The Good and Beautiful Life
The Sermon Notebook
Understanding the Bible Series

The total value of all these books sold separately is over $4000. Thank you again for your support!

Progress Update

Work continues on two fronts: Implementing features related to what we call “user data management” (notes, highlights, bookmarks, and daily reading progress), and translating the code at the core of PocketBible that reads and acts on PocketBible books and Bibles.

We’ve completed much of the nuts and bolts of user data management and have begun to work on user interface issues related to those features. For example, neither the Windows Store nor the Windows Desktop version of PocketBible allows you to set bookmarks on more than one verse at a time. (To be fair, neither does the Mac OS version.) But the iOS version recognizes that you have multiple verses selected and assumes you want to set or clear bookmarks on all (or at least some) of those verses. We prefer this behavior and want to introduce it in the new Windows version.

This is what we meant when we said that we would draw on our experience with the Mac OS and iOS versions when writing the new Windows version. Not that we were going to duplicate either one, but that we would allow what we’ve learned while experimenting with different ideas on those platforms to influence how we re-imagine the Windows version.

I’ve said before that we’d be building the new version using a different programming language, application framework, and toolset. So porting the shared portions of the code — functionality like being able to read and operate on our Laridian book (LBK) files — is mostly a “translation” task. This is not entirely true, as certain concepts are very different between the two languages, as are the syntax, idioms, and data types.

To give you an idea of the size of this task, I counted this morning (automatically, not by hand) the number of lines in the shared C++ code and it came to 457,326 lines. That’s about 8000 pages if you were to print it out. All of that code has to be read line-by-line, translated (taking into account changes made to other parts of the code during translation), and tested.

We continue to make progress in this area, though I believe we’re only about 10% to 20% through it. For example, the program is now able to detect the books you have installed and allow you to select from among them — though once you open a book, you’re not able to read text from it. The text we see on the screen is simulated — biblical lorem ipsum so to speak. I’m working on that portion of the code right now.

PocketBible is on MeWe

With more PocketBible users making the move from Facebook to MeWe, we thought we should be there, too. We’re not leaving Facebook, just adding a MeWe page. You can click here or search for PocketBible on MeWe. When you find us, follow us.

For those of you who have never heard of MeWe, it’s like Facebook except without the ads and the censorship of certain points of view. It’s free like Facebook, but you can get access to premium features for a small fee. The free version seems to work great, though.

We’ve been happily posting on Facebook since March 2008 and have no plans to leave. We have, however, left Twitter and have no plans to return. It didn’t really fit our needs, nor, apparently, the needs of the majority of PocketBible users.

PocketBible for Windows Progress Update #1

As you know, our crowd-funding campaign for PocketBible for Windows ended on September 15 so we’re about one month into the project. While I can’t demonstrate much for you at this point, I do want to fill you in on our progress and answer a few questions.

Over the last couple of years we’ve experimented with a number of programming languages, frameworks, and development tools to try to discover the best way forward for PocketBible for Windows. In the process, we’ve explored some proof-of-concept ideas, some of which will find their way into the finished product.

For example, we needed to be able to display and interact with books with complex layouts, like The NIV with Goodrick-Kohlenberger Numbers and our parsed interlinear Greek New Testaments. You would think that displaying formatted text would be trivial these days, given that it’s 2020 and even Web browser technology from the last century can do it fairly well. PocketBible for Android, iOS, and Mac OS uses HTML rendering built into those platforms that does a very good job. Unfortunately, the similar functionality built into Windows is significantly less capable. So as we explored alternative tool sets for implementing PocketBible for Windows, this is one of the areas we focused on. Our ability to successfully render these complex layouts during our experiments in the summer of 2019 is what led us to settle on our current solution. (We’ll have more to say about that in a future update).

Now that we’ve demonstrated that we can display and interact with the text, we need to be able to extract the text of a book or Bible from our Laridian Book (LBK) file format. The code that does that is fairly extensive and complicated and needs to be translated from its current implementation and thoroughly tested. We’re currently working on that task.

A major area of progress is what we call “user data management”, which is keeping track of your notes, highlights, bookmarks, and daily reading progress. In particular, we wanted to tackle synchronization of that data with Laridian Cloud. This would force us to fully implement the ability to read and write the data from and to the database, and would also require us to solve communication with our cloud-based sync provider — both of which are complex tasks that introduce risk into the schedule. Overcoming those challenges and dealing with that risk during the early part of the project avoids the possibility of unexpected delays right before our ship date, when it is least-practical and most-expensive to deal with it.

As of today, even though the PocketBible app for Windows doesn’t allow you to view or edit notes, it can sync its local notes database with the server. You can’t even see any verses, let alone select one to highlight, but you can correctly sync highlights to and from the cloud. This means we’re able to populate the local database from a customer account, make manual changes using a database editor tool, then request that the program sync again. The app accurately identifies what has changed and syncs those changes to the server. At the same time, it receives and records any modifications or new records sent to it from the server. That means that, at least internally, everything is working. There’s just no user interface to it yet. Sounds weird, but it’s very normal for a software project to be completely working but with no way to see that it’s doing so. That will come later.

It’s also worth noting that even though neither of the current versions of PocketBible for Windows (Windows Desktop or Windows Store versions) support Journal notes or renaming highlight colors (features of the Advanced Feature Set in PocketBible for iOS, Android, and Mac OS), the new version already supports those features. Or rather, the underlying support is there; there’s just no user interface to invoke it.

Until next time, thank you so much for your financial support, prayers, and words of encouragement for this project. We welcome your feedback and suggestions.

Frequently Asked Questions

What will be the effect of the Windows project on work being done on other platforms?

According to comments on a recent customer survey we did, some of you have expressed concern that our attention to the Windows project will take away from work on other platforms. I want to reassure you this is not the case. In fact, the very purpose of the crowd-funding campaign was to allow us to add staff for the Windows project in order to minimize the impact on other platforms. You may not realize it, but you’ve already seen the results — we shipped a new version of PocketBible for iOS coincident with the release of iOS 14, which introduced a number of major new features for PocketBible on that platform, all while work on PocketBible for Windows continued unabated.

When will I get my rewards?

When you get your rewards depends on what type of rewards you are entitled to.

Physical Rewards: Three contributors were entitled to some special rewards (a 1903 KJV New Testament and two framed, first-edition KJV pages from 1611). These were mailed within a week of the end of the fund-raising campaign.

2021 PocketBible Library Collections: Contributors at the $60, $120, $240, and $360 levels will get the 2021 Bronze, Silver, Gold, and Platinum Edition PocketBible Library collections, respectively, when those products are released near the end of the year.

Special Diamond-Level Library Collections: Contributors at levels $720 and above will get the special collection we’re putting together just for those contributors. It will be released either at the same time as the regular 2021 Bronze, Silver, Gold, and Platinum collections are released, or shortly thereafter. We’re aiming for having all of the collections distributed by the end of the year.

Advanced Feature Set Subscriptions: Some contribution levels included multiple years of either the AFS for the new Windows app or for all platforms. Those will be distributed when the new app ships. We haven’t announced a specific ship date but are aiming for late summer, 2021. Obviously, those who are entitled to a mention in the in-app credits will see that when the app ships.

Wait… Isn’t that a Mac in the picture?

Yup.

Americans Lack Basic Understanding of the God of the Bible

The Cultural Research Center (CRC) at Arizona Christian University released a study last week showing that Americans demonstrate an increasing ignorance of God and in some cases hold self-contradicting views of God’s attributes and actions.

The survey of 2000 adults was conducted in January, 2020 to determine the percentage of the country that holds a biblical worldview. It found that only 51% of Americans believe that God is the “all-powerful, all-knowing, perfect and just creator of the universe who still rules the world today.” This is down from 73% who agreed with that statement in 1991.

The largest drops are among the youngest (under 30) and the oldest (over 75) among us. There is also a clear divide along political lines, with self-described liberals and Democrats holding the least biblical worldview and conservatives/Republicans, the most. Agnostic (“there may be a God, but we can’t know for sure”) and atheistic (“there is no God”) views have grown substantially in the last 30 year.s

Some contradictory views also come out in the survey. 45% who claim God exists also say they can’t be sure. This would actually seem to be more consistent with an agnostic view. One-third of those who old a biblical view of God way that he has no reason behind what he causes or allows to happen to them. One could argue that an irrational God is little better than (and certainly more frightening than) no God at all. Only 1/3 of those who believe in the God of the Bible say that he is involved in their lives. Again, a God who doesn’t care about us seems little better than no God at all.

Slightly more people believe in the biblical person of Satan than in the biblical person of God. Think about that for a while.


PocketBible can’t fix a person’s ignorance of God or of God’s character on its own, but it can give you the tools you need to repair your own understanding of God and help you share a biblical worldview with the people you live and work with. And this survey reflects only the opinions of Americans, where Christianity allegedly has its best foothold. There is no lack of work to be done, starting here and throughout the world.

We’re not virtual anymore!

If you’ve ever visited the About page on our website in the past, you may have read:

This is as close as you’re going to come to visiting our “facilities”. Laridian is a virtual corporation where employees work from their homes. Currently we’re spread out over three states. We rely heavily on electronic means of communication, though those of us working in our hometown of Cedar Rapids, IA frequently meet in person just to keep from going crazy, if nothing else.

Well, times have changed and we’d like to officially announce that we have left our home-based, coffee shop, Skype’ing days behind us for a physical location where we all work together in one office in Cedar Rapids, IA. Yes, there are a few unhappy coffee shop owners in the area but for Laridian it has been a great move. We all loved the perks of working from home (i.e. optional showering, work in your pj’s) but now, having tried the alternative, we have to admit that there are some definite advantages to working together in the same building. We’ve already seen improvements in productivity in every area of the company. And as far as communication goes, we only have to get up and take a short walk to find out what is going on with a co-worker. We’ve replaced our “virtual” reality with a “new” reality that isn’t half bad and might just be worth having to take a daily shower.

Why the change? Until this summer we had used a number of outside contractors and companies to create the books and Bibles that go into PocketBible. When this process was working, it worked well. But recently, two of our best outside contractors had changes in their situations that robbed them of the free time they were devoting to tagging books. As a result it was taking longer and longer to get finished books. So we decided to bring this operation in-house. In addition to having more control over the schedule, we thought it would be easier to manage.

When putting together the budget for the new employees, we decided to include office space, office furniture, computers, internet connections, and everything else we’d need to operate a “real” office. It turned out the cost wasn’t really that bad, and the benefit of having the new people sitting right next to seasoned veterans made training a breeze. So we rented some office space close to Craig and Jeff’s house, then hired the editors. The result is that you saw more new titles from us in the last quarter of 2011 than in some previous entire years.

Just this month, the last of our home-based employees moved into the office with us. Yesterday, we made it official by putting a sign up on the door telling the world (and the FedEx driver) we’re here. So you won’t find us out in the virtual world any longer – we’ve come down to earth and we hope it will be for your benefit.