I actually like the idea of having an smart watch, but the problem I see with the technology is the battery time, I don't really want to be charging my watch every 8 hours, I don't want to charge it at home, and at work. The more you can do with the watch the less it's battery will last.
Thanks for the read, it really makes me think. He only wants to use it because is C#, he doesn't know anything about mobile development, in the end I guess the debate will be between cross platform vendors and native apps
so if you love C# and know how Objective-C works, this is a great framework, lame I'm not truly a fan of C#.. So i guess it won't be a time saver for me.
I know, the thing is that my boss is a fan of .net and all of those technologies, and I'm not, even when I'm the one that will develop the apps, I know that saying that I don't like the language is a good reason to not use it, so I'm looking for cons and pros so that can make him or me change our minds
I see that most of the limitations are about dynamic code generation, but it's on general because of the iphone?, so trying to do a java-objective c in these cases won't work?
I like the model, except the part where you charge the developers, if you charge 50$ to developers it means developers will charge on their apps, means that users will have to pay even more