PocketBible for Windows Progress Update #4

I apologize for the delay getting an update out. We get busy and we are always thinking that after we implement the next big thing would be a good time for an update. Next thing you know several big things have been implemented and no update.

Since the last time you heard from us:

Notes can be edited, saved, and sync’ed to the server. The note links in the text open the note in the editor.

Bookmarks can be created and lists of bookmarks in a given category displayed. You can select a bookmark to go to it in the text.

Highlights can be created but they’re not yet visible in the text. You can see a list of them and select from the list to go to the verse.

The option to sync Bibles and commentaries has been implemented, so commentaries and other Bibles will follow along as you scroll through the Bible text. There’s a separate option to sync dictionaries so that any request for one dictionary to go to an article for a word will result in all dictionaries responding, and another option for all devotionals to go to today’s reading when any one devotional goes to today’s reading. Here’s a little demonstration:

The scrollbar is implemented. As you drag the scroller up and down, there’s a tooltip that tells you where you’re at in the book. When you release the mouse button, the text goes to that location. There’s an option to scroll by pages or scroll by chapters in the Bible. Other types of books have similar options.

The program saves its display state, window size, and position between sessions. If  you have more than one monitor, it remembers which monitor it was on. If you unplug a monitor or switch to one with different resolution, it adjusts its size and position accordingly.

There are other little things that get done along the way, of which I may not have made a note.

We’re currently working on implementing searches. There are interesting technical challenges porting that code from Mac/iOS/Android to our environment in Windows. On the other platforms we launch a dozen parallel activities to perform a single search. The Electron environment is single-threaded. There is a way to create multiple processes but the communication between them is rudimentary. We’ve settled for trying to make it so the user interface (mainly mouse movement and interaction) doesn’t stutter during a search, but searching may be more of a serial, rather than a parallel, operation. I’m guessing nobody will notice. Searches will still be fast.

An interesting complication that arose during implementation of searching was being able to support finding words with the same root word as the one you are looking for. The algorithm that reduces words to their root words is written in an esoteric programming language that was created specifically for this one purpose. In order to translate that language into what we need (Java for Android, C for iOS and macOS), we have to use a custom transpiler that converts from the weird root-word language into Java or C. The new version of PocketBible is being written in JavaScript, which would require that we write a custom back-end for the transpiler. This was disappointing as we figured it would take several days, if not more, to implement. Fortunately, the next day we found that someone had already converted the code by hand to JavaScript. We added our modifications to support Early Modern English (KJV language) and we were back on schedule.

One of the things that happens during development is that you sometimes get to do things twice. We were using a very basic method of displaying lists like your list of bookmarks, notes, and highlights. This method worked fine (and is working now) but in those rare cases where you have 20,000 search results, it will get bogged down. So we’re replacing the already-working list mechanism with a new one. It’s one of those things that, once it’s done, you won’t notice the difference. But it requires careful surgery to remove one method and replace it with another. This is being done to support search results but other areas of the program will benefit. Most people don’t have 20,000 bookmarks, but for those who do, this will be a noticeable improvement (at least it would be noticeable if they had seen it before and after, which they won’t.)

As some of you know, last August our city was hit by a rare wind storm known as a derecho. Sometimes called a “land hurricane”, a derecho has straight-line winds that exceed 100 MPH. Our city experienced winds as strong as 140 MPH. And while a tornado has stronger winds, it generally only affects a narrow path, maybe a couple hundred yards wide. This derecho caused wind damage over an area 100 miles wide and 700 miles long.

The office build we were in took significant damage. The roof had to be replaced along with all the flooring, all the ceiling, and a good portion of the walls. We were able to continue working there while roof repairs were made and most of the interior was removed, but in mid-February we had to move out. We spent 3+ months working from home with some negative impact on productivity. Then in mid-May, a new office suite became available just 2 blocks from our old location. By the end of the month we’ll be in a beautifully restored 19th century building with exposed brick walls, original wood floors, and 12′ ceilings.

That’s where things stand as of today. Thank you again for your interest and support of this project.

“I heard that the author of that book eats babies. Are you going to drop their titles?”

From time to time, some controversy will arise over something an author publishes with which some faction of Christianity disagrees. We’ll get emails from users requesting that we drop that author’s work from our product line. Often they point out that this author has previously been associated with some other Christian leader, whose work we also publish, and that we should drop that person’s work, too. Our response has always been the same.

