When the Bible Becomes an App

You would think by 2018 we would be well beyond 20th-century thinking about the relative merits of printed vs. digital Bibles. But apparently not. Recently, a PocketBible user sent me this link and suggested I send the author a copy of our PocketBible app.

The author (Trevin Wax, Bible and Reference Publisher at Lifeway Christian Resources) argues that the form in which we experience the Bible (print vs. digital) matters. How the words of Scripture are presented to us says something (or many things) about those words. The question Wax asks is, does a particular format (in this case, print or digital) take away from our experience of reading, comprehending, and internalizing the message of the text?

The conclusion Wax comes to is that one should continue to read and study their printed Bible because what is lost when going from print to screen is simply too great. I want to address those alleged losses from the perspective of one who doesn’t have the author’s vested interest in print publishing and who has been carrying a digital Bible in one form or another for over thirty years and has been exclusively digital for almost as long.


Wax states that a leather-bound Bible with gilded edges and single-column layout “says something about the value” of the words it contains. But remember that the words of the Bible were originally written by hand on common paper or animal skin. The words themselves carried the value, not the medium. It could thus be argued that wrapping the words of Scripture with fancy covers and printing them on expensive paper with handcrafted fonts and gilded edges takes away from the value of the words themselves and places the emphasis on the physical presentation of those words.

The very argument that “presentation matters” makes the case that the form in which the Bible is published adds to the words of Scripture. I’ve long argued that the benefit of an electronic presentation of the Bible is that it removes the text from its fancy wrapper and places it in a position of prominence. A couple years ago I acquired a KJV Bible from about 1908 that was literally falling apart in my hands. There was nothing special about this Bible except that it was the first “red letter” edition of the Bible. After a couple months of sweeping up the crumbs it left behind wherever I placed it, I sent it off to be rebound. I was stunned by the results. Even though I no longer read or study from the KJV as I once did, I wanted to carry this luscious Bible everywhere. I had developed an emotional attachment to the look and feel of this Bible that overwhelmed the fact that the archaic language of the KJV doesn’t speak to me as clearly as some of the newer translations do.

Even binding the books of the Bible together adds meaning and makes implications that some Christians have difficulty overcoming. While I believe the Scriptures were “God-breathed”, it’s a fact that the Bible wasn’t written by one person at one time. It was written by over 40 people over a period of some 4000 years. The copies of those documents that we have were transmitted and copied by hand over centuries. It has only been in very recent history that Christians have had a “Bible” that collects all these works into one convenient binding.

The implications of presenting the sixty-six books of the Bible as one continuous book can include the idea that the worldview, culture, and understanding of God experienced by a person reading an original autograph of the book of Job (considered to be the earliest-written book of the Bible) would be the same as or similar to that of one reading an original account of John’s vision on Patmos as recorded in Revelation (probably the latest-written book of the Bible). We’ve all heard Christians refer to “how they did things in Bible times” – as if the customs of antediluvian nomadic hunter-gatherers were “basically the same” as those of a freed Roman slave living in Corinth when Paul wrote his epistles to the believers in that city. It could be argued that this misunderstanding is exacerbated by our practice of collecting the biblical books of history, law, prophets, poetry, gospels, and epistles all into one book.

But even this “benefit”  that is, that printed Bibles bind the disparate books of the Bible together, presenting a message of unity of message, thought, and ultimate authorship – is not a unique property of printed Bibles. Digital Bibles “bind” the same content together in the same way; they just present it differently.

The author cites research that indicates that screens are best for “surface reading” and that books are best for “deep and meditative reading”. I’ve seen those studies. They conclude that reading comprehension is higher when reading books vs. reading text on a screen. But it isn’t clear whether the medium itself is the cause of this difference. Other studies indicated that reading paginated text results in better comprehension than reading scrolling text. For years, our PocketBible app for iPhone presented the Bible in a paginated format for exactly this reason. While many PocketBible users appreciated this format, most objected to it, as it was so different from their customary experience with interacting with text on their device. We could have continued to ignore their pleas for change – arguing that it is for their own good – but in late 2017 we relented and now present text with both scrolling and paginated interfaces.

The point is that the medium (print vs. digital) may not be the cause of the difference in reading comprehension, but rather the way that text is presented in that medium (paginated vs. scrolling). Interestingly, while it’s difficult to change the way text is presented in a printed book, it’s easy to do it with a digital book. In PocketBible, the user can simply choose to interact differently with the text to regain the benefit of pagination vs. scrolling.

