if a company makes a smart watch that isn't android wear, but wants to use Wear's functionality.. Can this be done on the back end?
Say for instance Pebble wants to make a fork of Wear and customize it so that it make sense for their new color devices. How much could they use?
Also if they go ground up, how much of the Wear API is exposed to non-wear devices?
Would they be able to use the Wear app? If not, do you guys think that it should be able to?
I can tell you that Android Wear (both the OS, and the app) are not open source, even to the extent that traditional Android still is. So "make a fork of Wear" doesn't really make a lot of sense.
The APIs are, of course, public. So you could, of course, build an interface that duplicated those APIs, but worked with a non-Wear device (like Pebble). But as a wise old programmer once told me, "Anything's possible. Many things are difficult."
And I expect it would be possible to build a level of compatibility that even the Android Wear app would be fooled, and would work with this device. This strikes me as more dicey... IANAL, but reverse-engineering APIs has gotten some into hot water before.
I suspect the real-world answer is effectively no. It might be reasonable to build some amount of compatibility, so as to ease the burden of devs who already support Wear. But as for actually duplicating it, probably not.