> Tylermon Actually I disagree with you but there is no need to debate the issue.
Then add to the discussion. You literally have a thread driven for debate and discussion on the topic. Picking and choosing which views to refute or rather dismiss hardly helps people make a decent decision on Html5 being or not being the right tool for their needs. It is possible I am not aware of some aspect of html5 that you are, or perhaps I know something about html5 that you didnt. I only ask you share your opinions because everyone can benefit and then form their own.
---------Back on the topic of Html5 vs Native----------
One is more than welcome to develop IOS apps in xcode, and then rewrite the same app for android, and write it again for windows. But most developers don't have that amount of time.
Html5 has a huge advantage of being written once and working on every device. For near native app performance simply use a wrapper and make a hybrid app platform specific.
Is Html5 perfect for every situation? Absolutely not. When you cross a line into needing high security and high performance. Native code is your best option...at least for now. And some platform specific features are not available from html5 based apps(yet).
But if getting to a market quickly and cost effectively for near native-like performance is what one desires. Html5+wrapper of choice is perfect.
I do have to say however, if one intends only to publish to lets say the apple store. One market, on only a handful of devices they should be making native apps.
And on the topic of fragmenting.
Html5 does have it pretty hard here. There are many browsers to consider, and each offer more or less functionality than the other. This is often a challenge with Mobile web apps. However, wrappers help negate some of those issues.
That does not go without saying that native apps don't have to worry about fragmentation. Just think of how many IOS versions are out there. Each version needing to be maintained. This goes for android and windows as well.
I still have to say fragmenting and these browser and device differences is the hardest part about Html5 development.
In the end it really comes down to personal needs. I wouldn't say "HTML5 is NOT [the] right tool to make mobile games". I might say 'Html5 is NOT the BEST tool to make mobile games' But I would say 'Html5 IS the BEST tool to make cross platform games'.
I'm sorry, name of this title is limited by characters, I would have written as "HTML5 is NOT the right tool to make complex mobile games" and got an error due to character limit on this forum, then I had no choice and I left this name as simple of this current thread title.
Yes, we know HTML5 does like write once and run anywhere IF some browsers support, it's much like Java vm.
You was right about native, isn't designed for cross-platfrom that we have to write objective-c for iOS devices, then rewrite Java for android and rewrite C# for windows phone, it's big waste of time. That's why HTML5 is best option for cross platform but it has the worst enemy is performance.
The experience about Facebook tried to create own mobile app using HTML5 and they noticed it was terrible mistake due to lack of features, no information about performance but they mentioned about quality, then they decided to write own native app for each platform such as android and ios.
However, I believe the future of HTML5, the problem is we have to wait longer than we expected.
You know why a lot of C2 users post here about mobile performance... frequently
I'm trying to tell simple games would work for mobile devices, otherwise complex game is risky and not ideal.