I am observing a troubling pattern with Logos. But first - let's define our terms:
______________________________________________________________________________________
Pre-alpha
Pre-alpha refers to all activities performed during the software project prior to testing. These activities can include requirements analysis, software design, software development and unit testing.
In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the functionality is complete.
Alpha
The alpha phase of the release life cycle is the first phase to begin software testing. In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release.
Alpha software can be unstable and could cause crashes or data loss.
The exception to this is when the alpha is available publicly (such as a
pre-order bonus), in which developers normally push for stability so
that their testers can test properly. External availability of alpha
software is uncommon in proprietary software. However, open source software, in particular, often have publicly available alpha versions, often distributed as the raw source code of the software.
The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete.
Beta
Beta (named after the second letter of the Greek alphabet) is the
software development phase following alpha. It generally begins when the
software is feature complete. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it.
Some software is kept in perpetual beta — where new features and functionality is continually added to the software without establishing a firm "final" release.
____________________________________________________________________________________________
The trouble I am observing is Logos perpetually throwing a solution together without real consideration for design and usability. What they call beta, should be called Alpha or pre-alpha. Let's call a spade a spade, shall we?
Another big problem I am having is spending so much time to "beta-test" even things that are supposed to be working by now: basic PB features for Foreign languages, typos in resources, Vyrso website cart, downloading resources for offline use in Android, etc., etc. I will give Logos credit where credit is due, for the most part issues were acknowledged and fixed quickly.
Although Logos claims that they provide "free" software, their perpetual-beta cycle is too costly for me in terms of my time.The truth is, their "engine" does cost money to the customer (via more expensive resources) and as such, please design it with the end users in mind. One size doesn't fit all, so create options for users with different needs (highlights in a hidden file, highlights in last notefile, etc.) and not in Beta 5 but since the very beginning. There is absolutely no reason for rushing a feature that receives a huge outcry on the forums.
and hire a designer.