Wax further states that when the Bible is presented digitally, we lose the “geography” of the text – just as we do when using GPS to navigate in an unfamiliar city as compared to using printed maps and our own innate sense of location and direction. Digital Bible readers can simply type “John 3:16” to get to that verse; they don’t have to have a concept of where the Gospel of John lies physically within the text. They may lose the idea that the book of Psalms, which, according to its order, lies right in the middle of the Old Testament, actually lies right in the middle of the entire Bible. They may not realize that the “second half” of the Bible – the New Testament – isn’t “half” the Bible at all — it’s more like one-fourth or even one-fifth of it.

But I would argue that this sense of geography is only “important” because printed Bibles are so difficult to navigate. Small books like Obadiah and Jude are invisible in printed Bibles unless you have a really good idea where to begin looking. But they are just as “big” and “visible” in an electronic Bible as Jonah and Revelation, their larger and more familiar neighbors. In other words, the idea that the geography of the Bible is important is only true if knowledge of that geography is important to accessing the text, which is the important part.

Wax goes on to make a bizarre claim – that we more easily submit to the text when we read it in print than when we read it on the screen, because we have less control over print and are forced to “become more attuned to the complexities of family life, the vicissitudes of social institutions, and the lasting truths of human nature” when reading words on a printed page. This claim is questionable if not outright false just on its face. But if “complexities, vicissitudes, and truths” are what is important, it can be argued that an electronic Bible is better able to convey them because of the depth of resources it places at one’s fingertips.

On a recent Sunday, I was listening to a sermon on 1 Peter 2:1-3. Verse 1 tells us to “put aside all slander” (NASB). Having myself been falsely accused of slander (by a sociopath as part of her request for a restraining order against me – but that’s another story), I’m very familiar with the nuances of the term. I was intrigued by the fact that other translations of the same verse used “evil speaking” instead of the very specific term “slander”. I noticed this because my digital Bible, unlike my printed Bible, allows me to simultaneously view multiple English translations, multiple Greek New Testaments, and multiple Greek dictionaries.

The word used in 1 Peter 2:1 is καταλαλιας, which literally means “to speak against”. This includes more types of speech than simply slander (making statements about a person that are provably false), including gossip (which is often true statements being told out of context). The proscription of καταλαλιας includes more than slander, a fact I may not have realized if I did not have access to Bibles other than the one most people in my church carry on Sunday.

Wax concludes with an admonition against relying solely on digital Bibles and an encouragement to depend primarily on a printed Bible so as not to lose the benefits of reading the Bible the way God intended it. I believe I’ve shown that the perceived detriments of reading a digital Bible are not negatives as much as they are simply differences between reading words from a screen vs. reading words from a page, and that in some cases, the same positive (or negative) characteristics apply to both screens and pages.


Since we’re making arguable arguments, I’ll make this one. Do a study sometime on occurrences of the phrase “the word of God” or “the word of the Lord” and similar phrases throughout the Bible. (Needless to say, this is easier with a digital Bible.) You will find that the word of God is “received”, “heard”, “given”, and “spoken” but not “written” or “read”. This is not to say that written words are not the Word of God, but rather than there is more to the “word” than its form on a page. The Word of God is the message itself, as communicated to humans by God. It is not constrained to shapes made with ink on pages made of dead trees. It is God’s Word that is “sharper than any two-edged sword”, not your leather-bound Christian Standard Bible. The pages of your printed Bible do not convict of sin or judge the thoughts or intents of your heart, but the Word of God does.

The point is that God’s Word transcends medium, language, and typographical style. The Law was no less authoritative because it was printed on stone instead of paper. Paul’s letters convict believers of sin whether they were the original autographs written on papyrus or parchment, or a modern translation printed on paper or illuminated on a screen. The Spirit of God conveys the Word of God to people through their hearts and minds. Always has. Always will.

Photo byAaron Burden

Does It Matter Where Your Bible App Comes From?

DumpsterTrevor McKendrick is an atheist who wrote one of the top-selling Bible apps for iOS. A former Mormon, McKendrick saw an unserved niche market on the App Store and created a Spanish audio Bible to fill it. Now he’s banking over $100,000 per year selling the app. He compares the Bible to Harry Potter and describes Christians as people who learn the spells in the book and try to use them to heal their children. He compares them to people who teach The Lord of the Rings as real history.

Does it make any difference whether or not the people who create the products you use for Bible study agree with the materials they publish?

When I started writing Bible software in 1988 there were very few other products on the market. I purchased the King James Bible from Public Brand Software, a distributor of freeware and shareware programs for MS-DOS. While browsing their catalog (paper catalog — this was before the Web) I saw a Bible program called WordWorker and picked up a copy of that, too.

