AndBible – News & Blog

AndBible 6.0 public beta: one app for Android, iPhone, iPad, Mac, Windows and Linux

Sat, 07 Nov 2026 00:00:00 GMT

Today I am opening the public beta of AndBible 6.0. It is the biggest change in AndBible's history: one shared app for Android, iPhone, iPad, Mac, Windows and Linux. The Android, Windows and Linux betas are available now; the iPhone and iPad beta (which also runs on Apple Silicon Macs) follows in a few days.

Faster than planned

This is not what I expected to be writing this autumn. In July the separate iOS app opened its public beta as an early MVP, and in September it reached the App Store. A month ago, in the roadmap for Q4 2026 and Q1 2027, the plan was:

Q4 2026: release the Compose version to Android users only, first as a beta, with no new features.
Q1–Q2 2027: bring the shared codebase to iOS in a unified release, "when it is ready, not by the calendar".
WebDAV sync: to be built after the Compose release.

What is here now, in November:

The 6.0 beta is the multiplatform version, not an Android-only one. The same code runs on Android and on iPhone and iPad, and the iOS beta of it opens in a few days.
Windows and Linux are new platforms that were not in any roadmap.
WebDAV sync is already in, next to Nextcloud on every platform, iCloud Drive on Apple devices and Google Drive on Android.

One big factor in this pace is JailBee, my own side project, which I develop partly at my workplace, Gisgro Oy. It runs each piece of development work in its own isolated container and lets me coordinate many of them at once, so large efforts like this port move more smoothly than before. Like AndBible, JailBee is open source under the GPL-3.0 licence.

The whole interface, gone through screen by screen

The largest part of this release is one you could not see until now. Since early summer, when the UI modernisation work started, I have gone through AndBible's whole interface view by view. In July every screen was rebuilt in Compose and checked against the classic one. August went into round after round of comparing old and new screens side by side on a real device. In September the structure underneath changed: one navigation graph instead of separate Android activities, a restructured reading view and a new dialog system. Since then every section has been verified, and every defect found has been fixed.

Along the way a large part of the interface was redesigned, not just copied: Material 3 throughout, clearer menus and dialogs, and many small usability improvements in places that had aged. It has been long and largely invisible work. With this beta it finally reaches you, and the same interface is now shared by every platform, so your Bibles, bookmarks, notes and StudyPads work the same way wherever you open them.

What is new

Every platform. AndBible now runs on iPhone, iPad, Mac, Windows and Linux as well as on Android. On a Mac it is the iPad app, on any Mac with Apple Silicon.
A new interface, rebuilt with Compose Multiplatform and shared between the platforms.
Sync between platforms. Nextcloud and WebDAV sync work everywhere. iCloud Drive is available on iPhone, iPad and Mac, Google Drive on Android (not in the F-Droid build).
Background activity: syncing, downloads, search indexing and AI agent runs show in an activity list, and finished or failed work is reported with a notification.
Reading plans are now included in synchronization.
Search: Find all occurrences no longer opens a separate full-screen results page.

There are many more fixes and improvements. The full list is on the Release 6.0 page.

How to join the beta

Android. Join the beta programme on Google Play with the Google account of your phone or tablet. Google Play then updates AndBible to the beta. You can leave the programme on the same page at any time and go back to the stable version at its next update. If you do not use Google Play, download the andbible-<tag>.apk file (not calculator-…) from the newest Beta release on our GitHub releases page.

Windows and Linux. AndBible for the desktop is new in 6.0. Download the Windows installer (.msi) or the Linux .deb package or AppImage from the newest Beta release on the GitHub releases page. Both are for 64-bit computers. The Getting started guide walks you through the installation, and AndBible on Windows and Linux has the details.

iPhone, iPad and Mac. The 6.0 beta for Apple devices is coming in a few days through Apple's TestFlight, as soon as I have finished testing it on real devices. This post and Getting started will have the link when it is open. Until then the App Store has the current AndBible for iOS.

As always, AndBible is free and open source, with no ads and no tracking, on every platform.

Things work a little differently on each platform

Most of AndBible is the same everywhere, but not everything: for example which sync services you can use, how files are shared and how updates arrive. The Platform differences page lists them.

Please tell us what you find

A beta is a version for everyday use, but it will have rough edges, and that is exactly why we need you. When something does not work:

In the app, open the menu, then Feedback / bug report. The report includes the details we need to find the problem. The same menu item is there on every platform.
Or open an issue on GitHub.

Please tell us your device and operating system, and what you were doing when the problem happened. More about reporting is on the Support page.

Thank you for testing, and for helping AndBible reach every device.

God bless,
Tuomas Airaksinen
Lead developer, AndBible Open Source Project

The Road Ahead - Q4 2026 / Q1 2027

Fri, 09 Oct 2026 12:00:00 GMT

Alongside the financial report for Q3/2026, here is the roadmap update for the next two quarters. It is shorter than usual, because the plan is simple: release the Compose version of AndBible to Android users, while already laying the groundwork for bringing the same shared codebase to iOS. That is plenty of work for these two quarters.

Looking back: Q3 in brief

The previous roadmap moved the shared Android/iOS codebase to the front of the queue, and that is where most of Q3 went.

The Compose port. In July I laid the multiplatform foundations (a shared Kotlin Multiplatform module, a multiplatform event bus and a Material 3 theme) and ported the screens to Compose, one at a time and checked against the classic screens. August went into many rounds of comparing old and new screens side by side on a real device and refining the interface. In September the work turned to architecture: a single navigation graph replacing separate Android activities, a restructured reading view and an app-wide Compose dialog system. The quarter ended with systematic, section-by-section verification on the emulator. The Compose version is now functional and nearly finished.
AndBible for iOS on the App Store. At the end of September the native iOS app left beta and is now available on the App Store. It is the work of Jared Murrell (Primetheus), and I am very grateful for it.
Support. Timmy Braun (timbze) has been helping with user support, which has been a real relief at a time when nearly all of my AndBible hours go into the port.

The plan

Q4 2026: Compose to Android users

Finish the remaining verification and fixes.
Release the Compose version with its refreshed Material 3 interface: first as a beta, then to production. This adds no new features, but many existing ones get UI/UX improvements along the way. A change of this scale deserves a round number, so it will most likely be AndBible 6.0.
In parallel, continue the groundwork for "one codebase, two platforms". I have already started the preparations and some of the actual implementation, and it proceeds on its own branch alongside the work of polishing the Compose release for Android users. Compose to Android users stays the top priority and the goal of Q4; the iOS work does not delay it.

Q1–Q2 2027: one codebase, two platforms

Building on the groundwork begun in Q4, finish bringing the shared codebase to iOS and publish a unified release, so that Android and iOS run the same app at full feature parity. It will replace the current native iOS app.
The release is done when it is ready, not by the calendar: the Q1–Q2 2027 timing is indicative, not a promise. The existing iOS app stays in maintenance mode (bug fixes only) until then, and existing iOS users' data will migrate automatically on first launch of the new app.

Technical choices for the shared codebase

The design work for the iOS side has settled several questions that were open in the previous roadmap:

Bible engine: a Kotlin Multiplatform port of JSword ("KSword"), not libsword. The same engine will run on Android and iOS. The deciding factor is that verse numbering, passage parsing, book names and the text pipeline must behave exactly as in the Android app, or bookmarks and synced data would point to the wrong verses. libsword covers only the module-storage layer. The port is checked against the current JSword running side by side as a reference. The conversion foundations are already in place.
Database: Room multiplatform with a bundled SQLite on both platforms. The Android side of this is already done (Room 3 with the bundled SQLite driver); moving the databases into shared code follows once the engine's reference and book model are shared.
Search: Lucene is replaced by SQLite FTS5. The search modes stay the same, but each Android user's search index will be rebuilt once, automatically, after the update.
Interface: Material 3 plus essential iOS conventions (edge-swipe back, safe areas, native share sheet and file picker), not a separate iOS-styled UI.
Bible view: one shared bibleview-js for both platforms.
Sync on iOS: Nextcloud and iCloud Drive in the first release. Google Drive on iOS may come later.

Later: the Knowledge Graph

The Bible Knowledge Graph & Taxonomy and the Strong's annotation pipeline described in the Q2/Q3 roadmap remain very much on my list. They will likely be taken up around Q2 2027, or whenever the unified iOS release is done. Building them on top of the shared codebase means their interfaces only need to be built once.

Contributions

What I wrote last time still holds: until the Compose version has been merged and released, larger pull requests are not something I can realistically take in, because the code underneath every screen is changing. Small, well-scoped fixes remain welcome. Once the Compose work is merged, I intend to return to feature development and to taking in pull requests again. The iOS groundwork will keep changing some things underneath, so for anything larger, please open an issue first so we can agree on the approach and the timing. Ideas and feature requests are as welcome as ever.

Sponsorship

Thank you to every sponsor who keeps this work going. As the Q3 financial report shows, the port has no budget of its own and has been funded mainly from the general development pool, as intended. That pool now ends the quarter empty, so there is no buffer going into Q4. My goal remains one full day per week for AndBible, roughly 90 hours a quarter. You can help through the webshop, by recurring sponsorship by bank transfer (get in touch for details), or with a donation via GitHub Sponsors.

God bless,
Tuomas Airaksinen
Lead developer, AndBible Open Source Project

Financial report for Q3/2026

Fri, 09 Oct 2026 10:00:00 GMT

Background