We are a book store, not your pastor or spiritual mentor. We stock a wide variety of doctrinal perspectives. We base our publishing decisions a lot on what our customers request. We don’t want to waste our time creating a book nobody wants.

We trust you to choose material based on your own research. We don’t select books for you; we merely provide them for you to select from. If you don’t like the doctrinal positions of a particular author, don’t buy their books. There are plenty of others.

No author is perfect. No reader is perfect. We’re not perfect. If we refused to distribute books from authors with whom we disagreed on a minor point of interpretation, and if we refused to sell to people who have ever sinned, we would have to shut down and go live in the woods. We’re not going to do that. We’re not going to compel everyone around us to comply with our standard of belief and behavior; we have trouble enough following it ourselves.

So thanks for thinking of us, but we don’t participate in this type of debate and character assassination. Never have.

Photo by Fred Kearney on Unsplash

Trying Not to Panic Over Updates to the Bible

Recent updates to the New American Standard Bible, Christian Standard Bible, and, less recently, the New Internatlional Version, English Standard Version, and Amplified Bible have awakened discussion about the possibility of introducing error or succumbing to pressure to conform with the world when updating the English Bible.

There is a lot of misinformation out there about new translations. Christians are put in a very awkward position and most don’t realize the nature of it. On the one hand, we have language, which is continuously evolving. This evolution is relatively slow, but not so slow that you can’t see it if you’re looking for it. Those of us with more than a couple decades under our belts can definitely see changes between how the language was spoken in our youth vs. how it is spoken now. On the other hand you have the Bible, which we hold in high esteem and which we believe to be (or contain) the very Word (or words) of God. We can’t imagine God not expressing himself perfectly the first time, and just assume that our English Bibles should be just as unchanging.

When looked at in the big picture, we understand that we need a Bible written in our native language, and that by that we mean not just English but Modern English. We can probably understand the Great Bible (1540) and King James Bible (1611) but not in their original blackletter font and Early Modern English orthography. Even the vaunted 1769 and early 1900’s editions of the KJV that many Christians cling to as the Bible have been significantly modernized in order to be readable. Despite this innate understanding, we are at least slightly repulsed by the idea of “updating the Bible”.

It’s when we start to act this general understanding (that is, that we need a Bible written in our native language) that we get into trouble. One of the big problems is gender language. Because it’s a politically sensitive issue, there’s a feeling like the Bible should be above it. But setting aside where our personal politics lie, we have to admit that we want an accurate translation of the Bible. The fact is that the biblical languages do not convey gender in the same way English does, and the way English conveys gender has been changing. We try not to say men when we mean people. And we are trying to figure out if we like using they to refer to a single person of unspecified gender.

Personally, I’ve avoided these issues by not picking a favorite. I have a lot of experience with the RSV (predecessor of the ESV and descendant of the ASV) and the KJV (the most successful of the Early Modern English translations). For years I carried a side-by-side KJV/NIV. I was reading from the 1977 NASB when the 1995 edition came out. I’ve read through the Christian Standard Bible (CSB), World English Bible (WEB; modernized ASV), NIV (1984), and KJV; some of these more than once. I’m about 30% through the 2020 NASB. I don’t consider any of these to be the Bible; they are all just translations of the Bible into my language. By adopting this position, I completely avoid any emotional response to any new edition of any of the versions of the Bible I read.

I like to think this is an enlightened, mature perspective. Let others get hung up in arguments over which imperfect translation of one of several imperfect collations of imperfect copies of imperfect copies of the original manuscripts is somehow “best”. I choose to focus on the fact that Jesus summed up 3/4 of the Bible (the Old Testament) in two commandments (love God; love others) and his own ministry in one sentence (the Son of Man came to seek and save that which was lost). Paul summed up his ministry (and thus the bulk of the New Testament) in 2 Cor 5:14-21. Those fragments are enough to occupy one’s life; precisely how they are worded doesn’t change their implications or importance. And much of the rest is just exposition.

Photo by Andrik Langfield on Unsplash

PocketBible for Windows Progress Update #3

