The Road Ahead – Q2/Q3 2026

With Q1 behind us and its quarterly report now published, it’s time to look forward. Back in January, I shared my AI plans for AndBible — this post is a broader roadmap update covering not just the AI features but everything on the horizon. Going forward, I intend to publish these roadmap updates at the start of each quarter, giving the community visibility into what’s coming next.

Looking Back: Q1 in Brief

Q1 2026 was a busy quarter. The headline achievement was completing the entire AI integration feature set — a multi-provider LLM agent system with Bible-aware tools, an AI document system, a prompt editor, and deep integration points throughout the app. In total, the AI project consumed over 100 hours of development time across Q4 2025 and Q1 2026.

Alongside the AI work, I built a comprehensive reading and memorization progress tracking system with automatic reading detection, calendar heatmaps, multiple memorization modes (word scramble, word order, word blur, and typing), and reading cycle support. I also made significant improvements to Strong’s dictionary display, added multi-translation search, overhauled the text display settings with a new three-level inheritance model (global, workspace, window), and fixed dozens of bugs — including several long-standing ones.

The full feature list is available in the Q1 2026 changelog, and the financial details are in the quarterly report. Now, let’s talk about what’s ahead.

Q2 Priorities: Two Major Releases

The two most important goals for Q2 are shipping production releases on both platforms: AndBible 5.1 and AndBible for iOS 0.1.

AndBible 5.1 — AI Features and Reading Tracker Go to Production

The AI integration and reading/memorization tracking system are essentially feature-complete, but taking a feature set of this magnitude to production successfully requires thorough real-world testing. My testing process started when I installed the new version on my own devices and published the first test-* build on GitHub. Several people have been testing it since then.

The next step is the Google Play beta channel. I plan to push the new version to beta within the next one to two weeks. This will make it available to roughly 1,000 beta testers. During the beta phase, I’ll be collecting bug reports, fixing issues, and refining the experience based on real user feedback.

Documentation also needs to be updated for the new features. Thanks to AI-assisted writing, I can produce decent documentation with significantly less manual effort than before — and I plan to add direct links from the UI to relevant documentation pages, making help easily accessible to users.

The beta-to-production transition will happen once there are no major outstanding issues and the documentation is in good shape. At that point, the version number will bump to 5.1, signaling the significance of the new features.

AI-powered translations. One significant workflow improvement I’ve built this quarter is using Claude to update UI translations. I’ve created a dedicated Claude Code “skill” that handles the translation process and produces at least adequate translations across a large number of languages — I’ve been able to verify the Finnish output personally and found it more than satisfactory. These AI translations will be pushed to Transifex, where volunteer translators can review and improve them manually. This means translations no longer block the release process — I can get reasonable translations for the most important languages quickly and affordably, and the community can refine them at their own pace.

iOS 0.1 — AndBible Comes to Apple Devices

This is a development that has been years in the making — and it came as a wonderful surprise even to me. Primetheus has been quietly developing an iOS port of AndBible for a few years, and brought it to our attention in February. The work is remarkably far along, including many of AndBible’s most beloved features, although it is not yet feature-complete.

Primetheus and I agree that the project is now at a stage — accelerated by AI-assisted development — where we’re ready to publish a first version on the Apple App Store. This will be version 0.1, reflecting its MVP status and maturity level.

This work comes under the AndBible Open Source Project umbrella, with Primetheus as the primary maintainer of the iOS codebase at this stage. My role will be to conduct some code review, test the iOS version, provide feedback, and handle the App Store publication.

This is a huge milestone for the AndBible project. Users have been requesting an iOS version for years. I’ve always assessed — quite reasonably — that the effort required was prohibitive given the available resources. And yet, God’s ways are not our ways. He has called brother Primetheus into this project and demonstrated that yes, an iOS version is in His plans and it is happening — even though I myself am not the one primarily building it, at least not at this stage.

Long-term shared codebase vision. Looking further ahead, the plan is for the Android and iOS versions to share as much code as possible. We’re tentatively looking at Kotlin Multiplatform as the foundation for this. The code that could be shared falls into two categories: non-UI “backend” logic (Bible data handling, bookmarks, database, sync), and the Vue.js-based BibleView frontend, which already runs in a WebView and works on iOS with minimal changes (the iOS port already uses it, albeit an older version).

Building a fully shared codebase is a substantial project. My view is that it’s achievable with reasonable effort as AI tooling continues to mature, but I see it as wiser to target 2027 for this work rather than rushing it. We’re in active discussion with Primetheus about the next steps.

Beyond Q2: Bible Knowledge Graph & Taxonomy

One of the most exciting ideas on the longer-term horizon is building a Bible Knowledge Graph and Taxonomy for AndBible. The idea originally came up in a conversation with a sponsor, and I’ve been increasingly enthusiastic about it — I believe it could be the next truly impactful project for AndBible users. The concept is to use AI to extract structured data — people, places, events, themes, and their relationships — from public domain Strong’s-encoded Bible texts, creating an interconnected knowledge base that transforms how users explore Scripture.