WordWorker was pretty impressive compared to other programs available at the time. My problem with it was that the programmer who wrote it was associated with The Way International, which denies key teachings of historic Christianity and adds a few of their own. They encourage severing ties with family and friends and living with other “believers” instead, which many argue qualifies them as a “cult”.

Coincidentally I had been unsuccessfully recruited by a member of The Way while in college. Noticing a strange-looking guy observing me playing pinball at the student union, I struck up a conversation and bought him a couple games (he had never played pinball). He invited me to join his “twig fellowship”. As a brand new Christian with very little foundation in the Bible, I struggled with figuring out if this was God’s direction or not. Fortunately I dodged that bullet, and got involved with a local church that had a strong emphasis on the Bible and Bible study, which is what eventually led me into developing Bible software.

It was difficult to get excited about using WordWorker because I felt like I was supporting a cult. Even if it coincidentally met my needs, it was hard to recommend to others or even use enthusiastically because I knew where it came from. One benefit of using Bible software that comes from a person with whom you share a common faith is that you don’t have to feel guilty about supporting something with which you disagree. You and I may not agree on every fine point of doctrine, and we may not share a common worship style preference, but I bet we’re closer to agreeing with each other on the fundamentals of the faith than you would be with an atheist.

I originally wrote my Bible study software as a tool for myself to use. Its features were designed to meet my needs, which I obviously knew well. I didn’t have to do any research to figure out what people who read the Bible wanted; I wrote what I wanted.

I took my Bible program (QuickVerse) to Parsons Technology in 1988, where, over the next ten years, I employed a couple dozen different programmers. Not all of them were practicing Christians, but they were good programmers. Jeff Wheeler (who would later leave Parsons with me to start Laridian) and I led the development of the program. Both of us were Bible-believing Christians who were not just developers, but users of the program.

Having real Christians write your Bible study app guarantees that it is designed to meet the needs of someone who really studies the Bible.

Parsons Technology was not a “Christian company”. It was a plain-old software company that happened to have a Church Software Division that published church management and Bible study software. Parsons was eventually purchased by Intuit (1994), which sold us to Broderbund (1997), which was purchased by The Learning Company (1998), which was purchased by Mattel (1999), which sold the Church Software Division to a dormant company that was rumored to have previously been a booking agency for Las Vegas acts (2000). During those years we were faced with a number of demands from our pagan overlords that compromised the quality of QuickVerse. They saw “unserved niches” on store shelves and wanted us to create products that were just old versions of QuickVerse with a new cover. They weren’t interested in meeting needs, but in making money.

This was the final straw for me. When it got to where creating Bible software was about duping people into buying old versions of our program at a cheap price because BestBuy or Costco was looking for 25-cent CD-ROMs to fill an end-cap, I bailed out and started Laridian in 1998.

Our goal has always been to focus on our customers and our product, not on creating a company to sell to the highest bidder. The features and reference materials you see in PocketBible come from customer feedback (and from our own needs as our product’s first customers). We bristle at doing things like renaming our product “@Bible” so that it pops up first in alphabetic search results on the App Store, or calling our program “Bible App” to cause it to come up first when you do a generic search for a Bible app, or seeding the store with identical products, all with different names, so it appears more often in your search results. This is what marketeers do to trick people into buying shoddy products. We aim for letting the quality and usability of our apps speak for themselves.

So another benefit of having real Christians write your Bible study app is that they’re not just seeing you as a rube who will spend their hard-earned money on a quickly thrown-together, shallow product, but rather they are committed to creating not just one download but an ecosystem of products that will meet your Bible study needs not only today, but for years to come.

I don’t have a doctrinal test for people with whom I do business, but I expect my Bible study materials to come from people who are as firmly committed to the Bible as I am. It’s not that they’re the only ones who I can trust to create useful products, but it is at least more likely that they’re doing a better job.

Is Your Bible “Missing” Verses?

We occasionally receive reports from PocketBible users that a PocketBible Bible is missing a verse (or verses). These “errors” are usually discovered in a group Bible study situation. Following along as someone else reads, you realize that a verse appears to be missing in your Bible. But in this case, there is more to this than meets the eye.

What are these “missing” verses and why are they missing?

The numbering scheme for verses in the English Bible was first used in the Geneva Bible in the year 1560. This pattern was followed in subsequent English translations including the King James Version, published first in 1611. In the years since these Bibles were translated, many additional manuscripts have been found which predate those used by the translators of the Geneva and King James Bibles. Because of their age, these older manuscripts are believed by many scholars to more accurately represent the original documents. In many cases, however, they do not include all the verses that are in the more recent manuscripts.