Today we want to talk about our progress so far on PocketBible for Windows. At this point in the project, it’s difficult to show everything we’ve been working on because a lot of it is “under the hood” or “behind the scenes”. It’s related to how PocketBible accesses its files, or the server, or the database where your user data is stored. These are all hard to demonstrate.

But we’re at the point where there are a few things we can demonstrate, and you can see them in the video above. I’ll also briefly describe them here for those of you who, like me, don’t like to watch videos.

We’re trying to make PocketBible more tablet and touch friendly. We’ve taken ideas from our iOS and Android apps. You’ll notice in PocketBible for Windows that the toolbar buttons are a little bigger than they might be in a typical app. This is to accommodate the touch/tablet environment.

The toolbar at the top of the screen is reconfigurable. You can drag buttons onto and off the toolbar from the Preferences screen.

The toolbar on the left side controls the features of the Study Panel. This is where we display your bookmarks, highlights, notes, search results, etc. In particular today, we demo the note editor. We can style text and paragraphs as you might expect, though your edits are not yet saved to the database. You can edit your notes in a plain-text editor if you’re comfortable working around the HTML tags that control the appearance of your notes.

We have a lot of the features related to display books implemented. There’s no “navigation” features yet, but you can scroll through them and see both text and images.

We’ve been doing a lot of work on the Library functions. This is how you download and open books. You can view a list of books installed on the device or books that you own (your Cloud Library account). You can view the lists in a “gallery” format or in a “list” format.

Clicking on a book in the Cloud Library causes it to be downloaded. Clicking on books in your Device Library opens them. You’ll see a progress indicator as you download books, and you can select multiple books to download them all at the same time.

You can choose to see only Bibles, only dictionaries, only commentaries, etc. You can also search for a book by typing a portion of its name in the search field.

There are a limited number of display format preferences implemented. You can currently choose a font, font size, line spacing, and some other options. You can choose from one of several color schemes, including a “dark mode” scheme, and you can create a custom color scheme by choosing colors for each of a couple dozen different elements of the display.

There’s more going on behind the scenes that are hard to demonstrate, and there a lot of things visible on the screen that are really just placeholders. Anything you see on the screen currently could change at any point before release.

About Our Development Tool Set — Electron

I’ve been talking about our innovative, new development environment since before we started coding on the project. I want to explain that in more detail at this point. If you’re not interested in the technical side of what we do, you can probably just jump to the end at this point. 🙂

We’re using a tool called Electron to develop the Windows version of PocketBible. Electron is a framework for creating native applications using Web technologies like JavaScript, HTML, and CSS. It combines node.js (a JavaScript run-time environment) and the Chromium engine (the guts of the Chrome browser built into the app). This allows us to write our code in JavaScript and create our user interface using HTML and CSS just like we would on a website. It wouldn’t be incorrect to describe this as a website running on an embedded Web server inside a Windows executable.

A lot of programs you are already familiar with are implemented using Electron, like VS Code, Facebook Messenger, WhatsApp, Twitch, and Microsoft Teams. We’re encouraged by the fact that Microsoft seems to be committed to this tool set.

This lets us leverage what we know about website design as we design the user interface and write the app.

We can actually use the Chrome developer tools just like you would in your browser to debug the app. We can explore the user interface, set breakpoints in our code, and examine the values of variables — all using tools we’re familiar with from Web development.

Using Electron allows us to use our Macs for Windows development. The video above was shot on a Mac. That’s why you don’t see a menu bar in the app — on a Mac the menu for the active app is displayed at the top of the screen, not in the app’s window. Being able to run the app on a Mac is a real benefit to us since we’re 100% Mac OS here. We use it for Android, iOS, and Mac development. When necessary, we have Windows running on our Macs under Parallels so that we can use Windows apps. But we try to avoid it as much as we can. 🙂

So that’s where things stand as of early February. You can post questions below or send them to support@laridian.com and they’ll make sure I see them and can respond.


Brief demo of multiple panes. See comments below.

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.

Reading Through the Bible in 2021

Every year, our church encourages members to start a program of Bible reading with the goal of reading the entire Bible by the end of the year. Each month we all exchange emails with progress reports and are encouraged to keep going. Despite the planning, the encouragement, and the reminders, about half of those who start don’t finish.