The Vision

Imagine tapping a name in the Bible text — say, “David” — and instantly seeing a rich information page: his biography, family tree, key events, all verse mentions, and connected theological themes. Or pressing an “Explore” button on any verse to see all the people, places, themes, and cross-references connected to it. Or browsing a theme like “Grace” and seeing key passages, the original Hebrew and Greek words, and related themes.

This goes far beyond traditional cross-references or dictionary lookups. It creates a web of knowledge where every name, place, and concept is interconnected and explorable — turning Bible study into something more like browsing an encyclopedia, where each link leads to deeper understanding.

How It Works

The key ingredient is a Strong’s-encoded Bible — a text where every word is tagged with its original Hebrew or Greek root number. Two such Bibles are freely available in the public domain: the KJV and the World English Bible. Strong’s numbers solve one of the hardest problems: disambiguating identical names (e.g., John the Baptist vs. John the Apostle have different Strong’s numbers).

Modern AI can systematically process every chapter of the Bible and extract structured information: named entities, events, relationships, and theological themes. This data is then validated against existing scholarly datasets — STEPBible TIPNR for people and genealogies, OpenBible.info for place geocoding, the Treasury of Scripture Knowledge for cross-references — with the AI filling the gaps, especially the thematic taxonomy that no existing dataset covers comprehensively.

The resulting dataset would be packaged as a downloadable database and integrated into AndBible’s existing architecture, building on the same patterns already used for dictionary entries and cross-references.

Why It Matters

Several high-quality open datasets already exist (TIPNR, Theographic, OpenBible.info), but none provides a unified, comprehensive graph covering people, places, events, and theological themes together. The AI-generated knowledge graph would combine and extend all of these, and — critically — the dataset would be published under an open source license that keeps it freely available to the open source Bible software ecosystem and its users, while preventing commercial exploitation. The exact license is still being determined, but the intent is clear: this data should serve the community, not be locked behind paywalls.

This project is targeted for Q2–Q3 2026, after the production releases are shipped.

Strong’s Annotation for Non-English Bibles

A related project that I’ve already begun is building an AI-assisted Strong’s number annotation pipeline for Bible translations that don’t have Strong’s numbers. Using the Strong’s-tagged KJV as a reference, the pipeline processes a target translation chapter by chapter, mapping each word to its corresponding Strong’s number.

The primary goal is to develop and publish this pipeline as open source tooling that can be applied to any Bible translation. The goal for the annotated output is high coverage with uncertainties and conflicts visible to the reader (annotated as footnotes). Accuracy will be measured through sampling with the help of experts in the original languages and theology. I’m using one or two Finnish Bible translations as the initial proof of concept.

An important design decision is that the annotations can be published as add-on modules that attach to existing Bible translations. Rather than redistributing the full Bible text with Strong’s numbers embedded (which would raise licensing issues), the add-on contains only a number list for each verse that maps to the word order of the original translation. This means Strong’s annotations can be added to any published translation without requiring redistribution rights — AndBible applies the mapping at display time.

This project will directly enable the Bible Knowledge Graph features described above for languages that don’t currently have Strong’s-annotated translations. Processing does consume significant AI resources, so I won’t be mass-processing translations across many languages myself. However, the tooling will be open source — anyone can run it and publish the results. I also plan to offer sponsored processing at some point, where users can request annotation of a specific translation for a fee that covers the AI processing costs.

What’s Next

To summarize the priorities going forward:

Q2 2026 (immediate)

• Ship AndBible 5.1 to production (AI features + reading tracker)
• Ship iOS 0.1 MVP to the App Store
• Update documentation for new features
• Catch up on user support and issue triage

Q2–Q3 2026 (medium-term)

• Bible Knowledge Graph: data generation pipeline and initial integration
• Strong’s annotation: develop and publish the pipeline, with Finnish translations as an initial proof of concept

2027 (longer-term)

• Kotlin Multiplatform shared codebase for Android and iOS
• Bible Knowledge Graph Phase 2: maps, timelines, visual exploration

Sponsorship and Sustainability

I’m deeply grateful to the faithful sponsors who make this work possible. Thanks to your support, AndBible development is moving forward at a pace that would have been hard to imagine a year ago. These goals are achievable — and they are being achieved.

That said, AndBible development is a side project alongside my near-full-time employment. The target I’m working toward is having one full day per week fully dedicated to AndBible — roughly 90 hours per quarter. Reaching that level of sustained, predictable funding would allow the current momentum to continue: regular releases, responsive support, and steady progress on the roadmap items above.

If you’d like to help make that happen, you can support AndBible through the webshop — whether through general development sponsorship or by commissioning specific features. Recurring sponsorships via bank transfer are also available; reach out for details.

I intend to publish an updated roadmap at the start of each quarter. If you have thoughts or feedback, I’d love to hear from you.