Sponsoring a Feature

How long does it take to implement a feature?

It depends on the feature. Some take less than an hour, others can take weeks. To give you an idea, here are a few past examples:

1. MyBible initial support: 1–2 days
2. MySword support: 3 hours (built on top of MyBible support)
3. Initial, fully working EPUB support: 1–2 days
4. Optimized EPUB support: 1–2 additional days
5. Bookmarking for Generic Books: 1 week
6. Improved TTS for Generic Books: 1–2 days
7. “No highlighting” bookmark style: 30 minutes

These estimates are from before AI-assisted development. Today, AI tools can speed up the process by up to 5x, so many features may take significantly less time than listed above.

What if the estimate does not match the actual time?

I estimate the time needed before starting. If the actual development takes less time than estimated, I will offer you the chance to suggest other improvements or features to use the remaining hours for. Any time not used this way goes to the non-earmarked development pool. If it takes more than estimated, the extra work is covered from non-earmarked time — or done at no charge if none is available.

Earmarked features are prioritized over non-earmarked work, unless there are critical bugs or urgent production issues.

What if a sponsored feature cannot be implemented?

If I cannot implement a feature you have paid for, I will offer a full refund.

What kind of features can be sponsored?

Not everything fits AndBible. I evaluate each idea before making an offer.

The primary channel for feature requests is GitHub Issues. There is already a large collection of requests there, and many popular ones already have time estimates. I provide estimates for others on request.

You can also suggest ideas by email at tuomas+andbible@sykero.fi or via the Contact page.

Pricing & How to Sponsor

See the sponsoring info page.