The NIV Bible contains 753,429 words. Divided into 365 equal readings, that would be 2064 words per day. The average person reads at a rate of 200-300 words per minute. If you’re a college graduate, you probably read around 450 words per minute. So reading through the entire Bible can be easily done by most people in 4-1/2 to 8-1/2 minutes per day. Certainly less than 10 minutes.

So why do so many people fail at keeping this goal? The time itself is not the problem; we all have 5-10 minutes sometime in our day to read the Bible. Here are some suggestions on how to get through the Bible this year.

Make it a part of your morning ritual.

We all have a list of things we do like clockwork every day. Wake up. Shower. Shave. Brush teeth. Get dressed. Have breakfast or at least a cup of coffee. Check email and social media. Go to work. The next day it repeats. Maybe on the weekend it happens later in the morning, but it happens.

Put your Bible reading on that list. In my case, I make a cup of coffee and sit down to make my first pass through email, Facebook, and moderation of my church’s email prayer/announcements list. It was easy to add 5 minutes of Bible reading to that schedule.

For you it might be 5 minutes before you even get out of bed. Or while you eat breakfast. The important thing is to find it a place in your morning ritual so that it becomes habitual.

Use PocketBible on your phone or tablet.

You might think this goes without saying, since it’s coming from Laridian, but it’s a valuable point to make. Laridian offers a number of free and low-cost Bible reading plans and devotionals for PocketBible and makes it easy to access each day’s reading and keep track of your progress. Simply tracking your progress by marking each reading as complete will motivate you to keep going and help you catch up if you get behind.

In addition, for most of us, our phone or tablet is with us all day. This makes it easier to take advantage of break-time, commute-time, standing-in-line-time, and other moments in our day to do our Bible reading. Instead of Candy Crush or Facebook, spend those minutes getting your Bible reading done.

Be realistic.

Figure out how much time you want to devote to the Bible and schedule your reading appropriately. 5-10 minutes will get you through the Bible in a year. 10-15 minutes will get you there in 6 months. Don’t set out to get through the whole thing in a month unless you have an hour each day to set aside for Bible reading.

Try a different translation of the Bible.

Because PocketBible reading plans are not tied to any one translation of the Bible, you’re free to experiment with something different. My previous reads through the Bible have always been in the KJV or NIV. So last year I tried the Christian Standard Bible (CSB). This year I’m using the World English Bible (WEB). (Note that neither the CSB nor WEB are compatible with the Windows versions of PocketBible, but work fine in the Android, iOS and Mac OS versions.)

I think the unfamiliar wording of familiar verses helps me comprehend the passage better. For example, the WEB uses “Yahweh” where the KJV, NASB, and NIV all use LORD. Encountering “Yahweh” in the text seems to make God more personal to me – as if he’s more of a character in the story with his own plans, motivations, and ways of interacting with the people I’m reading about. When I just see LORD in the text, he seems to just blend in and is more of a nameless force or entity in the background. It’s a subtle but important difference in the way I’m perceiving the text.

Last year I ran into the phrase “half the tribe of Mannaseh” (vs. the more familiar – to me – “half-tribe of Mannaseh”). I found this confusing, since I had always assumed the “half tribe” title was because Mannaseh and his brother Ephraim shared the inheritance of their father Joseph (each was half the tribe of Joseph). Running into this wording in verses such as Deuteronomy 3:13 caused me to realize the title is based on the fact Moses gave land on the east side of the Jordan to half the tribe of Manasseh and land on the west side to the other half. The important point here being that running into an unfamiliar phrase caused me to stop, ask the question, and go looking for an answer.

Don’t tell anyone, but it’s OK to skim some passages.

I had a person tell me that they were doing fine reading through the Bible until they got to “the part with all the ‘begots'”. To be honest there aren’t that many of these, but they are mind-numbing. Come back some time and look at the names in those lists and try to learn more about them, but if those lists are what’s keeping you from getting through the rest of the text, just scan ahead to where the story picks up and keep reading from there.

You may run into other places you just can’t get through. I get bogged down in the various sacrifices, dimensions of buildings, descriptions of furniture and draperies, and quantities of items plundered in battles. It’s ok to skip ahead a few verses. None of these are that long. Don’t let a verbal description of an architectural diagram keep you from finishing your reading.

Read it in a different order.

