I think that Samsung and Google are doing it all wrong.
They are still making smartwatches be "companion devices" to smartphones, yet you still have to write custom code to run on the device.
I think that the best type of smartwatch would be one that would act as a dumb terminal to the phone. Let it act as a second screen to the phone with a few button/touch actions plus a few sensors that feed data in the other direction. That would satisfy the most common use cases where a smartwatch would be useful. The others could be hard-coded not as apps but as system features.
This would be best for the developer, as you would only have to develop one app - not two.
This would be best for the user, as the program code on the "watch" could be simple you would need only a microcontroller that runs at tens of megahertz, and you get long battery life approaching what you are used to get in a watch.
But of course, such a device would be too cheap to make and Samsung would not be able to sell it at a premium...