Bug fixes need to be decoupled from major version updates. There should be constant iterative bug fixes and less frequent major releases. This should apply to app and firmwares. These are the minor point release updates like App version 3.18.1 to 3.18.2 and firmware version 3.13.0 to 3.13.3. These would be “hot fix” releases and should be streamlined through the internal testing processes as there shouldn’t be any sweeping code changes, only targeted and specific bug fixes that are being addressed.
I think Yarbo should introduce a public beta test program. This program would be optional for all users to opt into if they choose to. This would be for the major update releases and would not replace the closed beta testing (PPP tests). This would be the next step after PPP testing has completed. Software updates would still be announced publicly like they are now and at that time the users who want the newest features could choose whether or not they want to participate in the public beta for it or wait until it’s available in general release.
For implementation, this should be something as simple as the way that Apple does it. That is to add a toggle under a new “software updates” section in settings. In this section would be “Check for update”, “Automatic Updates” toggle, and if automatic updates is enabled, a schedule for a day and time to check and apply them. This should be daily, weekly, monthly and let you pick a specific day of the week/month and time. Finally, a public beta toggle to enable and disable participation.
A user could choose to toggle on the public beta if they want it and toggle it off if they don’t. Rolling updates wouldn’t be needed then IMHO. Those users who want the latest and greatest features, can have it immediately and opt in to deal with any known and unknown issues. They would leverage the same standard support process for any issues, with the option for support to roll them back to current public release to solve their immediate issues. Ideally, the user could choose to roll themselves back to the production release, but support being able to do it would be a good compromise for now.
After 2 weeks of a public beta without big issues, ship it to all. Those who have automatic updates enabled (this should be a toggle), it will auto install at the time and day specified by the end user. No unpredictable updates time/day. Otherwise it will inform the user there is an update available when they open the app and they can choose whether or not to install it. If they say no, they should be able to go back into the app and check for updates and install at any time. Users should not have to wait for the next update or contact support to get firmware updates.
Additionally, the app needs to be fully backwards compatible through a couple of firmware versions. App functionality shouldn’t be dependent on having the latest firmware.
If you agree with this approach, please click VOTE at the top of this thread and feel free to drop comments, suggestions, etc.