The order in which the books of the Bible appear isn’t ideal for reading through from start to finish. The Old Testament is ordered by genre – first the books of Moses (the Pentateuch), then history, wisdom/poetry, major prophets, and minor prophets. The New Testament follows a similar model, but more by author – first are the gospels; then history; letters from Paul (kind of in order by length, longest to shortest); the letter to the Hebrews (which some argue was written by Paul, but the author is generally considered to be unknown); letters by the apostles James, Peter, John, and Jude; and finally the New Testament’s only book of prophecy.

This year I’m reading through the Bible in chronological order using The Harmony Bible. The author of The Harmony Bible has rearranged the text so that you read about events in the order they occurred, not the somewhat random order that they appear in the Bible. So Job is inserted into the Genesis narrative. David’s psalms are inserted into the stories of his life. The prophets are inserted into the historical narratives, primarily in the books of Kings and Chronicles. In the New Testament, letters to the churches are intermingled in the book of Acts.

Other alternatives include reading a little from the Old and New Testament each day, which is what I did last year.

Some of the devotional books for PocketBible include short commentary or homiletic passages for each day. These can provide context for the passage and help you find application for what you’re reading in your daily life.

Be accountable.

I have really benefited from my email group that is made up of people who are all reading through the Bible at the same time. Find some other people in your church who want to read through the Bible. Meet together or at least exchange emails throughout the year to discuss what you’re reading. Encourage each other to keep reading. Ask your partner what was in those passages you only skimmed. 🙂

Don’t stop.

If you miss a day, keep reading the next day. PocketBible lets you adjust your reading schedule to account for missed days. If it ends up taking you an extra couple of days or weeks to get through the whole thing, that’s fine. Nobody’s keeping score. Don’t let a missed day derail your entire year. Just keep going.

Photo by Rohit Tandon on Unsplash

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.

PocketBible 4.14 for iOS 14

Today Apple approved PocketBible 4.14.1 for distribution through the App Store. This version coincides with the release of iOS 14, and while it doesn’t necessarily take advantage of every new feature of this latest version of iOS, it should work better than the previous version did.

iOS 14 adds a number of new features that may or may not make sense for PocketBible to take advantage of, such as widgets and app clips. Because PocketBible needs to continue to work with older versions of iOS (we go back to iOS 12 with this release), it’s not always practical to implement the very latest new features. And we never know what’s going to survive until iOS 15 and what will be dropped. So don’t expect a PocketBible complication for WatchOS or a PocketBible widget for iPhone.

Here’s what’s new in PocketBible 4.14.1:

FEATURES

Saved/named layouts on iPad. (AFS)

If you subscribe to the Advanced Feature Set, you’ll be able to save the current screen layout, which includes the number and position of open panes/tabs, the list of books open in each pane/tab, the position of each of those books, your navigation (back/forward) history, your recent searches, and your recently visited Bible verses (the latter itself being a new feature; see below).

Keyboard shortcut keys (customizable with AFS)

If you have an iPad Pro with an external keyboard, there are now key combinations that can be used to activate frequently used features like searching and navigating to a Bible verse. A list of these keyboard shortcuts can be viewed by pressing and holding the ⌘ (Command) key (this is true for any iOS app, not just PocketBible).

If you subscribe to the Advanced Feature Set, you can customize these commands. You’ll do that by selecting the function (such as “open a book”) then just press the key combination you want to use for that function.

Trackpad and mouse support in book panes

If you have an iPad Pro with an external mouse or keyboard with trackpad, you’ll find that 2-finger trackpad and scroll-wheel scrolling work better in PocketBible’s book panes than they did before.

New long-press functions of back, forward, search, and go-to toolbar buttons

Pressing and holding on the Back button will display the portion of your navigation history that is “behind” you. You can jump back more than one location by selecting an item from this list. If you have gone back at least one step on this list, a long-press on the Forward button will show you the locations that are “ahead” of you.

You’ve always been able to access a list of recent searches by selecting that option from the Search form. Now you can press and hold on the toolbar Search button to see that list.

A frequently requested feature was a modification of Back that would allow you to see a list of recently visited Bible verses so you could quickly jump back to a passage you had been reading. You can now access this list with a long press on the Go To button while a Bible is active.

