Only a month ago, I received an S2 as a replacement for the S0 that I broke, and I'm tempted by the S3. It would do the job when I'm out and don't need all the capabilities of my phone -- all I'd need is to be able to be called or texted.
But, because Apple also gave me two years of AC+, I can wait it out and see what S4 and watchOS 5 bring.
If I still had my S0, though, I'd put my name down for a steel or ceramic S3.
[doublepost=1506432928][/doublepost]
Thanks guys. I am overall happy with my Series 2, but there is lag present at times that gets annoying.
Since you mention lag, this is a question I've got for current S3 owners: Does it have less lag when it needs to grab data from the phone/network? The S2's UI has been slick enough to satisfy me, and I recognize that it's at its slowest when it loads data from elsewhere (sometimes depending on the app's server).
My problem is I literally have my phone with me almost everywhere. I am trying to think of instances on where I would use the LTE. Maybe if nothing else to turn bluetooth off of my phone and conserve the battery?
Experiment by making your phone difficult to reach -- put it in your backpack or gym sack -- and trust the watch to do its job.
That'd be like when I started putting my phone in my pack as I walked to and from work. I learned how much the watch could do "by itself"; even though the phone carried the data, the watch was my sole interface. When I saw for myself how easy it was to send texts and whatnot, even on watchOS 1 and 2, I was much more confident in the watch's ability to act as a first-line communication gadget.