While I don’t disagree with this, in concept… Android actually doesn’t change that much outside of major revisions, which at best come out annually. While there are hurdles to programming across android and IOS, this is actually significantly easier if you don’t keep 2 code bases and instead use a platform agnostic language/framework, like flutter for instance. However, Android programming in terms of properly working with background tasks I don’t think has really changed much since Wyze has been in business… Let alone since they added this watch to their lineup.
Even so, Google offers fairly flexible compatibility abstraction, that if used properly, can prevent the need for major software changes for multiple versions. Even things like keeping an entire app running in the background, rather than creating a service with the limited functionality that you actually need in the background, hasn’t really been “proper” coding on Android for a while now. Android added the “background task” notification of shame when developers keep the functionality in the main app rather than using something more sensible like WorkRequest. The notification goes ahead and lets you know that an app is basically ignoring any battery saving features that Android provides as well as batching of notifications/data syncing. To me, this either means that they rushed it out the door or just don’t know better.
Given that I still get crashes on a rule that I made in their app when it tries to pull the rule from the server for the past few months (probably got stored malformed), I’m going to assume that it’s more of the latter.
I will say that I’ll give them some leeway as it looks as though Wyze created their own firmware for the watch (rather than doing something crazy like adopting Wear OS, which would’ve locked then mostly to Android device) which makes things even more difficult for them. Now they have to create the entire framework between the app and device. While I was excited to get this smart watch, it’s a bit of a sad state when (from pictures in this thread) the smart watch is less functional than their fitness tracker.
I feel like they would’ve been better off holding off a couple extra months before shipping the pre-orders to finish more of what is considered “basic” smart watch functionality these days. There are some things that can be expected based on the hardware that was advertised… No lux sensor for auto brightness (though this field l could be worked around with time based rules from the app to change brightness), no proximity sensor, no microphone, no speaker, no local storage. Fair enough, this was all expected.
However, they needed more time for the software. For instance, take this “concept photo” that I literally just snapped a screenshot from the Wyze watch page…
Where’s that notification at? I don’t have anything on my watch even remotely resembling that for emails.
I think it really shot them in the foot to release this watch as is. I personally can’t recommend it to anyone as it currently is. Maybe I’m another 6 months to year of software updates, it will get where it’s a decent smart watch… But, that’s definitely not where it is today.