Sykerö Software (Tuomas Airaksinen Software Oy), company of the lead developer, provides a way to sponsor AndBible development. You can support the ongoing development of AndBible financially via the webshop. Recurring sponsorships via bank transfer (EUR, USD, GBP) are also available — reach out for details. You can also make a recurring donation through GitHub Sponsors. The previous quarter's report is available on the AndBible blog.

Quarter Overview

I logged 75.85 hours of development this quarter, almost exactly the same as in Q2. About two thirds of it (48.52 hours) went into the shared Android/iOS codebase, more precisely its first phase, the Compose UI port, which the Q3/Q4 roadmap moved to the front of the queue. A new roadmap post, published alongside this report, covers that work and the plans ahead in more detail. This report focuses on the hours and how they were funded.

Compose port. During the quarter, AndBible was ported to Compose and Kotlin Multiplatform: 45.35 hours of UI modernization plus 3.17 hours of common-codebase groundwork. The Compose version is now functional and nearly finished. The goal for Q4 is to release it to Android users, with a refreshed Material 3 interface, most likely as AndBible 6.0. The project has no budget of its own. Its funding has come from the 13.03 hours left over from the completed reading tracker, which the sponsor allowed me to redirect here, and those hours were used up in July. From then on, all available hours in the generic pool were transferred to this project. Even so, 6.39 hours remained unsponsored (see the "Free Work" column below).

iOS. The native iOS app, the work of Jared Murrell (Primetheus), left beta and is available on the App Store. My part (7.68 hours) was the release pipeline, taking the app through App Store review, and the releases themselves.

Maintenance. General maintenance came to 13.33 hours. That is far less than Q2's 53.58 hours of post-release hardening, as expected now that 5.1 is stable. The stable 5.1 branch still received eight production releases during the quarter (5.1.1107–5.1.1117). They brought: - Crash fixes, many of them in EPUB handling, document synchronisation and dropped Nextcloud connections. - Fixes to verse tracking and scrolling (#3865, #3866). - A document selector on the search results screen. - An "In cloud only" filter in the synced documents view. - Page numbers shown as "x/y". - An update to target Android 16.

