There have been some significant app revisions in the last week, but there are still serious problems.
I tried to clear old videos a couple of days ago. I have four different devices installed and recording, and on one of those I was unable to delete recordings.
On our “Flood Light Camera” I tried multiple times on two different days before I was able to delete “all recordings” Not sure if this is related to this specific camera or not. One of the clues that ring had been led astray is that the “spinner” started and never stopped on all attempts to delete.
As an example, the “camera history” has a completely different interface from that of the individual camera recordings. Tap the “3dot” menu, sometimes you get a menu, but most of the time you get sent to the recording. <tap/hold> and you get “check circles” as opposed to <check boxes> …but, they can only be selected one by one, …and as a special treat, scroll down and the check circles (and your previous selections) disappear.
In addition to different interface options for each camera type as well as yet another interface on the “all events” button, there’s no documentation for users for this (and many other sections of the app)
Sometimes icons appear on the screen, but, in the ring app, unlike other apps, <press/hold> does not tell the user what the icon is notifying. (no ring icons do this other than the “invite friends” icon… (that would tend to indicate that the ring sales department is in control of the app)
For example, there is no hint or clue that to delete, one has to swipe left to right to expose the checkboxes and “delete all” If you check _one_ box, the “delete all” changes to “deselect all” …so, if you have a large number of recordings and want to save several, the _only_ option is to manually check the boxes for every one you want to delete and not check the boxes of the ones you want to save.
It would make far more sense to change “delete all” to “select all” then the user could deselect the ones they want to save and press the trash can icon.
There’s also no way to reliably (or easily) to go to the event viewer. Press the “3dot” menu to the upper left of the camera image and sometimes you go to a 3 to 5 option menu at the bottom of the screen, select “settings” then select “event viewer” BUT most of the time when you press the “3dot” menu you go to the camera’s view screen, then you have to press the settings gear at the top right of the screen, etc.
The above selection errors point to the probability that whomever created the touch zone, did it completely wrong.
There’s zero information on the screen to tell you that the alert that just notified the user of motion is not available to view and my not be available for five or more minutes… gotta get up, go to the door, walk to the gate and look for yourself.
If you press <Back> on the the vertical view screens or the camera page, you exit the entire app.
Again, from the users’ viewpoint, when you select view, it appears totally random if you will be sent to the vertical view screen or the horizontal full screen.
Then the user has no way of knowing if the user is in “live view” or a recorded event.
Some full screens have a date time stamp, other viewings such as pressing the right arrow of the events screen show the same screen with no date time stamp… could be that it’s a live view, no way for the users to know.
This morning, from the vertical view screen, when “live view” pressing “full screen” takes you to full screen. From the same vertical view screen, when viewing a recorded event, pressing full screen starts to load the full screen, then the app exits to the camera menu.
All of the above anomolies have been tested multiple times.
All of the above are inconsistant at times.
The ring app is up to date and has been uninstalled and re-installed several times on a Moto G6 with over 11gb free storage
I know this is a “lowly user” forum, but I post the above with the hope that someone from ring who can pass it on… will… not that I expect that any action will be taken.
Again, from a programmer’s viewpoint, it seems obvious that no one responsible for the design or programming of the app actually uses the app… if they did, I would assume that major errors and problems such as the above would be noticed and addressed.