I’m really enjoying the new app. I personally love the auto stream on the favorites page. Instead of removing that, it would be nice to have a toggle setting for auto stream on/off so the functionality isn’t entirely lost.
4 Likes
Why can’t they give us true dark mode?! This is ridiculous because when I go to the about page I can’t even make out the app version number because the green/blue numbers are hard to make out with the white background. They should have at least black numbers and much larger. to see them. But right now because the background is white it’s just blinding at night.
5 Likes
I dig. I can’t speak to that directly with respect to the new app version, though. What you’re describing seems like the v2.5x behavior of groups, so I get that. Reading @Seapup’s posts here and in other Forum topics seems to indicate a new paradigm for the Devices tab, which he likens to maintenance area in contrast with the Favorites being more of a “dashboard”.
1 Like
Auto-streaming favorites might be useful for someone with a small number of devices, but I have 30-40 devices on multiple properties. I need to jump around and none of the are “favorites”. A toggle switch to turn off the entire Favorites Tab would be nice for me.
2 Likes
Agree 100% - People want readability and functionality, not flashiness.
Change for the sake of change is never good. Fix what’s broken and leave what works.
3 Likes
One more issue I’m having with this new app update, often the delete button doesn’t work on recorded events. Then I have to shut the app down and open it up again to get it to work.
This has been a problem for a long time. I was hoping they could easily fix this issue in this new app. Why not?
1 Like
After fumbling around with WYZE app 3.0 today… I can’t any longer.
I’m not buying another Wyze product unless there are major changes to this app to make it more usable.
The Old app was pretty good. With this new one, Wyze took 3 steps backwards.
I also cannot, in good conscious, recommend wyze to anyone anymore. (I’ve done this a lot and I know it has resulted in purchases).
WISE UP WYZE and listen to your customers.
8 Likes
Where did the power button go. The new app sucks for turning cameras off and one so im not getting alerts
1 Like
It’s still hidden in the “More” section of the individual camera.
They’re probably referring to a battery-powered cam’s on/off button on the 2.x Home tab, missing for battery-powered cams on the 3.0 Favorites tab.
1 Like
1 Like
Waiting on the Android version. I kind of like the new app. There’s a few things I would change, but I find it to be better than the original versions.
I agree I would like to choose what tab to start the app with.
I just put my groups in the favorites with nothing else the cameras don’t load up good in the favorites tab
2 Likes
It’s because Wyze programmers are using their own code instead of using native code for android and apple devices. And because they have done this from the start, it will take quite some time to redo the app in the fashion they are trying to do it. Personally I think a version 3 app like this with such a huge change in features should have been left to a time when bugs were already addressed or, to when they finally start from the ground up using native features.
1 Like
Sort of. It kind of depends on what you mean by the “native code.” Technically speaking, their native code is as follows:
Android Native Code:
- Java: The traditional language for Android development.
- Kotlin: A modern, more concise alternative to Java, officially supported by Google.
- Android SDK: The Software Development Kit that provides the tools and libraries necessary to develop Android apps.
iOS Native Code:
- Swift: The preferred language for iOS development, known for its performance and safety features.
- Objective-C: An older language still used in some legacy iOS applications.
- iOS SDK: The Software Development Kit that provides the tools and libraries necessary to develop iOS apps.
However, you CAN do app programming in a number of programming languages and not have a problem:
Cross-Platform:
- React Native (JavaScript): Allows you to build apps for both iOS and Android using a single codebase.
- Flutter (Dart): Another cross-platform framework that enables you to create natively compiled applications for mobile from a single codebase.
- Xamarin (C#): Uses .NET and C# to build apps for both iOS and Android.
Other Options:
- Python: Can be used with frameworks like Kivy for mobile app development.
- C++: Sometimes used for performance-critical parts of mobile apps.
The problem with Darkmode isn’t actually related to the KIND of code or programming language they use(d) being the same as Android or iOS. It is more about the way the app was organized (the framework) from the start that isn’t conducive to modern things like app-wide styles and themes. The app was structured to be segmented into different “plugins” per device and screen, etc (basically each part acts like it’s a separate app within an app). So we can’t just simply change the color scheme on one thing and have it update for the whole app.
They’re trying to retrofit that, but it’s complicated. The Wyze app appears to have originally hardcoded colors and styles for each individual object in the app instead of setting up the structure and framing for Dynamic Theming. If that is what you meant by code, then that is correct. That is problem. The organization and framework has to be redone and reoganized into groups and subgroups that can then be told to get their coloring and styling and such from a single-source that has that coloring information for each different object group. Right now, each object has it’s own manually hardcoded coloring. It’s extremely time consuming to retrofit code like that. I know because I actually did some of this when I was working through getting a certification for Java years ago. It sucks. It can be hard to find, decipher, change and reorganize/restructure into a new framework, test it out. It’s a bigger pain than I think people realize to retrofit old code to an entirely new framework, especially when the old code was done by a different programmer.
Don’t get me wrong, they definitely need to get through it, and I personally think they should’ve prioritized Dark Mode before starting a NEW project. But, I kind of wonder if whoever they assigned this task to, just told them; “Look, it’s going to take me just as long to manually go through all the code on this annoying plugin section as it would take me to just rebuild this Home screen segment. Why not let me make other updates to this section while I’m having to break down all this code anyway. It probably won’t even add a whole lot more time.” I wouldn’t be shocked to hear that this is exactly what happened and they’ll now move on to the next subsection in their list to update more of the app to the new theming framework.
Ultimately the main issue is the segmentation and hardcoding from the beginning of the app until now. It wasn’t designed with a framework that would support theming, etc. and now they’re trying to retrofit it to support that. It’s a pain, but it’s been one of the highest demand changes we users have been begging for, so they finally gave in. 
Hopefully they’ll get back to converting more of it to dark theme.
2 Likes
I get it that maybe some people might want to see multiple live camera feeds on a tablet, I really don’t want this on a phone, especially on my small iPhone 13 Mini, so give us an option to turn it off. It’s also slow to load the feeds and if you tap it before it loads, it gets stuck loading on the next screen.
The app is getting less and less intuitive, the screen real estate is too crowded. It’s just way too much and should be simple, easy to see and navigate. Less is more.
But really wish they would have waited to release it because they must have gotten feedback from the beta testers, so they had to know so many would not like things and would have issues. Spend the extra time to make it what your customers wanted first.
And are they ever going to make event labels to only review what triggered the motion event? Today I had probably 50 vehicle events for a parked car, because the wind kicked up and the camera was seeing the branches move and people were walking in the background (but it didn’t label them). I don’t care about parked vehicles, so I don’t review them right away and would easily miss say a person breaking into a vehicle. It would be much better if it only labeled what moved and not everything in the frame.
5 Likes
I AM YI… the Great and Powerful! Who are you?
Yet there are things that daunt me. Like this:
I’m almost - dare I say it - human?
( Y + long-I : YI ! (aka AI))
(Apologies, couldn’t let this pass, no response required or expected, it’s just a simple snipe.)
Ⓒ Panacea Unproductives
I’m having this same issue again where I get a notification but don’t tap on it, instead I open the app directly and it goes right to the motion event recording. I had this issue earlier this year, which is something the app never used to do. I do understand however, that if I tap the notification it will go right to the event recording and in that case it makes sense. But being forced to watch a recorded event that I don’t want to watch yet shouldn’t happen when the app is opened directly and not through the notification.
1 Like