Translations such as the New International Version, Revised Standard Version, and other newer translations take advantage of these more recently discovered manuscripts and therefore do not include all of the verses found in the older translations. Rather than reinventing a numbering scheme for the whole Bible, the translators decided to use the same verse numbers as the older Bibles but leave the missing verses blank (or move them into footnotes). The result of this is that several verses in these newer translations appear to be “missing”.

The affected verses are:

  • Matthew 17:21; 18:11; 23:14
  • Mark 7:16; 9:44,46; 11:26; 15:28
  • Luke 17:36; 23:17
  • John 5:4
  • Acts 8:37; 15:34; 24:7; 28:29
  • Romans 16:24

For the Revised Standard Version, in addition to the above list, there are other verses and points of interest:

  • Matthew 12:47; 21:44
  • Luke 22:43,44
  • The order of Exodus 22 in printed form is 1, 4, 2, 3, 5. PocketBible displays these verses in numeric order: 1, 2, 3, 4, 5.
  • James 1:7,8 was combined in verse 7 leaving 8 blank. 3 John 14 was split into 14 and 15.

Another point of view

Some are quick to jump on the idea that the newer translations are removing text from God’s Word and therefore are not to be trusted. It is important to note that it could just as correctly be argued that the older translations added text to God’s Word. Where one comes down on this argument depends on the nature of one’s own research, or on which scholars one decides to trust. We’ve determined it’s best to present a variety of options to you so that you can come to your own conclusions when choosing the Bible (or Bibles) that you find to be the most beneficial to your own spiritual growth.

If you enjoy learning about the history of the Bible, consider the PocketBible book: The Origin of the Bible by Philip Comfort.

Serendipitous Programming

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PocketBible for Mac OS: Design Principles

PocketBible for Mac OSWhile it may not be evident from the outside, there are certain philosophies, both of Bible study and software design, that strongly influence each of our Bible study apps regardless of platform. While we’re not at a point where we can give a concrete demonstration of PocketBible for Mac OS, we can talk about how those philosophies will influence our work.

In no particular order:

You should spend most of your time in PocketBible wrestling with the Bible text, not with your Bible software. This means that frequently accessed functionality should be immediately available, and that you shouldn’t have to deal with overlapping windows that obscure the text you’re trying to read. You shouldn’t be thinking about how to arrange things on the screen or how to access basic functions like navigating to a verse or creating a note, but instead be thinking about what you’re reading and how it applies to your life.

While we should consider specific use cases and how they are served by our design, we shouldn’t design around the use cases. We think a lot about all the things you might want to do with your Bible software, like search for a word, compare Bible translations, and view a commentary on a passage. This list of ways that you use our software defines a set of “use cases” (or “user stories”).

Informally, a “use case” or “user story” is a combination of a specific goal (“User must be able to search the text for a given word or phrase”) and a description of the steps or interactions with the program necessary to meet that goal. Programmers use these use cases as part of validating that their solution meets the user’s requirements.

Some Bible software companies make the mistake of creating new user interface elements for every use case. In these programs, when you’re in “search mode” the program looks and behaves differently than it does while just browsing through the text. When you want to compare two translations of the Bible, the second one pops up in a window that may obscure a portion of what you’re reading, and which doesn’t have all the functionality you have in your “main” Bible. And the only way to view a commentary might be to split your Bible window to show a commentary beneath it, with no consideration given to how you might open a second commentary or that you might not want to lose space for Bible text when viewing a commentary. And while you might consider “commentaries” and “dictionaries” to be just “reference books” and expect them to work similarly, the program might display dictionaries in the form of pop-up windows when activated for a particular word, covering other text and behaving differently than commentaries, devotionals and other reference books.

We will try to create a flexible user interface where, for example, search results, bookmark lists, lists of notes, and other “lists of verses” share a common user interface component or pattern, and where opening a Bible to compare to the current one is no different than opening a dictionary, commentary, devotional, or any other book. There’s less to learn and there are fewer surprises.

PocketBible for Mac OS should not necessarily look like PocketBible for Windows, PocketBible for Android, or even PocketBible for iOS. While it should share a lot of design, algorithms, and even code with those platforms, it should look and feel like a Mac app, not a Windows app ported to the Mac or even an iOS app ported to the Mac. We like to take the best features of all our previous apps and combine them with fixes to the mistakes we made in previous apps and wrap them in a user interface that is consistent with the other apps on the target platform.