Sponsored features. The custom background image / wallpaper commission (#3617) was completed with 1.33 hours of final work, and its small shortfall was covered from the generic pool. A new commission for WebDAV synchronisation (#3837, 4 hours sponsored) arrived in September. It will be built after the Compose release, so its budget carries over.

GitHub Sponsors. The GitHub Sponsors button now has two monthly donors, bringing in a total of $30/month. As noted in the Q2 report, these are donations without consideration: they do not purchase development hours and are not part of the hour pools in this report. Thank you to both donors.

Planning, reporting and support. Planning took 4.97 hours. This category covers roadmap work, such as the Q3/Q4 roadmap, and other dedicated planning. Part of the planning, reporting and support work is also included in the maintenance hours above, since many of the bug fixes respond directly to reports that come in through the support desk. For user support itself, I have received welcome help, and special thanks go to Timmy Braun (timbze).

Sponsorship Flow

The sponsorship flow tables show how development hours are funded. Sponsors purchase development hours through orders. Each pool tracks available hours vs. hours worked. Transfers between pools are configured explicitly and may use a conversion ratio (e.g., feature hours are worth more generic hours due to different rates).

Sponsored shows hours purchased by orders (amount / hourly rate). Hours shows actual development work done. Remaining shows the hour balance — negative values indicate unsponsored work.

Sponsorship Flow - Feature #3837 (WebDAV for Sync)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
September	0.00 h	4.00 h	4.00 h	0.02 h	-	-	3.98 h

Sponsorship Flow - Feature ui-modernization (UI Modernization / Multiplatform preparation)

Month	Carryover	Available	Hours	Transfers	Free Work
July	13.03 h	13.94 h	13.93 h	0.91 h (← generic)	-
August	0.00 h	13.47 h	19.63 h	13.47 h (← generic)	6.16 h
September	0.00 h	14.72 h	14.95 h	14.72 h (← generic)	0.23 h

Sponsorship Flow - Feature #3617 (Custom background image / wallpaper support)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
July	0.50 h	0.00 h	1.33 h	1.33 h	0.83 h (← generic)	-	0.00 h

Column Explanations:

Carryover: Hours carried over from the previous month
Sponsored: Hours purchased by sponsorship orders this month
Available: Total hours available (Carryover + Sponsored ± Transfers)
Hours: Hours of development work done
Transfers: Net hours transferred in/out (already included in Available)
Free Work: Unsponsored hours (negative balance absorbed, does not carry forward)
Remaining: Available − Hours − Free Work, carried to next month (always ≥ 0)

Sponsorship Flow - Generic Development

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
July	2.05 h	20.29 h	20.47 h	8.95 h	-1.87 h (→ ui-modernization, → #3617)	-	11.52 h
August	11.52 h	16.20 h	14.25 h	14.23 h	-13.47 h (→ ui-modernization)	-	0.02 h
September	0.02 h	17.50 h	2.80 h	2.80 h	-14.72 h (→ ui-modernization)	-	0.00 h

Transfers

Date	From	To	Hours (from)	Hours (to)	Note
2026-07	Generic	ui-modernization	0.91 h	0.91 h	Cover UI modernization shortfall from generic pool (pool is in 65 €/h units, 1:1)
2026-07	Generic	#3617	0.96 h	0.83 h	Cover #3617 shortfall from generic pool (converted at 65/75)
2026-08	Generic	ui-modernization	13.47 h	13.47 h	Cover UI modernization shortfall from generic pool (all available generic hours)
2026-09	Generic	ui-modernization	14.72 h	14.72 h	Cover UI modernization shortfall from generic pool (all available generic hours)

Time Tracking Summary

This section shows how development time was actually spent during the reporting period. By Category groups work into broad areas like feature development, bug fixes, and maintenance. By Task provides detailed breakdown of specific tasks, showing exactly what was worked on and for how long. This transparency helps sponsors and users understand how their contributions are being used to improve AndBible.

By Category

Category	Total Hours	Tasks
Generic	25.98 h	ab ios (ID=42), ab maintenance (ID=11), ab planning (ID=33)
Feature	49.87 h	ab ui modernization (ID=48), ab webdav (ID=53), ab custom background 3617 (ID=40), ab ios common cod

By Task

Task	Hours	Category	Ticket
ab custom background 3617 (ID=40)	1.33 h	Feature	#3617
ab ios common codebase (ID=47)	3.17 h	Feature	ui-modernization
ab ui modernization (ID=48)	45.35 h	Feature	ui-modernization
ab webdav (ID=53)	0.02 h	Feature	#3837
ab ios (ID=42)	7.68 h	Generic	N/A
ab maintenance (ID=11)	13.33 h	Generic	N/A
ab planning (ID=33)	4.97 h	Generic	N/A

Charts

The following charts provide visual insights into the development work and funding distribution:

Hours Worked vs Sponsored Hours

Time Distribution by Category

Time Distribution by Task

Summary

In total, 75.85 hours of development work were done this quarter. Roughly 69.5 hours were covered by sponsorship, and 6.39 hours (8%) were unsponsored. This is the same level as in Q2, so the gap between sponsored and actual hours stays small. The recurring monthly sponsorship remains the stable core of the funding.

The balance in this quarter's sponsored hours came from moving all available hours in the generic pool to UI modernization. The generic pool therefore ends the quarter at zero, and there is no buffer going into Q4. The shared-codebase project runs at least until the end of the year, and the current level of sponsorship does not cover it in full. Dedicated sponsorship for this work would make a real difference. Overall funding is still below the target of roughly one full working day per week (around 90 hours per quarter), which would let me commit to a predictable development pace.

Looking ahead, the new roadmap is simple. In Q4, the Compose version will be released to Android users, most likely as AndBible 6.0. In Q1–Q2 2027, the same shared codebase will come to iOS as a unified release.

Best regards & blessings,
Tuomas Airaksinen
Lead developer of AndBible Open Source Project

AndBible for iOS: Now Available on the App Store

Sat, 26 Sep 2026 00:00:00 GMT

Back in July, we announced the public beta of AndBible for iOS — our answer to one of the most frequent requests we’ve received over the years. Today we’re happy to say the beta phase is over: AndBible for iOS is out, and you can download it right now from the App Store.

👉 AndBible: Bible Study on the App Store

It runs on iPhone, iPad, Apple Silicon Macs, and Apple Vision Pro.

From early MVP to (almost) feature-complete

When we launched the beta, we described it as an early MVP — functional, but with gaps and rough edges. Since then the iOS app has come a long way: it’s now close to feature-complete, bringing over most of what AndBible users on Android already rely on:

Multiple Bible translations, commentaries and dictionaries, with split-view for comparing versions side by side
Strong’s concordance integration for digging into the original Greek and Hebrew
Full-text search across your installed documents
Bookmarks, highlights and personal notes
Reading plans with progress tracking and memorization modes
Text-to-speech
Cross-device sync via your own iCloud, Nextcloud or WebDAV account
Access to the same library as on Android — 1,500+ documents in 700+ languages
An optional AI study assistant, if you bring your own API key

As always: AndBible is free, open source, has no ads, and doesn’t collect your data.

None of this would have happened without Jared Murrell (Primetheus), who did the heavy lifting on the iOS port. Thank you, Jared.

What’s next: one codebase, two platforms

The bigger goal behind the iOS port was never just “AndBible, but also on iPhones” — it’s building toward a single, shared codebase that powers both the Android and iOS apps. That work is progressing well, and our target is a unified release around Q1 2027.

As a first step in that direction, the Android app itself is getting a user interface refresh — moving to Material 3 — and we expect that to land already in Q4 2026. It’s the groundwork that makes a shared UI across both platforms realistic.

Try it, and tell us what you think

If you’ve been waiting for AndBible on iOS, now’s the time. Grab it from the App Store, and if you run into bugs or missing features, let us know on GitHub — that feedback is exactly what will get us the rest of the way to feature parity and, eventually, that unified release.

The Road Ahead - Q3/Q4 2026

Sat, 01 Aug 2026 00:00:00 GMT

With the Q2 financial report published, it is time for the roadmap update I promised there and in the iOS beta announcement.

A roadmap is a way of looking ahead rather than a fixed plan. The clearest commitments in the Q2/Q3 roadmap were finishing the 5.1 release with its AI features and bringing AndBible to Apple devices, and both of those happened much as intended — in the case of iOS, rather more than I had promised. What has shifted is the part further out. In April I placed a shared Android/iOS codebase somewhere in 2027, with the Bible Knowledge Graph and the Strong’s annotation pipeline ahead of it in the queue. Since then the iOS work has moved considerably faster than I expected, and I have spent a great deal of time on it, learning and thinking along the way. The upshot is that the shared-codebase project has moved to the front, and the next several months will go into it.

Looking back: Q2 in brief

Q2 was about shipping what Q1 had built, and stabilising the app around it.

AndBible 5.1 went to production on 13 June — the largest release in some time, bringing optional AI assistance, the reading and memorisation progress tracker, and editable “My Documents” pages to everyone. The AI toolset in particular has been received far better than I dared hope, with surprisingly little negative feedback. Document Sync arrived on top of that, letting you synchronise a whole document library across devices through your own Google Drive or Nextcloud storage. Alongside these came a stream of smaller improvements: colour e-ink mode, an ePub reading progress indicator, an option to hide the status bar, and page scrolling with the volume keys in list views.

And in mid-July, AndBible for iOS entered public beta on TestFlight — for iPhone, iPad and Apple Silicon Macs. The credit for that release belongs to Jared Murrell (Primetheus).

In total the quarter came to 75.2 hours of work, about 69 of them sponsor-funded.

Why iOS moved to the front

Jared started the native iOS port back in 2021 — years before the AI era. His approach was to take the AndBible Android codebase as the source of truth and build a separate, natively written iOS app from it, and for most of those years that was hand-written work.

He kept the project to himself for a long time: he was not sure it would ever come to anything, and he did not want the pressure that a publicly announced project brings. He only told us about it earlier this year. Over the spring his AI-assisted workflow has grown markedly more effective as the project has advanced, and the progress has been dramatic: the port has now reached very nearly full parity with the Android version — something I could not have dreamed of.

I see God’s leading in this, particularly through the work Jared has done. He gave the iOS effort the push it needed, and I do not want that work to go to waste. That is why I spent the spring accelerating my own readiness for iOS: I bought a MacBook Air M1 specifically for this project and have been working on the iOS release ever since, most recently the public beta.

But the current iOS version carries one catch: it is a separate codebase. Every feature — each new one, and each of the ones still missing on iOS — has to be built twice. Jared and I both see that this is not a sustainable foundation. What we want instead is a single codebase that serves both platforms well, at full feature parity, with a consistent user interface.

An unplanned proof of concept

What settled the technical question for me was not planned at all. MIDI Recorder is a hobby project of my own, written to record my piano improvisations automatically. I published its Android version in the spring, with the UI written in Compose from the start, and over the summer turned it into a single shared codebase serving both Android and iOS with Kotlin Multiplatform and Compose Multiplatform — the iOS app is built from that same code. Looking back, I take that time as God’s leading: without intending it, I had built exactly the proof of concept I needed for the decisions now in front of me in AndBible.

It clarified my thinking about AndBible’s future considerably. I used to believe that supporting iOS would take more work than this project could ever muster, and for a long time that was a fair assessment. AI-assisted development has cut that effort dramatically, and Jared’s port is itself a demonstration of how much ground can now be covered with modest resources. My own experiment convinced me that Kotlin Multiplatform and Compose Multiplatform are the right foundation for AndBible.

The plan: one codebase, and a modern interface

The work breaks down roughly like this.

Work from both existing codebases. The Android version is the source of truth for the port, with the iOS version alongside it for comparison — it has already solved a number of hard problems well, and there is no reason to solve them twice. The porting itself is done with AI agents.
Rebuild every screen in Compose, one at a time, with the old implementation living side by side with the new one behind a flag. That way nothing is broken while the port is in progress. Most of the architectural change happens here too, screen by screen: a Compose UI is reactive and declarative, so event-driven patterns have to give way as each screen is ported. In places that means changing a fair amount of existing code — sometimes quite a lot of it.
Test all of it carefully once the screens are done, and iterate — fixing every problem that surfaces, step by step. This phase also includes genuine UI/UX improvements: the project is a UI/UX modernisation, so it is the natural moment to modernise interface decisions that have aged.
Ship it to Android first: a beta, then a production release. This stage adds no new features, though existing features may gain UI/UX improvements. AndBible’s interface will get a significant refresh (Material 3) along the way. A change of this scale deserves a round number, so that release would most likely be AndBible 6.0.
Then settle the remaining questions. Nothing is locked down yet, but the likely path is the one the iOS port already took: replacing JSword with libsword. A decision is also needed on the database. I would like to keep Room — Room Multiplatform may be the answer — but there are technical challenges there that I have not thought through to the end.

The project has started well, and it is already at step 3. Every screen has been ported to Compose in a first pass, and the human part of the work is now under way: going through each function in turn, looking closely at how it behaves and how it looks, writing down every shortcoming and defect, and fixing them with AI assistance. This iteration is laborious, and it is the slowest stage of the whole process — but it is also where the fruit is. Usability improves, the interface is modernised and becomes better-looking, and a good many practical improvements arrive along the way.

My target is to have the shared codebase done by the end of 2026. That is a target rather than a commitment — and it assumes I can keep giving AndBible a substantial share of my time, which depends in no small part on the level of sponsorship. My thanks to every sponsor who helps keep that time available.

So the coming months are groundwork more than new invention — and it is good, motivating work to be doing. It will multiply how many people AndBible can reach, and it leaves the app in far better shape for everything that comes after. That does mean the Bible Knowledge Graph and the Strong’s annotation pipeline wait their turn; they remain very much on my list, and building each of their interfaces twice, once per codebase, is precisely the trap the shared codebase exists to escape.

Contributions, and working together

There is a second reason this project matters, beyond maintainability.

I want Jared to have an unobstructed path to contributing to AndBible. He has shown himself to be a first-class developer: highly professional, highly effective with AI tooling, and remarkably committed and hard-working as a volunteer. I do not want to be an obstacle to him. A single codebase, plus a process we build together for making large changes to it safely, is what makes that possible — and we will use AI heavily in that process, naturally.

That brings me to code contributions in general, and I want to be straight about them, because the situation has genuinely changed.

The bottleneck has moved from writing code to making use of what is written. AI can be applied through a great many different processes, and they do not all produce comparable quality — so the demanding part of a contribution is no longer producing it, but establishing that it is sound and that it fits where the project is going. Careful review, not implementation, has become the scarce resource. AI-assisted review helps to a degree, but assessing an unfamiliar change often takes more of my time than building the same thing myself with AI tooling would. That is the honest reason a number of pull requests have gone without the attention their authors deserved, and I am sorry for the silence that has meant in practice.

To be practical about it: until the modernised, shared codebase is in place, larger contributions are not something I can realistically take in. The code is about to move underneath every screen, so a substantial pull request written against today’s implementation would in all likelihood be obsolete before I could merge it. Small, well-scoped fixes remain welcome. If you have something larger in mind, the best route is to open an issue and talk it through with me first, so we can agree on the approach and on the right moment for it — which is exactly what Jared and I are doing at a larger scale.

Ideas themselves are as welcome as they have always been, quite apart from code; a feature request on GitHub is the best way to send one my way.

What’s next

Q3 2026

Work through the Compose port screen by screen: review each function, fix what is lacking, and improve the UI/UX as I go
Take the native iOS app from beta to a production release on the App Store — this is the current iOS version, not the multiplatform one
Catch up on user support and issue triage

Q3–Q4 2026

Finish that review-and-fix pass across the whole app
Material 3 interface refresh
Android beta, then a production release of the modernised UI — most likely as AndBible 6.0
Decisions on the remaining questions: libsword and Room

After that

Full feature parity between Android and iOS on one common codebase
Bible Knowledge Graph and the Strong’s annotation pipeline

Sponsorship and sustainability

My thanks go to the faithful sponsors who make this work possible. Their support is why AndBible is moving at a pace I would have found hard to imagine a couple of years ago.

Part of that pace comes from the way software development itself has changed. AI has reshaped this industry in a remarkably short time, and it now plays a central part in how AndBible is built — which means a sponsored hour buys considerably more than it used to. The work is every bit as demanding: I no longer type most of the code, but I take full responsibility for all of it. What has changed is where the time goes. The hours that once went into typing now go into design, and I can plan larger and more ambitious changes than I would previously have thought possible — this multiplatform project being a case in point.

AndBible development remains a side project alongside near-full-time employment. What I am working towards is one full day per week fully dedicated to AndBible — roughly 90 hours a quarter. Funding at that level, sustained and predictable, is what would let the present momentum continue: regular releases, responsive support, and steady progress on the items above.

If you would like to help make that happen, you can support AndBible through the webshop — either as general development sponsorship or by commissioning a specific feature. Recurring sponsorship by bank transfer is also possible; get in touch for details. There is also a GitHub Sponsors button, added last quarter, for easy recurring monthly support. It differs from the webshop in kind: webshop sponsorship is essentially purchasing development hours from my company, whereas GitHub Sponsors is a plain “thank you” donation.

Thoughts and feedback are genuinely welcome.

God bless,
Tuomas Airaksinen
Lead developer, AndBible Open Source Project

Financial report for Q2/2026

Sat, 18 Jul 2026 00:00:00 GMT

Background

Sykerö Software (Tuomas Airaksinen Software Oy), company of the lead developer, provides a way to sponsor AndBible development. You can support the ongoing development of AndBible financially via the webshop. Recurring sponsorships via bank transfer (EUR, USD, GBP) are also available — reach out for details. The previous quarter’s report is available on the AndBible blog.

A note on GitHub Sponsors. In response to a user request, a GitHub Sponsors button has also been added this quarter for easy recurring monthly support, currently bringing in $20/month. Unlike the webshop and bank-transfer sponsorships, which purchase development hours in return, a GitHub sponsorship is a donation without consideration — a gift supporting my company, with no promise of work attached, nor can there be one. In spirit it is closest to the “Free Work” column in the reports below: a simple, voluntary way to help narrow that gap.

Quarter Overview

Where Q1 2026 was defined by building the AI feature set, Q2 was about shipping it and stabilising the app around it. After a beta cycle running through April and May, AndBible 5.1 reached stable release on 13 June 2026 — the largest release in some time. It brought the optional AI assistant (Gemini, Claude, OpenRouter and others), the reading & memorisation progress tracker, and the new editable “My Documents” pages to all users. Getting a release of this size out cleanly is a substantial undertaking in itself, and a large share of the quarter went into the testing, bug fixing and polish needed to make it happen.

This shows plainly in the time data: maintenance was by far the largest category at 53.58 hours, reflecting the crash resolution, bug fixing and general hardening that a major release demands — from EPUB and font-pack fixes to synchronisation crash handling and improved commentary browsing. In total I logged just over 75 hours of development this quarter — a lower and more sustainable figure than Q1’s 140-hour AI push, and a welcome return to a healthier pace.

Document synchronisation. The headline new development of Q2 was a system for synchronising your entire installed document library across devices — Bibles, commentaries, dictionaries, maps and sideloaded modules alike. It copies the actual document files (not just references to re-download them) through your own personal Google Drive or Nextcloud storage, so nothing passes through third-party servers; transfers run automatically over Wi-Fi in the background, with a preview of what will be uploaded and downloaded and per-device control over which documents to include. This was a major piece of engineering — an incremental cloud-listing cache, a “Sync now” transfer preview, cloud-storage accounting, and a good deal of lifecycle hardening — and it was released as a full, stable feature, announced on the blog in early July.

Reading tracker completed. The reading & memorisation progress tracker (#3586), which was nearly finished at the end of Q1, was completed early this quarter (7.78 hours of final work). With the feature done, the 11.29 hours remaining in its budget have been redirected into a new pool — more on that below.

Smaller improvements. A number of quality-of-life refinements also landed, including a new colour e-ink mode for colour e-ink devices, an unobtrusive reading-progress indicator for EPUB documents, refreshed list views, a “hide status bar” option, and generic volume-key page scrolling.

iOS — a major new front. The most significant strategic development of the quarter was bringing AndBible to iOS. The iOS port itself is overwhelmingly the work of contributor Primetheus (Jared Murrell), whose efforts over an extended period are what made it possible. My own contribution this quarter was to turn it into a real, maintainable platform: I acquired an Apple computer, set up an Apple Developer account, and built out the automation for iOS builds and releases. This led to a public TestFlight beta for iPhone, iPad and Apple Silicon Macs, announced in mid-July. It is an early MVP with gaps and rough edges, but it is a genuine milestone — AndBible now runs on Apple devices, fulfilling years of user requests.

Towards a unified, modern codebase. In the near term, the current iOS beta will mature, as it stands, into a full production release. The larger goal — God willing, perhaps six months to a year away — is a single AndBible in which the Android and iOS versions share one common codebase at full feature parity, together with a modernised UI/UX (a Material 3 redesign). To fund the groundwork, the hours freed up by the completed reading tracker have been transferred into a new “UI Modernization / Multiplatform preparation” pool as a starting budget (13.03 hours). This is the main focus for the quarters ahead, and — much as I did for the AI plans earlier this year — I intend to publish a separate blog post in the coming weeks setting out the vision and roadmap in more detail.

Support and issue triage. User support remained the weakest area, at just 0.82 hours for the whole quarter — the major release and the synchronisation work absorbed most of my available time, and catching up on support and issue triage carries over as an ongoing priority.

Sponsorship Flow

Sponsored shows hours purchased by orders (amount / hourly rate). Hours shows actual development work done. Remaining shows the hour balance — negative values indicate unsponsored work.

Sponsorship Flow - Feature #3617 (Custom background image / wallpaper support)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
May	0.00 h	0.50 h	0.50 h	0.00 h	-	-	0.50 h

Sponsorship Flow - Feature finark (Avoin Raamatunkäännös module)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
May	0.00 h	1.00 h	1.00 h	1.15 h	-	0.15 h	0.00 h

Sponsorship Flow - Feature #3586 (Reading & Memorization tracker)

Month	Carryover	Available	Hours	Transfers	Free Work	Remaining
April	19.07 h	19.07 h	1.43 h	-	-	17.63 h
May	17.63 h	17.63 h	6.35 h	-	-	11.28 h
June	11.28 h	-0.01 h	0.00 h	-11.29 h (→ ui-modernization)	0.01 h	0.00 h

Sponsorship Flow - Feature ui-modernization (UI Modernization / Multiplatform preparation)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
June	0.00 h	0.00 h	13.03 h	0.00 h	13.03 h (← #3586)	-	13.03 h

Column Explanations:

Carryover: Hours carried over from the previous month
Sponsored: Hours purchased by sponsorship orders this month
Available: Total hours available (Carryover + Sponsored ± Transfers)
Hours: Hours of development work done
Transfers: Net hours transferred in/out (already included in Available)
Free Work: Unsponsored hours (negative balance absorbed, does not carry forward)
Remaining: Available − Hours − Free Work, carried to next month (always ≥ 0)

Sponsorship Flow - Generic Development

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
April	0.00 h	16.40 h	16.40 h	15.80 h	-	-	0.60 h
May	0.60 h	16.50 h	17.10 h	23.22 h	-	6.12 h	0.00 h
June	0.00 h	29.30 h	29.30 h	27.25 h	-	-	2.05 h

Transfers

Date	From	To	Hours (from)	Hours (to)	Note
2026-06	#3586	ui-modernization	11.29 h	13.03 h	Reading & Memorization tracker remaining → UI modernization (new project, converted at 75/65)

Time Tracking Summary

By Category

Category	Total Hours	Tasks
Generic	65.30 h	ab ios (ID=42), ab maintenance (ID=11), ab planning (ID=33), ab support (ID=10)
Feature	9.90 h	ab finark (ID=39), ab tracker feat (ID=37), ab ai project (ID=32)

By Task

Task	Hours	Category	Ticket
ab finark (ID=39)	1.15 h	Feature	finark
ab tracker feat (ID=37)	7.78 h	Feature	#3586
ab ai project (ID=32)	0.97 h	Feature (generic-funded)	N/A
ab ios (ID=42)	5.97 h	Generic	N/A
ab maintenance (ID=11)	53.58 h	Generic	N/A
ab planning (ID=33)	4.93 h	Generic	N/A
ab support (ID=10)	0.82 h	Generic	N/A

Charts

The following charts provide visual insights into the development work and funding distribution:

Hours Worked vs Sponsored Hours

Time Distribution by Category

Time Distribution by Task

Summary

In total, 75.20 hours of development work were done this quarter, of which roughly 69 hours were covered by sponsorship and about 6 hours (8%) were unsponsored. This is a marked improvement on Q1, where unsponsored work reached 31% — the gap between sponsored and actual hours has essentially closed. In euro terms, revenue was lower than in Q1 (whose total had been boosted by one-off feature commissions), but the recurring monthly sponsorship remains the stable core of the funding; the full figures are in the revenue table below.

The funding balance was therefore much healthier than in Q1, even though total revenue was lower. The quarter’s work was almost entirely sponsor-funded, which reflects both a more sustainable pace and the maintenance-heavy nature of stabilising a major release. Sponsorship still falls short of the target of roughly one full working day per week (around 90 hours per quarter), which would let me commit to a predictable development pace with confidence — but the shortfall this quarter was in overall capacity rather than in unpaid work.

Looking ahead to Q3, the priorities follow directly from the iOS beta: unifying the Android and iOS codebases, modernising the UI/UX (a Material 3 redesign), and growing the iOS version towards feature parity — while catching up at last on user support and issue triage, which remained the weakest area this quarter. As noted above, I intend to publish a separate roadmap blog post in the coming weeks that will set out this multiplatform vision in more detail.

Closing Words

I want to express my heartfelt gratitude to every AndBible sponsor for making it possible to maintain, support and continually develop the app. A great deal happened this quarter — a big release brought to stable, a powerful new document-synchronisation feature, the first steps of AndBible onto iOS, and a great deal of quieter bug fixing that kept everything running smoothly — and it is your support that makes all of it possible.

Above all, I remain deeply grateful to God for how the project continues to develop. It is a privilege to work on software that helps people engage with Scripture, and I’m genuinely excited about the road ahead: bringing AndBible to more platforms, and giving the app the modern, polished interface its users deserve.

Best regards & blessings,
Tuomas Airaksinen
Lead developer of AndBible Open Source Project

AndBible for iOS: The Public Beta Is Here

Fri, 17 Jul 2026 00:00:00 GMT

For years, one of the most frequent requests we have received has been for an iOS version of AndBible. We’re glad to say that it is now within reach: the AndBible iOS public beta is open.

👉 Join the beta on TestFlight: https://testflight.apple.com/join/sB7guYsk

In the Q2/Q3 roadmap we mentioned this effort, which had been growing quietly for some time. It has now reached the point where anyone with an iPhone or iPad can install AndBible and try it — and it runs nicely on Apple Silicon Macs (macOS) as well. This is an early MVP: it currently covers only a subset of the Android version’s features, so expect some gaps and rough edges. Even so, the core is there: powerful, offline Bible study on Apple devices, free and open source as always.

Our thanks go to Jared Murrell (Primetheus), who has done the work on the iOS port over a long period. It’s a significant milestone for the project, and the credit for this release belongs entirely to him.

If you try the beta, please share your feedback and report issues on GitHub — every report helps us on the way to a 1.0 release.

Finally, it’s worth noting that work has now begun on unifying the Android and iOS codebases so the two can share a common foundation, and I am now actively involved in that effort. As part of this, AndBible’s user interface will also get a significant update (Material 3). Once the shared codebase is in place, we expect the two versions to reach full feature parity. I’ll have more to say about it soon, in our upcoming quarterly report and the roadmap update that will be published alongside it.

New feature: Reading Progress indicator for ePub documents

Sun, 05 Jul 2026 00:00:00 GMT

Ever found yourself deep in a lengthy EPUB commentary or Bible book, wondering how much further you have to go? AndBible's new Reading Progress indicator answers exactly that — at a glance, and without getting in your way.

Watch on YouTube

What it does

When enabled, a small, unobtrusive text overlay appears in the corner of the reading view and updates live as you scroll. It tells you how far you’ve read through what you’re currently reading:

EPUB books: progress through the whole book, shown as a percentage plus an estimated page — for example 47% · 142/300.
Bibles and commentaries: progress through the current book, shown as a percentage plus your chapter — for example 47% · 23/50.

The indicator is smart about context. The meaning of “how far through” adapts to what you’re reading, so a single setting does the right thing everywhere.

New feature: Document Sync

Sat, 04 Jul 2026 00:00:00 GMT

Watch on YouTube

Your Bible library, on every device: introducing Document Sync

If you use AndBible on more than one device — a phone and a tablet, an old phone and a new one — you know the small frustration of setting everything up again. You carefully install your Bibles, commentaries, dictionaries and other documents on one device, then have to hunt them all down again on the next.

Document Sync takes care of that for you. Turn it on, and the documents you install on one device are copied to your own cloud storage and re-installed on your other devices automatically. Set up a new device, enable sync, and your whole library comes down with it.

What gets synced

Everything you’ve installed, regardless of how you installed it:

Bibles, commentaries, dictionaries, maps and other books from the download list
Sideloaded documents — modules you added from a ZIP file
MyBible, MySword, eSword and EPUB documents

Because AndBible copies the actual document — not just a “go download this again” note — it works even for sideloaded modules and documents from custom repositories that can’t simply be re-downloaded elsewhere.

It uses your own cloud account

Document Sync uses the same cloud connection as the rest of AndBible’s sync — your own Google Drive or Nextcloud account. Your documents are stored in your private cloud space, not on anyone else’s server.

Turning it on

Open Settings → Synchronization and switch on Documents (it sits in the list of sync categories alongside Bookmarks, Workspaces and the rest). After you sign in, AndBible shows you exactly what’s about to happen — for example, “Upload 12 (45 MB) · Download 3 (8 MB)” — so there are no surprises before anything transfers. Confirm, and syncing begins in the background.

From then on it’s automatic: install a document on one device and it shows up on the others; upgrade a document and the newer version follows. Transfers run quietly in the background with a notification, so they never hold up what you’re doing.

The Synced Documents screen

Settings → Synchronization → Synced documents gives you one place to see and manage everything — both what’s installed on this device and what’s in your cloud. Each document shows its status: Synced, On this device only, In cloud only, Update available, or Blocked.

From here you can:

Download a document that’s in the cloud but not yet on this device
Push a document that’s only on this device up to the cloud
Block a document from this device — handy when you don’t want a large document taking up space on, say, an older phone, while keeping it synced on your others
Remove a document from the cloud (and, when sync is on, from all your devices)
Sync now — a manual one-time sync, useful if you prefer to keep automatic sync off and pull things over by hand

You can also pull down on the list to refresh it.

On your terms

Wi-Fi only (default): automatic transfers wait for an unmetered connection, so Document Sync won’t eat into your mobile data. Manual actions always go through immediately when you ask for them.
Per-device choices: blocking a document only affects the device you block it on; your other devices keep syncing it.
Manual mode: you don’t have to enable automatic sync at all. As long as you’re signed in to your cloud account, you can open Synced Documents and move documents to and from the cloud by hand whenever you like.

A note on removing documents

Removing a document behaves the way you’d expect for each situation:

With automatic sync on, Remove from all devices removes it from the cloud and from your devices — including the one you’re holding — so you don’t end up with a stray copy that’s no longer being synced.
With automatic sync off, Remove from cloud clears it from your cloud storage but leaves the copy on this device untouched.

Preview of new features of upcoming 5.1 version

Sat, 18 Apr 2026 00:00:00 GMT

I made a video for Beta release, so you can take a look if you are interested to see what kind of features there will be soon in AndBible 5.1.

Watch on YouTube

The Road Ahead - Q2/Q3 2026

Sat, 11 Apr 2026 00:00:00 GMT

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. Jared Murrell (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.

Jared 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 Jared 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 Jared 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 Jared 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.

God bless,
Tuomas Airaksinen
Lead developer, AndBible Open Source Project

Financial report for Q1/2026

Fri, 10 Apr 2026 00:00:00 GMT

Watch on YouTube

Background

Quarter Overview

The defining theme of Q1 2026 was developing AI-powered features for AndBible — bringing LLM capabilities directly into the app for users. I outlined the vision and roadmap in a blog post in early January, and I’m pleased to report that the entire feature set is now essentially implemented as planned. What remains is testing, bug fixing, and prompt refinement, with the goal of shipping the AI features to production during Q2. The AI integration — including a multi-provider LLM agent system with Bible-aware tools, an AI document system, a prompt editor, and deep integration points throughout the app — is arguably the most ambitious feature addition to AndBible in the past couple of years, and I’m genuinely thrilled with how all the pieces have come together.

This work came at a cost: the AI project consumed 75.72 hours this quarter (101.69 hours total since Q4 2025), and since there is no dedicated feature sponsorship for it, all of that was drawn from the generic development pool. As a result, the generic pool accumulated 43.23 hours of free (unsponsored) work over the quarter, meaning roughly 43 hours (~2,810 €) of the AI work was effectively self-sponsored. The detailed sponsorship data below tells the full story, but in short: community sponsorship doesn’t come close to covering this implementation in full. That said, I consider this a worthwhile investment — the feature is genuinely exciting and I believe it will be a valuable addition for users.

Business restructuring and rate adjustment. At the start of the year, I gained a significant new sponsor whose recurring monthly commitment provides a more stable funding base for ongoing development. This prompted a restructuring from a sole proprietorship to a limited liability company (Tuomas Airaksinen Software Oy, trading as Sykerö Software), which is considerably more tax-efficient since, as a side business alongside near-full-time employment (4 days/week), the sole proprietorship income was taxed at a high marginal rate, whereas a limited company benefits from corporate tax and preferential dividend taxation. At the same time, I made the first-ever hourly rate adjustment, raising both rates by 5 €/h (generic: 60 → 65 €/h, feature: 70 → 75 €/h) based on the Finnish consumer price index. Going forward, I intend to make a similar index-based adjustment each January; since this was the first increase since the project started, the step was larger than future adjustments will be.

Additionally, the new company’s Wise business account now enables recurring sponsors to pay via direct bank transfer in EUR, USD, and GBP (and possibly others). Note that bank transfer sponsorships require a separate invoice and agreement, so the webshop remains the recommended option for smaller or one-time contributions.

Quarterly planning and reporting. The new sponsor requires quarterly roadmap planning and progress reporting (tracked as “ab planning” in the time data, 6.98 hours this quarter). I carry out this work within sponsored hours, and I also publish these planning reports as articles on the AndBible blog.

Sponsored feature work. In addition to the AI work, I worked on three sponsored feature commissions during Q1. The first was a collection of smaller improvements (8.00 hours sponsored, 4.90 hours worked), which was completed and its remaining 3.10 hours transferred to the tracker commission below. The second was a maintenance work pool (7.50 hours sponsored, 14.15 hours worked) — this is essentially generic development, but the sponsor specifically wanted to earmark their contribution for non-AI work such as bug fixes and general maintenance. The shortfall was covered by a transfer from the generic pool. The third was a comprehensive reading and memorization progress tracking system (#3586) with automatic reading detection, progress statistics, calendar heatmaps, and reading cycle support. This work is nearly complete — 19.07 hours remain in the budget, which will be used for final bug fixes and polish, with any remaining hours allocated as directed by the sponsor.

Support, issues, and pull requests. One area that suffered this quarter was user support and issue triage. After January, support work dropped to just 1.97 hours for the entire quarter, and I have not been reading through open issues except those directly related to the AI project and the sponsored tracker feature. This is something I need to address going forward. On the pull request side, we’ve seen an increase in community-contributed pull requests — likely driven by the growing use of AI coding assistants. I have not had time to properly review most of them. A refined contribution policy is under development to ensure that high-quality contributions make it into the codebase efficiently, while avoiding spending disproportionate review time on lower-quality AI-generated submissions.

Report Format Changes

Starting with this quarter, the sponsorship flow tables have switched back to an hour-based format. The motivation is clarity: orders purchase hours, tracked work consumes hours, and transfers between pools are straightforward hour-to-hour operations (with a conversion ratio when rates differ). The previous euro-based format made pool transfers and carryovers harder to follow. A “Free Work” column has been added to clearly show unsponsored hours — when a pool’s balance goes negative, the deficit is absorbed as free work and the carryover resets to zero instead of propagating a negative balance to the next month. The old “Sponsored %” column has been removed, and inter-pool transfers are now shown in a dedicated Transfers table. The hours comparison chart now also includes a “Free Work” bar alongside the existing “Total Hours Worked” and “Sponsored Hours” bars, making the unsponsored portion visible at a glance.

Sponsorship Flow

Sponsored shows hours purchased by orders (amount / hourly rate). Hours shows actual development work done. Remaining shows the hour balance — negative values indicate unsponsored work.

Sponsorship Flow - Feature #3388 (Small features collection)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
January	0.00 h	8.00 h	8.00 h	3.88 h	-	-	4.12 h
February	4.12 h	0.00 h	4.12 h	1.02 h	-	-	3.10 h
March	3.10 h	0.00 h	0.00 h	0.00 h	-3.10 h (→ #3586)	-	0.00 h

Sponsorship Flow - Feature #3588 (Maintenance work)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
January	0.00 h	7.50 h	7.50 h	6.50 h	-	-	1.00 h
February	1.00 h	0.00 h	7.65 h	7.65 h	6.65 h (← generic)	-	0.00 h

Sponsorship Flow - Feature #3586 (Reading & Memorization tracker)

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
March	0.00 h	37.50 h	40.60 h	21.53 h	3.10 h (← #3388)	-	19.07 h

Column Explanations:

Carryover: Hours carried over from the previous month
Sponsored: Hours purchased by sponsorship orders this month
Available: Total hours available (Carryover + Sponsored ± Transfers)
Hours: Hours of development work done
Transfers: Net hours transferred in/out (already included in Available)
Free Work: Unsponsored hours (negative balance absorbed, does not carry forward)
Remaining: Available − Hours − Free Work, carried to next month (always ≥ 0)

Sponsorship Flow - Generic Development

Month	Carryover	Sponsored	Available	Hours	Transfers	Free Work	Remaining
January	0.00 h	23.80 h	23.80 h	17.40 h	-	-	6.40 h
February	6.40 h	20.05 h	19.80 h	36.18 h	-6.65 h (→ #3588)	16.38 h	0.00 h
March	0.00 h	18.80 h	18.80 h	45.65 h	-	26.85 h	0.00 h

Transfers

Date	From	To	Hours (from)	Hours (to)	Note
2026-03	#3388	#3586	3.10 h	3.10 h	Small features remaining → Reading tracker
2026-02	Generic	#3588	6.65 h	6.65 h	Cover #3588 shortfall from generic pool

Time Tracking Summary

By Category

Category	Total Hours	Tasks
Feature	102.15 h	ab ai project (ID=32), ab tracker feat (ID=37), ab small feats #3587 (ID=34)
Generic	37.67 h	ab maintenance (ID=11), ab maintenance #3588 (ID=35), ab planning (ID=33), ab support (ID=10)

By Task

Task	Hours	Category	Ticket
ab small feats #3587 (ID=34)	4.90 h	Feature	#3388
ab tracker feat (ID=37)	21.53 h	Feature	#3586
ab ai project (ID=32)	75.72 h	Feature (generic-funded)	N/A
ab maintenance (ID=11)	14.57 h	Generic	N/A
ab planning (ID=33)	6.98 h	Generic	N/A
ab support (ID=10)	1.97 h	Generic	N/A
ab maintenance #3588 (ID=35)	14.15 h	Generic (earmarked)	#3588

Charts

The following charts provide visual insights into the development work and funding distribution:

Hours Worked vs Sponsored Hours

Time Distribution by Category

Time Distribution by Task

Summary

In total, 139.82 hours of development work were done this quarter, of which roughly 97 hours were covered by sponsorship and 43 hours (31%) were unsponsored work — primarily due to the AI feature effort. Revenue for the quarter was 7,618 €, a significant increase from Q4 2025 (1,335 €), largely thanks to the new recurring sponsor and the feature commissions.

While the funding situation has improved significantly compared to late 2025, sponsorship still falls short of the target: roughly one full working day per week (around 90 hours per quarter). Reaching that level consistently would allow me to commit to a predictable development pace with confidence. This quarter’s high free work percentage was largely driven by the AI feature, which put me in a particular creative flow that was hard to step away from — but that level of unsponsored contribution is not sustainable in the long run.

Looking ahead to Q2, the priorities are: shipping the AI features to production, releasing an MVP of the iOS version, finishing the reading tracker, catching up on user support and issue triage, and establishing a clearer contribution policy for community pull requests. I intend to publish a separate roadmap blog post soon that will cover the forward-looking plans in more detail.

Closing Words

I want to express my heartfelt gratitude to every AndBible sponsor for making it possible to maintain, support, and continually develop the app. This quarter in particular, the gap between sponsored and actual work hours was significant, but the enthusiasm from sponsors — both new and returning — gives me confidence that the project is heading in a good direction.

Above all, I’m deeply grateful to God for how things have developed. My personal motivation for the project has grown enormously — knowing how many people are walking alongside me in this work makes all the difference. It is a privilege to work on software that helps people engage with Scripture, and I look forward to shipping the AI features and returning to a more balanced workload in Q2.

Best regards & blessings,
Tuomas Airaksinen
Lead developer of AndBible Open Source Project

P.S. Roadmap post "The Road Ahead - Q2/Q3 2026" has been published!

New Printable Flyers Available

Sat, 17 Jan 2026 00:00:00 GMT

Want to help spread the word about AndBible Bible Study? We’ve created printable promotional flyers that you can download and share with your church, Bible study group, or community.

The two-page flyers include an overview of the app, key features, and a QR code for easy downloading. Two versions are available:

Home printing version – optimized for standard home printers
Professional printing version – high-quality version for print shops

Download the flyers and print as many copies as you need. They’re perfect for church bulletin boards, Bible study meetups, conferences, or anywhere people might benefit from a powerful, free Bible study tool.

Download the flyers here

Thank you for helping others discover AndBible!

My AI plans to AndBible

Mon, 05 Jan 2026 00:00:00 GMT

I've been working on integrating AI capabilities into AndBible, and there have been enquiries about the plans and timeline. Rather than answering piecemeal, I decided to share this roadmap document that outlines the vision for AI features in AndBible.

Everything described below is still in development — no AI features have been released yet. This document represents the plan and direction, not finished functionality. I'm sharing it to be transparent about what's coming and to invite feedback from the community.

Introduction

AndBible is expanding its capabilities with AI-powered features designed to enhance Bible study. This roadmap outlines our vision for integrating Large Language Model (LLM) technology into AndBible, giving users powerful new tools while maintaining full control over their data and AI interactions.

Goal: make AI a helpful companion for Bible study — one that saves time on routine tasks, helps discover connections you might miss, and assists in organizing your study materials.

Guiding Principles

Completely Opt-In — AI features are hidden and inactive by default. Nothing AI-related appears in the interface until you choose to enable it by configuring your own API connection. If you prefer AndBible without AI, you’ll never see these features.
User Control — When enabled, you decide when and how AI is used. All features are customizable, and write operations require explicit permission.
Transparency — See exactly what the AI is doing through a real-time status log. No hidden operations.
Flexibility — Use any OpenAI-compatible API endpoint. This includes commercial services (OpenAI, xAI Grok, Mistral, Google Gemini, Groq, OpenRouter, and others) or your own self-hosted server (Ollama, vLLM, etc.). Create custom prompts tailored to your study needs.

Core Features

LLM Mode: Automatic Document Processing

Process Bible text automatically as you read, with results displayed inline.

Use cases:

Translate commentaries and study resources into your native language (many excellent resources exist only in English or other major languages)
Get AI-assisted analysis of original language words in Strong’s-enabled Bible modules
Apply custom transformations (summaries, simplifications) to any document

How it works: Enable LLM Mode in Text Display Settings, select a prompt (e.g., “Translate to Finnish”), and the text is processed automatically as you read. Results are cached locally — the same content won’t be processed twice.

Prompt Manager: Your AI Instructions

A central place to create, edit, and organize AI prompts that define what the AI should do.

Built-in prompts (examples, subject to change):

Translate to UI language — Automatic translation to your app’s language
Summarize — Concise summaries of passages or chapters
Explain verses — Synthesize insights from installed commentaries
Word study — Analyze original language words with Strong’s definitions
Create thematic bookmarks — Identify and bookmark key passages

Custom prompts: Create your own for specific study tasks. Configure where each prompt appears:

Text Display Settings (automatic processing)
Verse selection menu (One Tap Actions)
Text selection context menu
Window menu (document-level actions)

AI Actions: On-Demand Assistance

Manually triggered AI operations on selected text or documents.

Example workflows:

Action	What happens
Commentary summary	AI reads all installed commentaries for selected verses and creates a unified summary
Cross-reference analysis	AI explains connections between related passages
Study notes generation	AI creates structured notes for a chapter, saved to your documents
Thematic bookmarking	AI identifies important themes and creates labeled bookmarks

Results appear in different places depending on the action: summaries and analyses go to My Documents, bookmarks appear in your bookmark list, StudyPad entries in your StudyPads. All AI-created content is tracked in the status log, making it easy to review what the AI has done and remove unwanted items.

AI-Powered Search

Traditional Bible search finds exact word matches. AI search understands meaning and context.

How it works: Describe what you’re looking for in natural language, and the AI returns relevant Bible references — even when your search terms don’t appear in the text.

Examples:

“Passages about God’s faithfulness during trials” → Returns relevant verses from Psalms, Job, Romans, etc.
“Jesus teaching about money” → Finds parables and teachings even without the word “money”
“Old Testament prophecies about the Messiah’s suffering” → Returns Isaiah 53, Psalm 22, etc.

AI search is integrated into the existing search interface as an additional search mode.

AI-Enhanced Cross-References

Some Bible modules include cross-references, but coverage varies. AI can suggest additional connections based on:

Thematic similarities
Parallel narratives
Prophetic fulfillments
Linguistic patterns in original languages
Theological concepts

How it works: Like LLM Mode, this is enabled in Text Display Settings and configured via Prompt Manager. When active, AI-generated cross-references appear as footnotes in the Bible text alongside regular cross-references — seamlessly integrated into your reading experience.

My Documents & AI Links

Create and manage personal documents within AndBible, with special support for AI-generated content.

Features:

Create study documents with multiple pages
Supports Markdown formatting with Scripture links
Documents appear in the document selector alongside installed books
Full bookmark and StudyPad integration

AI Links — Interactive AI Content:

AI-generated documents can include special links that trigger further AI actions. For example:

## The Beatitudes (Matthew 5:3-12)

Jesus opens the Sermon on the Mount with eight blessings...

**Explore further:**
- [Compare with Luke's version](ai://compare?refs=Matt.5.3-12,Luke.6.20-26)
- [Word study: "Blessed" (μακάριος)](ai://word-study?strongs=G3107)
- [Find similar teachings](ai://search?query=Jesus+teachings+on+humility)

Clicking these links triggers the corresponding AI action with pre-configured parameters. This creates interactive study documents that enable deeper exploration without manual prompt configuration.

What the AI Can Access

The AI can read from and write to various parts of AndBible, with appropriate permissions.

Read capabilities (automatic):

Bible text from installed translations
Commentary entries
Cross-references
Dictionary and Strong’s definitions
Your bookmarks, labels, and StudyPads

Write capabilities (requires permission):

Create bookmarks with notes
Add entries to StudyPads
Create new labels

Note: A dedicated “AI Documents” document is available where AI can save its output without requiring separate permission. This keeps AI-generated content organized in one place by default.

All AI-created content is marked with its source, so you always know what was generated by AI.

Control & Management

Permissions System

You stay in control:

Write operations require explicit approval
Permission dialog shows exactly what the AI wants to do
Options per operation type: “Always ask,” “Allow for session,” “Always allow,” or “Deny”

Status visibility:

Real-time log shows AI operations as they happen
See what data is being read and what changes are being made
Cancel operations at any time

Cache Manager

Manage your locally cached AI-processed content:

View cache contents — See what’s been processed and when
Selective deletion — Remove specific entries or clear by date range
Invalidation — Mark old entries for re-processing (e.g., after switching to a better model)
Storage info — Monitor cache size and manage disk usage

Useful when you want to re-process content with improved prompts or a different LLM provider.

Cost Tracking

Monitor how much your AI usage costs:

Configure pricing — Set per-token prices for your LLM provider (input and output tokens)
Per-operation costs — See how much each AI action costs before and after execution
Usage history — Track cumulative costs over time
Budget awareness — Make informed decisions about which operations to run

Since different providers have vastly different pricing, this helps you stay in control of your spending.

Privacy

Your API, your data — Configure your own API endpoint (commercial providers or self-hosted servers)
No third-party data sharing — Data only goes to your chosen API provider
Local caching — Processed content stored on your device
Device sync — When enabled, AI-generated documents, cached content, and custom prompts sync between your devices via Google Drive or Nextcloud (using AndBible’s existing sync feature), just like bookmarks and notes etc.

Technical Notes

API Compatibility: Works with any OpenAI-compatible endpoint
Caching: Processed content cached locally to avoid redundant API calls
Offline Access: Cached content available offline; new processing requires internet
Sync Support: AI content and custom prompts sync between devices

Summary

AndBible’s AI features are designed to enhance your Bible study by:

Benefit	How
Remove language barriers	On-the-fly translation of any text
Discover connections	AI-powered search and cross-references
Save time	Automated summaries and commentary synthesis
Organize insights	AI-assisted bookmarking and note generation
Enable exploration	Interactive AI links for deeper study
Maintain control	Transparent permissions and customizable prompts

These tools make deep Bible study more accessible while keeping you firmly in charge of your study journey.

Financial report for Q4 / 2025

Thu, 01 Jan 2026 00:00:00 GMT

Watch on YouTube

Background

Tuomas Airaksinen Consulting, company of the lead developer, provides a way to sponsor AndBible development. You can support the ongoing development of AndBible financially via the webshop.

See also: financial report for Q4/2023, Q1/2024, Q2/2024, Q3/2024, Q4/2024, Q1/2025, Q2/2025 and Q3/2025.

I have again revised reporting to some extent, trying to make it clearer.

"Free work" correction notice for Q1-Q3/2025 reports

First I want to let you know about a small bug that I noticed when creating report for Q4 in my report generating script. When feature development work exceeded its sponsorship (shown as negative values in the "From Features" column), this unsponsored feature work was not being counted as "Free Work".

The "Free Work" column in the Generic Development tables was underreported in previous quarters. The corrected values are:

Quarter	Month	From Features	Old Free Work	Corrected Free Work
Q1	January	-732.50 €	293.00 €	1025.50 €
Q1	March	-19.00 €	0.00 €	19.00 €
Q2	April	-339.00 €	0.00 €	339.00 €
Q2	May	-239.00 €	808.65 €	1047.65 €
Q3	July	-1.00 €	73.77 €	74.77 €
Q3	August	-103.00 €	317.80 €	420.80 €

The "Free Work" column from now on correctly includes both:

Generic development work not covered by available funding (as before)
Feature development work that exceeded its sponsorship (previously missing)

This provides a more accurate picture of the total volunteer/unsponsored development effort. All other figures in the reports (revenue, hours, costs, etc.) remain unchanged. Only the "Free Work" calculation was affected.

Sponsorship Flow

The sponsorship flow tables show how funding for AndBible development works. When users sponsor specific features, their money is allocated to pay for the development work on those features. If a feature receives more sponsorship than needed, the excess helps fund general development. If a feature needs more work than its sponsorship covers, the shortfall is covered by general development funding when possible, or becomes volunteer work when no funding is available.

Each feature table shows month-by-month how sponsorship money was used: Revenue is money received from sponsors, Cost is what the development work actually cost, and Remaining shows leftover sponsorship money that carries forward to next month or gets transferred to general development when the feature is completed.

Sponsorship Flow - Feature #3570 (LLM features)

Month	Carryover	Revenue	Available	Cost	Remaining	To Generic
December	0.00 €	0.00 €	0.00 €	1558.00 €	0.00 €	1558.00 € (25.97 h work)

Rate: 60.00 €/h

Sponsorship Flow - Feature #1982 (In search result window add button 'Change displayed language')

Month	Carryover	Revenue	Available	Cost	Remaining	To Generic
November	0.00 €	105.00 €	105.00 €	49.00 €	56.00 €	56.00 € (surplus)

Rate: 70.00 €/h

Sponsorship Flow - Feature #3551 (Study pad cursor editing position and Studypad search)

Month	Carryover	Revenue	Available	Cost	Remaining	To Generic
November	0.00 €	0.00 €	0.00 €	672.00 €	0.00 €	672.00 € (11.20 h work)

Rate: 60.00 €/h

Column Explanations:

Carryover: Funding balance carried over from the previous month
Revenue: Sponsorship money received this month
Available: Total funding available (Carryover + Revenue)
Cost: Actual cost of work done
Remaining: Funding balance after costs, carried to next month
To Generic: Work exceeding feature budget (shown as € with hours) or surplus funds transferred when feature is completed

Sponsorship Flow - Generic Development

Month	Carryover	Revenue	From Completed	Available	Feature Cost	Generic Cost	Remaining	Free Work	Sponsored %
October	0.00 €	1032.00 €	0.00 €	1032.00 €	0.00 €	495.00 €	537.00 €	0.00 €	100 %
November	537.00 €	60.00 €	56.00 €	653.00 €	672.00 €	472.00 €	0.00 €	491.00 €	57 %
December	0.00 €	138.00 €	0.00 €	138.00 €	1558.00 €	55.00 €	0.00 €	1475.00 €	9 %

Rate: 60.00 €/h

Column Explanations:

Month: Calendar month name
Carryover: Funding balance carried over from the previous month
Revenue: Generic development sponsorship received this month
From Completed: Funding transferred from completed features
Available: Total funding available (Carryover + Revenue + From Completed)
Feature Cost: Cost of unsponsored feature work (feature overflow)
Generic Cost: Cost of generic development work
Remaining: Funding balance after all costs, carried to next month
Free Work: Work not covered by available funding
Sponsored %: Percentage of total costs covered by sponsorship funding

Time Tracking Summary

AndBible development is much more than just writing code implementing new features. Below is a description of how my time is distributed across different tasks:

Code Review: This task involves reviewing contributions and changes submitted by other developers. It's a crucial process that ensures high-quality code, consistent coding standards, and reduces potential issues before they reach production.

Maintenance: Maintenance includes tasks necessary for keeping the AndBible application stable and up-to-date. This covers bug fixes, dependency updates, refactoring code, and optimizing performance to ensure the app continues to function smoothly.

Support: Support tasks involve actively engaging with users and developers through email and GitHub. This includes reading and responding to user inquiries, addressing bug reports, participating in discussions, and providing guidance to help resolve issues quickly.

Feature Development: This involves developing new functionalities and improvements based on user needs and sponsor requests. Feature development is essential for the ongoing enhancement and expansion of AndBible capabilities.

By Category

Category	Total Hours	Tasks
Feature	37.87 h	ab ai project (ID=32), ab 1982 language (ID=31), ab feature development (ID=2)
Generic	17.03 h	ab maintenance (ID=11), ab support (ID=10), ab feature development (ID=2)

By Task

Task	Hours	Category	Ticket
ab 1982 language (ID=31)	0.70 h	Feature	#1982
ab ai project (ID=32)	25.97 h	Feature	#3570
ab feature development (ID=2)	14.93 h	Feature	#3551
ab maintenance (ID=11)	8.45 h	Generic	N/A
ab support (ID=10)	4.85 h	Generic	N/A

Summary

The fourth quarter was dominated by work on the new LLM/AI features, which consumed roughly half of all development time during this period. I started this project because I saw enormous potential in it, and personally it excited and inspired me significantly. Even though there was no sponsorship for it, I wanted to sponsor the work myself through my own volunteer contribution. This is a substantial project and is expected (Lord willing) to be completed during spring 2026.

Two other features were also completed during this quarter: improvements to Study Pad cursor editing and search functionality, and a language selection button for the search results window. The latter was the only fully sponsored feature work this quarter.

Another highlight of the quarter was welcoming a new team member: Tobe Iheme joined the project as a part-time developer trainee. He assists with bug fixes, user support, and other project tasks, freeing up more of my time for core development work.

Overall, Q4 saw a noticeable drop in sponsorship coverage compared to earlier in the year, with December being particularly lean. In the long term, a continued decline in sponsorship would naturally reduce my ability to participate in the project at the level I have before. However, I remain positive about the future in this regard. Development continued at a steady pace throughout the quarter, reflecting a commitment to moving AndBible forward regardless of funding levels. Maintenance and user support work continued as usual alongside the feature development.

Closing words

I want to express my heartfelt gratitude to every AndBible sponsor for making it possible to maintain, support, and continually develop the app. It brings me great joy and encouragement to see others sharing the financial burden and joining me in supporting the ongoing development of AndBible.

Best regards & blessings,
Tuomas Airaksinen
Lead developer of AndBible Open Source Project

New feature: Search StudyPads that have certain content

Thu, 27 Nov 2025 00:00:00 GMT

In this short video I will show you can now search your studypads based on content.

Watch on YouTube

New feature: StudyPad edit position

Thu, 27 Nov 2025 00:00:00 GMT

In this new short tutorial video I will show how you can now edit your studypads not just at the end of the document but anywhere, thanks to new "edit position" feature.

Watch on YouTube

Developer trainee for AndBible project

Thu, 13 Nov 2025 00:00:00 GMT

I'm excited to share some news with the AndBible community! Thanks to your continued support through sponsorships, I have decided to employ a developer trainee for AndBible open source project.

How your sponsorship makes a difference

First and foremost, I want to emphasize that all sponsored hours continue to be worked by me personally, at 100%. Your direct support for AndBible development hasn't changed – every hour you sponsor goes directly into the features, bug fixes, and improvements I work on.

However, thanks to the overall sustainability that your sponsorships have helped create, I'm now able to take an additional step: hiring a trainee developer using the company's revenue.

Meet our new team member

I'm pleased to announce that Tobe Iheme, a Nigerian student currently studying in Finland, has joined the AndBible project as a Software Developer Trainee. I know Tobe personally through our church community – we attend the same congregation here in Finland.

Tobe brings the project experience from his background in mobile application development in Nigeria, and is now gaining additional skills and experience while studying in Finland. You can check out his work on GitHub. This is a part-time position (1 working day per week) running through the end of 2025, with the possibility of extension into 2026.

Tobe will be working on:

Bug fixes and implementing new features
User support through our email helpdesk system
Writing and organizing bug tickets based on user reports
Other AndBible project-related tasks as needed

Why this matters

This arrangement is good for all of us:

For AndBible: More development capacity means bugs get fixed faster and new features can be implemented. Fresh perspectives, additional capacity for user support
For Tobe: An opportunity to gain real-world software development experience, earn some income while studying, and contribute to a meaningful open-source project
For me: it enables me to use more of my time to the actual development of useful features to the app, as I get help in other areas of the project

Thank You!

None of this would be possible without the generous support of our sponsors and the broader AndBible community. Your contributions – whether financial sponsorship, bug reports, feature suggestions, or simply spreading the word – continue to make AndBible better for everyone.

If you'd like to support AndBible's continued development and growth, please consider becoming a sponsor. Every contribution helps ensure that this free, open-source Bible app can continue to serve users around the world.

Thank you for being part of the AndBible journey!

- Tuomas Airaksinen
AndBible Project Lead

Financial report for Q3 / 2025

Thu, 02 Oct 2025 00:00:00 GMT

Watch on YouTube

Background

Tuomas Airaksinen Consulting, company of the lead developer, provides a way to sponsor AndBible development. You can support the ongoing development of AndBible financially via the webshop.

See also: financial report for Q4/2023, Q1/2024, Q2/2024, Q3/2024, Q4/2024, Q1/2025 and Q2/2025.

Sponsorship Flow

Sponsorship Flow - Feature #3330 (Separate shared verses with newline characters for better readability)

Month	Orders	Revenue	Hours Spent	Rate	Cost	To Generic
July	0	0.00 €	0.00 h	-	0.00 €	-
August	1	70.00 €	2.72 h	70.00 €/h	190.17 €	1.72 h
September	0	0.00 €	0.00 h	-	0.00 €	-

Sponsorship Flow - Feature #189 (Import / Export bookmarks), see video & blog post!

Month	Orders	Revenue	Hours Spent	Rate	Cost	To Generic
July	2	420.00 €	6.02 h	70.00 €/h	421.17 €	0.02 h
August	0	0.00 €	0.00 h	-	0.00 €	-
September	0	0.00 €	0.00 h	-	0.00 €	-

Column Explanations:

Month: Calendar month name
Orders: Count of sponsorship orders for this feature
Revenue: Total sponsorship money received
Hours Spent: Total hours worked on this feature
Rate: Average hourly rate used
Cost: Actual cost of work done (uses actual hourly rates)
Remaining: Sponsorship balance after paying for work
To Generic: Hours (insufficient payment) or € (completed feature transfer) moved to generic funding

Note: When a feature is completed, remaining sponsorship funds are transferred to generic development (shown as € in 'To Generic' column).

Sponsorship Flow - Generic Development

Month	Orders	Revenue	From Features	Available	Hours Spent	Rate	Cost	Remaining	Free Work
Leftover from Previous Period	-	1061.71 €	-	-	-	-	-	1061.71 €	-
July	6	174.52 €	-1.00 €	1235.23 €	21.82 h	60.00 €/h	1309.00 €	0.00 €	73.77 €
August	5	344.20 €	-103.00 €	241.20 €	9.32 h	60.00 €/h	559.00 €	0.00 €	317.80 €
September	3	444.00 €	0.00 €	444.00 €	8.28 h	60.00 €/h	497.00 €	0.00 €	53.00 €

Column Explanations:

Month: Calendar month name
Orders: Count of generic development orders
Revenue: Total generic development funding received
From Features: Net funding flow from features (positive: transfers from completed features, negative: feature overflow costs)
Available: Total funding available after feature flows
Hours Spent: Total hours worked on generic development
Rate: Average hourly rate used for generic work
Cost: Actual cost of generic work done
Remaining: Generic funding balance after paying for generic work
Free Work: Generic work not covered by available funding

Note: the new reporting system is lacking data from 2024. Please see data in previous financial report (Q1/2025) if you want to compare.

Time Tracking Summary

AndBible development is much more than just writing code implementing new features. Below is a description of how my time is distributed across different tasks:

By Category

Category	Total Hours	Tasks
Generic	39.42 h	ab maintenance (ID=11), ab support (ID=10)
Feature	8.73 h	ab 3330 shared verses readability (ID=28), ab 189 export bmarks (ID=26)

By Task

Task	Hours	Category	Ticket
ab 189 export bmarks (ID=26)	6.02 h	Feature	#189
ab 3330 shared verses readability (ID=28)	2.72 h	Feature	#3330
ab maintenance (ID=11)	34.48 h	Generic	N/A
ab support (ID=10)	4.93 h	Generic	N/A

Final observations

👍New cool features that sponsorship has enabled me to do during the quartal: Import / Export bookmarks (CSV).
👍Also a lot of essential maintenance work during the period.
👎Support has dropped in this quartal to some extent (~40 % less than in Q2 or Q1).

Closing words

Best regards & blessings,
Tuomas Airaksinen
Lead developer of AndBible Open Source Project

New feature: Export & Import Bookmarks as CSV

Thu, 21 Aug 2025 00:00:00 GMT

In this video I will introduce you to the new feature that was recently developed: Export & Import Bookmarks as CSV.

Watch on YouTube