What is this about?

With years of the MyBible project existence a number of active users have joined efforts of producing modules they need, to add them to the MyBible modules arsenal. However, once such a labourer has produced some version of a module, a question arises: how to conveniently distribute it among the potentially growing audience, if it is not ready for, or cannot at all be placed to, the main MyBible module repository?

Yes, MyBible automatically picks up a module if it is placed to the MyBible data directory on the device. However, this is not a one-tap action, especially since Android 11 (it limits apps to their private data directories, located rather deep in the file system).

Besides, modules tend to have defects which are being iteratively corrected, as defects are found and reported.

Also, there are ongoing Bible translation efforts out there, with frequent updates wanted by eager users.

So, new module versions periodically appear as the result, and a periodic update of modules on the end users’ devices, requiring a not-straight-forward manual procedure, quickly becomes an irritating burden, distracting from the main goal of MyBible – deep studying of the Word of God, the Bible.

What’s a solution?

The MyBible core team, Denys and Oleg, who maintain the main MyBible module repository, decided that it is time to equip MyBible module creators outside of the MyBible core team for feeding of their audience conveniently. So starting MyBible 5.5.0, the app supports entities called “extra module registries”.

Here is how it works (see also the usage tips in the MyBible Modules window):

So what do I do?

If you create and update MyBible modules:

If you want to use MyBible modules being produced by someone not from the MyBible core team, then:

  1. get in touch with the module producer, obtain from them a URL for downloading their extra module registry file
  2. in MyBible:
    1. open the Modules window
    2. select the “Extra module registries” menu item
    3. observe, think and use the obtained URL – you will figure it out
    4. consider enabling automatic module updates in MyBible settings