![]() ![]() ![]() Go for HTML 5, with HTML 4 graceful degradation.Reach is paramount, and development budget does not allow 3 individual versions.Need to support Android, iPhone, Windows Phone 7 and iPad.Intranet Application where Reach is important on new devices HTML4 (degrade for unsupported browsers - lose rich retain reach).Does HTML5 even have multi-touch, GPS or camera support? Do I have to code gesture-recognition in JavaScript? We're talking about rich interfaces here, may be in another 2 years when tools are better at faking it. HTML5 (reach) - I wanted to recommend HTML5, but really, the more I think about this, do I really want to use a web app on my WP7 or iPhone? Really? That would be pretty silly.Microsoft-Corporate environment / Business Apps: The conclusion I came to is not pretty for HTML 5: I wonder about the whole "HTML5 standards" - the IT industry is littered with corpses of different vendors coming together to put together different implementation of the same specĪt the very end - you can't trust ANY implementation - you end up relying on a framework to smooth out the differences and give you the lowest common denominator: Silverlight - great, easy to deploy, installation independent of IE version.Flash - so so, but in a MS environment lack skillset to develop Flash/Flex.HTML5 - only for latest/future mobile devices.Silverlight - bad - Windows Mobile, Symbian (support woeful).Silverlight - less reach than Flash, works on most Windows and Mac, no mobile.Let's consider the scenarios to build applications: So, 2014 or 2017 to be able to use HTML5 for less features than Silverlight 2.Except old devices will never work: old iPhone, blackberry, windowsphone 6.5.Newest Mobile devices should move quicker.Based on current corporate adoption rates - let's add another 5 years to upgrade to IE9 (or later).MS tools and JavaScript frameworks (JQuery-Mobile) should be ready pretty quickly. ![]() Say, it will take HTML5 another 2 years for the standard to mature.Technology-wise, I think HTML5 is still a few years behind Silverlight. I would love to see HTML5 be successful, but people who only think Silverlight is about video or the canvas element is really missing the mark. This makes Silverlight still the best choice for the next decade, even before you consider the possibilities for hosted online services (SharePoint, Exchange or CRM), or Windows Phone 7. While HTML5 is great for the mobile devices, I don't see corporate upgrading to the latest browsers for another 5 or more years (so many are still on IE6/XP). There's this big fruity company in the way. Sure, some "might" have hoped we'd see Silverlight on the iPhone one day - but let's be serious I really doubt that day would ever come. We started using it for intranet and even Internet business applications (as long as you only support Windows and Mac - it works just fine). Ever since Silverlight 2 was available we have had great tools, support for connecting to services and hundreds of controls for building business applications. Silverlight evolved quickly, because the community responded and Microsoft heard what we're asking: business apps. Yes Silverlight 1 was rushed out the door because we don't really want to learn Flash, the Olympics was happening, Microsoft saw an opportunity and pushed it - while the rest of the world was going Flash because of Video and YouTube. Most of us that have been actively working with Silverlight has never had the misconception that Silverlight was about reach. ![]() HTML 5 - well I don't think this will ever be suitable for Business Apps. Silverlight has always been about Business Apps since version 2. ![]()
0 Comments
Leave a Reply. |