Sync to current verse

PocketBible has long had the ability to keep all your Bibles and commentaries sync’ed up to the verse you are viewing in the active pane. That’s not always what you want to do, however. But when that feature is turned off, there wasn’t a way to easily sync your other Bibles and commentaries to the verse you’re reading. Now there are two.

When the automatic sync between Bibles and commentaries is turned off, you can choose Sync All to … from the PocketBible menu to cause all Bibles and commentaries to go to the topmost verse in the active pane (assuming the active pane is displaying a Bible).

You can also select a verse via pressing and holding, and choose the Sync button from the Selection tool bar. In that case, your other Bibles and commentaries will sync to the first selected verse.

ENHANCEMENTS

Customizable sorting of list of open books

When viewing the list of open books in the Library window, you can choose the Edit button to drag the books into the order in which you’d prefer to see them. This is a frequently suggested feature that turned out to be a lot easier to implement than we feared, though it has an important caveat.

That is, the order of the books in each pane is saved as a part of recording your navigation history. So if you change the order of books in a pane, then use Back to go back to a time before you re-ordered the books, the order will revert to its earlier state. Going Forward will restore the new order.

In addition, the order of open books is saved when you save a layout using the new Saved Layouts feature on the iPad. So if you change the order of the books in one layout, it will not affect the order of the books in the same pane in another layout.

And more…

Choosing a range of verses for searching requires fewer button presses. Once you’ve selected a range you’re taken right back to the main Search window.

Autostudy Word and Autostudy Verse will start the study when Enter is pressed in
input field (Advanced Feature Set subscription required for Autostudy).

Long-press link preview now works on the asterisks that mark footnotes in books
and Bibles.

FIXES

The correct background color was not being chosen for certain menus.

After closing the current book using Close this Book on the Library screen, the wrong book was marked as being active.

The program was not checking your AFS subscription expiration date often enough, which kept the subscription active well passed its expiration until you performed a particular action that caused it to be checked. The program now checks the expiration date on launch and at convenient intervals while you’re using the program. There is a grace period to allow you time to renew and activate the renewed subscription.

We Reached Our Goal!

Thanks to the kindness of 492 of our closest friends, we were able to reach our goal of raising $50,000 for the development of an all-new version of PocketBible for Windows! The final total came to exactly $53,000.

If you contributed to the project, you’ll get an email from us letting you know how we’re going to keep you updated on our progress. We’ll publish updates here on the blog. Some will be public like this one; others will be for supporters only.

To get things started, I met yesterday with the outside developer responsible mainly for user experience to bring him up to speed. And since the beginning of the crowd-funding campaign I’ve been working with another in-house developer to bring her up to speed on the development tools and the initial tasks we need to work on.

Even though we already have two different Windows versions of PocketBible, this version is going to be implemented a whole new way (more about that later). So we have to treat it as if we’re doing it for a whole new platform. When we launch into PocketBible for a new platform, I like to tackle the hard things first. That is, I try to identify what is going to be a challenge for us and do some prototyping or proof-of-concept tests to make sure we’re going to be able to solve those problems before they become hinderances to the schedule.

What that means is that we’re going to start kind of in the middle of the project, focusing on the note editor and user data synchronization, because those seem to always present problems on every platform. We’ve already done some experimenting with simply displaying and scrolling through text, as that’s another problem area. We’ve actually written and thrown away a few different attempts at some of those problems already.

This approach creates interesting paradoxes. We’ll be able to sync your notes, highlights, bookmarks, and daily reading progress to and from the server before the program can create or display a note, highlight a verse, or set or go to a bookmark. We’ll be able to scroll through Bible text before we can choose and open a Bible to read. But such is the world of software development, especially with a mature product like PocketBible. Even though the new version of PocketBible for Windows doesn’t exist, PocketBible itself exists both as an abstract concept and in several concrete implementations — not just the existing Android, iOS, and Mac OS apps, but our soon-to-be extinct Windows apps and our already-extinct Windows Mobile Smartphone, Pocket PC, Handheld PC, Palm-size PC, webOS, Blackberry, Palm OS, and browser-based versions. So this new Windows version already exists in our heads. Starting in the middle or at the end or the beginning is all the same to us. 🙂

Photo by Danielle MacInnes on Unsplash