Mac users should not feel like they are being accommodated, but rather that Laridian considers Mac to be a primary platform for its products, and PocketBible for Mac a flagship product. We confess that we treat certain platforms as second-class citizens. For example, both our BlackBerry and webOS apps were “Bible only” apps, and neither shared the LBK file format used by our other apps. BlackBerry was primarily an enterprise (business) platform, and the future of webOS was always doubtful. This made it difficult to commit the time and money to those platforms that would’ve been necessary to really do them right. Mac OS is different. It is our intention to make it difficult to tell if we’re “Mac people” or “Windows people” because of our level of commitment to both platforms.

PocketBible for Mac OS will focus on the needs of the 99% of Christians who are neither “clergy” nor “Bible scholars”. Most of our customers occupy the pews on Sunday morning and work in secular jobs during the week. While many are Sunday School teachers or Bible study leaders and a few are pastors, most are simply everyday Christians with a love of the Bible. Some have some experience with Greek or Hebrew, but most don’t do their daily devotional reading from the Greek New Testament. PocketBible for Mac OS may include resources like the Greek New Testament and meaty, scholarly commentaries, but its focus will be on concise, accessible works that help the average Christian understand and apply the teachings of the Bible in their daily walk. It’s not that we have a disdain for the original languages, but rather that, as Bible software users and everyday Christians ourselves, we understand there are people out there who understand those languages significantly better than we do, and it’s better, faster, and easier for us to read what they’ve written in English about the Bible than to depend on our own spotty and questionable original language knowledge.

Of course, the 1% of you who dream in Greek will want a different Bible study app. PocketBible may not be for you. We understand that; you’re not our target user.

Given a choice, we will take functionality over complexity; usability over displays of our technical prowess, and simplicity over beauty. We’re not trying to solve every problem in the field of computerized Bible study, but instead we’re trying to provide a tool that can help you solve the most common problems you encounter in your everyday study of the BIble. We’re not trying to flex our programming muscles to win your admiration, but instead give you something you can be expected to use and understand with minimal learning time. We feel that beauty is often only skin-deep; that simplicity and elegance are beautiful in their own way. You may find another girl who looks prettier, but PocketBible is the girl you want to take home to meet your parents and be with forever.

We hope this helps you understand more about how we think about Bible software, how we try to focus on the way you study the Bible, and that you can see how that is implemented in PocketBible for Mac OS X.

“Side-loading” or “Manual Install” Instructions for Android

This is an old article but the general idea still works not just for Kindle, but for installing PocketBible for Android onto any Android device from our website instead of from Google Play.

If you have the option of using Google Play on your device – even if it didn’t come with it already installed – that is the easiest way to install PocketBible. But if you must do a manual installation of PocketBible, this is how you do it.


You need to make sure you’ve enabled “third party apps” on your Kindle. Go to Settings and look for “Device” (it may be in the “More…” menu). Look for “Allow Installation of Applications” and turn it on. On the HDX, this option is under Applications in Settings. You’ll get a warning message but that’s OK – they’re just trying to scare you into only buying software from Amazon. 🙂

For newer Kindle devices, swipe down from the top and select Settings. Under Personal select the option for Security. Under Advanced select the option to enable Apps from Unknown Sources and accept the security warning.

Once you’ve done that, just go to the Web browser on the Kindle and type in this:

https://LPB.cc/pbsideload

PocketBible should automatically download. On some devices, you’ll be prompted to install the app but on the Kindle devices, you’ll have a few more steps

Original Kindle Fire and HD: You may have to tap the notification number next to your name in the upper left corner of the screen. You will then see a list of notifications. One of them should say something like com.laridian.pocketbible or pocketbible.apk and “download complete”. Select that one. You’ll be asked if you want to install PocketBible and it will ask if you want to allow PocketBible to use network communications and some other things. Choose the “install” button and when it’s done choose “open”.

Kindle Fire HDX: After you download from the Silk Browser, tap on the menu icon in the top left corner. Choose the Downloads option and you should see PocketBible.apk listed there. Tap on it and choose the install option to finish the process. If you prefer, you can watch of video of this.

On newer Kindle devices we have found that you may not be able to just tap on the downloaded file after it is downloaded, but rather you need to go to the File Explorer (or Kindle equivalent thereof), locate your Downloads folder, then locate the downloaded apk file for PocketBible and select it there to run it.

Once PocketBible is installed you can choose it from the carousel like any other program. The PocketBible icon may look “blurry” but that’s OK — Amazon uses low-resolution icons for third-party apps because they’re upset that you didn’t give them any money to run the software on their device, so they want to make you think there’s something less than professional about our app.  🙂

Once again, if you have the option to install Google Play on your Kindle or other Android device, that is the easiest way to install PocketBible. We can’t help you do this because of the large variety of Android devices out there, but if you google it you should find instructions for installing Google Play on your particular device.