Html5 – Not Designed For Business Applications

HTML5 – Not Designed for Business Applications

HTML5 is the next version of HTML to come along since version 4.0 in 1997.

HTML is an acronym for Hyper Text Markup Language and HTML elements are the basic building-blocks of web pages. The Internet would not exist as we know it today without HTML.

But HTML is not a programming language at all. This concept is confusing to some people. Web pages rely on a scripting language such as JavaScript in order to respond to user input. Think of it as HTML being a car and JavaScript being the engine.

JavaScript was introduced in 1995 by Netscape and coincidentally, that’s when the web started to really “take off”. This is an important fact to consider before we dig deeper into HTML5.

The open source nature of HTML and JavaScript has contributed to the growth of the Internet as a whole. Source code and design ideas are often borrowed from around the web and even from competitor’s web sites. This is facilitated by the fact that HTML and JavaScript are impossible to hide or protect.

HTML5 is no different!

There has been a lot of talk about HTML5 over the past couple of years and developers think that HTML5 is “cool” and “fun” to work with. But the logic ends there.

As usual with most new technologies, there has been confusion and misinformation over when HTML5 should be used and for what purpose. We aim to enlighten you about what HTML5 can and can’t do in this article.

New Features Same Old Concept

HTML5 includes new features such as the “Canvas” element, along with audio, video and Scalable Vector Graphics (SVG) content, some of which replace the “object” tags of HTML4. There have also been some modifications and standardization of tags such as (a, cite, menu) but the basic concept of HTML remains the same in HTML5.

Who’s Promoting HTML5?

HTML5 was originally proposed by Opera Software (makers of the Opera web browser) and designed by the World Wide Web Consortium, also known as W3C.

An important point is that the W3C has been criticized as being dominated by larger organizations and thus writing standards that represent their interests.

The large organizations (Apple, Microsoft, Adobe, Google and Facebook) have promoted HTML5 as the most up to date technology for web development. In fact the late Steve Jobs termed HTML5 as the win-win solution for consuming any kind of web content on all types of web platforms. But it is important to note that Apple, Microsoft, Google and Facebook each have an incentive for promoting HTML5; each own and operate very profitable “app” stores such as the Windows Marketplace, Google App Store, iTunes App Store, Facebook Canvas Apps, etc. Protection of intellectual property and trade secrets is of little or no concern to those companies and in fact it is almost a conflict of interest.

Fact #1: HTML5 is based on JavaScript, which is impossible to protect. Yes, that’s a fact!

As we discussed a moment ago, JavaScript is the core “language” of HTML5, whose source code is impossible to protect. The most evident reason is that anyone can view HTML5 and JavaScript source by just a simple click. JavaScript was never intended to be anything more than an engine for client-server communication and re-useable web content, including menus, buttons, tabs and the like.

Developers may argue that they can mangle JavaScript source code by obfuscation and pseudo-encryption (such as “minification”, where the code is compressed and “minified”). But this is a dangerously false sense of security. Any skilled developer can reverse engineer a “minified” or “obfuscated” JavaScript application. By design, JavaScript cannot be encrypted and it cannot be hidden. JavaScript files must be downloaded in order to run in a web browser.

To make matters worse, JavaScript also cannot be locked down to a specific web domain.

The code is accessible to be hacked by any competitor. No matter how many steps are taken to hide the JavaScript, the web browser eventually downloads the JavaScript file to run it within the client’s web browser.

For comparison, hacking a Flash or Silverlight application just by viewing the source is not very easy but anyone with a little knowledge of HTML5 can do it in minutes.

The hacks of famous HTML5 games like AngryBirds, Texas Holdem and many others are excellent examples of the insecure techniques employed by HTML5 developers. All security measures are useless once the code has been obtained and reverse engineered. No matter what any HTML5 or JavaScript developer may claim, these facts are true and irrefutable!

Fact #2: The concept of HTML5 Canvas is nothing new.

As we discussed already, HTML5 is based on the same concepts of HTML4. The most useful and talked about feature of HTML5 is the new “Canvas” object. Canvas makes it easy for JavaScript developers to “paint” within a web browser, simplifying the design of applications that utilize graphics. But you may be surprised to know that this functionality has been available in a simulated manner with very little attention since the release of HTML4.

Fact #3: There is a widespread misconception about HTML5

HTML5 has been labeled as a “cross platform programming language” which is a serious misconception. It is true that HTML5 is capable of running on all types of platforms such as Windows, Linux, Android and other mobile operating systems but let’s not forget that HTML5 is nothing more than web page markup, which is controlled by JavaScript. Classifying HTML5 and JavaScript as a true programming language would be incorrect. It is a browser integrated language that cannot utilize all the features of the underlying operating system.

When Should You Use HTML5?

The answer is quite simple. Use HTML5 when you do not care about your source code, intellectual property, or trade secrets. If you do not care that a competitor may steal your source code after it has been uploaded to your web site then use HTML5. As you can see, HTML5 is perfect for buttons, menus and website specific content, for which it was designed.

The Bottom Line – Better Options Available

The bottom line is that HTML5 and JavaScript are great for a lot of things, but you can’t effectively protect anything that you develop with them. This clearly doesn’t add up if you are using these technologies for developing business applications, which they were not designed for.

If you are developing a web application then consider using Flash or Silverlight, both of which run in all popular web browsers for desktop operating system, including Windows, Mac and Linux.

If you are developing a mobile application, there are far better options for iPhone, iPad and Android development that afford better protection of trade secrets, better security, performance and usability for the end user and also allow you to take advantage of the native features of the underlying operating systems. For iOS (iPad and iPhone), use the Object C programming language. For Android, use the Java programming language.

For Windows development, consider C++, C#, Delphi or other proven languages.

Although slightly more difficult to develop with, Objective C, C++, C#, Java and other low level languages are always the best option no matter if you are developing desktop, web, or mobile applications.

Permission to Redistribute

Copyright (c) 2012 by Modulus Financial Engineering, Inc. http://www.modulusfe.com All rights reserved. Permission is hereby granted to redistribute the article providing this copyright notice remains in place.

About the Author

Richard Gardner is Founder/CEO of Modulus Financial Engineering, Inc. In addition to his leadership role of the firms team members, Richard is an influential member of the financial technology industry at large, a globally-respected professional trader and software engineer, a guest speaker at industry conferences and among the inventors on over 70 technology patents.

Get Up And Running With These Web Design Tips

Have you ever seen a website that you were just really impressed with? From layout to graphic design, there are many elements which turn a website from good to great. Here, you will learn some of these tricks. So keep reading and take note of what you read.

If you’re designing a website, make sure the code you write has a valid HTML+CSS. Although most browsers can make sense of code that isn’t valid, it could be rendered correctly or incorrectly. Valid code will render the same way most of the time in modern browsers. You can check the validity of your HTML code with an HTML validator.

On the Internet today, speed is where it’s at. So you must make sure everything on your site loads fast. If your website takes ages to load, they will wash their hands of your site and find one that loads in a reasonable amount of time.

You don’t ever want to use too much graphics. Graphics are indeed important to make your website look well-designed and professional, but if you use too many, it just looks cluttered. Don’t just use graphics to decorate the website; they should be used to make it better. Having the right mix of graphics will improve your site’s usability, too.

Keep the sizes of your files and images small. Excessive loading times are a death knell for any site. The larger the files are that must load, the longer a user’s load time is going to be. Most users will click away if the page doesn’t start to load within the first few seconds of opening your page.

Build your website using a content management system. Knowing how to build a website using just HTML and CSS is good foundation knowledge, but this can only produce a static website. Web design has evolved into providing dynamic content. If you couple your coding skills with the use of a content management system, you can practically build any type of website that you desire.

Add a link where your visitors can send you feedback. You will find out if a link is broken or if a page is not loading properly. If a visitor feel involved, he or she will want to see your website again.

Minimize the amount of clicking or scrolling visitors must do to access information. The more a user has to click or scroll around to find the information they seek, the more likely they are to give up looking for it. Aim for having at least 400 words on every page of your site by combining pages that have content that falls below this number of words.

Make text easy to ready by using colors that contrast or backgrounds that are easy to read text on. When your text is harder to read because the background or text color creates eye strain or portions of text that are unreadable, site visitors are less likely to stick around.

Now you know some great places to begin with web design. Write down what you enjoyed about other sites, and figure out how to incorporate them into your site. Enjoy the process and remember to continue learning.

Html Email Design Best Practices

HTML Emails are arguably the most effective of all email marketing designs. Theyre eye catching, engaging and flexible. They provide you with a variety of opportunities to promote your business and achieve email marketing success. However, there are many pitfalls to be aware of when designing HTML Emails. In this article well highlight some of these and give you a few tips to help you design effective email campaigns.

Back to the old school

Theres no point denying it HTML Email design is Old School web design. This means no Stylesheets, JavaScript or Flash, they just wont work consistently across the wide and varied range of email clients.

When it comes to layout its back to a basic table-based structure, which may, to some web designers seem like committing web standards blasphemy. However, when you take into account the number of email clients that either remove or pay no attention to CSS it becomes quite clear going back to basics is the only way to guarantee your email looks the same regardless of which email client is displaying it.
We have found when designing table based layouts using merged cells (indicated by colspan and rowspan in your code), some email clients, especially Lotus Notes will usually distort any layout with merged cells. Instead, using nested tables will work more consistently than merged cells. For example, a two column layout could consist of a base layer of one table with two columns with other tables inserted into each column to give you space to enter your content.
Looking Good

A great deal of formatting can be done using Inline Styles small snippets of CSS code inserted into either a containing table cell (&#60td&#62), in paragraph tags (&#60p&#62) or span tags (&#60span&#62)

Below is an example of an inline style insert into a table cell tag:

&#60td width=”400″ align=”left” valign=”top” style=”color:#000000; font-family:Arial, Helvetica, sans-serif; font-size:11px;”&#62

This style would then apply to the text contents of that table cell. Other standard HTML formatting tags such as &#60strong&#62, &#60em&#62, &#60font&#62 etc can be used as well to vary the formatting on top of this base style.
When deciding on a font for your email its always best to stick to a font that most, if not all, of your readers will have. Common fonts such as Arial, Verdana, Tahoma, Times New Roman and Georgia should be fine. If youre willing to take the risk of a slightly lesser-known font its good practice to specify a set of backup font faces in your inline style eg.
&#60td style=” Lucida Console, Arial, Helvetica, sans-serif; “&#62

If a computer does not have a certain font it will look to the next in the list to see if it has that one.

Time Warp

When we first got our hands on Microsoft Outlook 2007 we were a bit taken aback with what Microsoft had created, not only locking it down to use only the Word HTML rendering engine (Outlook 2003 will let you choose between normal HTML and Word rendering) but also support for background images had been removed, which meant a real step back with what you can and cant do to keep your emails looking good.

To ensure the most consistent display across the majority of email clients, we took the decision to not include background images in our designs (unless otherwise specified by the customer), and weve come up with a few little tricks along the way to help us keep our designs looking top notch. The main thing to remember is HTML text should only appear on a solid background colour (which you can set in a table cell). There should be no gradients or any other fancy effects behind actual text, unless you plan to include that text in an image.

The final few things…

There are hundreds of elements to take into consideration when designing a HTML email. These are just a few of the most important things to consider:

Create a plain text version of your email to send alongside the HTML version for those who prefer it and for mobile devices and email clients that only accept text only email.
Keep the width of your email between 600-650px to ensure readability for the maximum amount of email clients.
Assign an alt tag to each image so if readers have the images turned off they should see some sort of useful information to assure them the email is legitimate.
Always set height and width attributes on images in your HTML design. Some email clients like Outlook 2003 and 2007 will suppress images in the inbox. Failing to put a height and width will result in your deign be distorted by the security message that is inserted by the email client into the image space.
Use images at the size they are meant to be rather than resizing them with HTML some email clients will ignore the HTML resize and just display the image at its original size.

Whatever you choose to do with your email marketing designs, the most important thing is to test, test and test again. You should always proof your email into the major email clients to ensure its rendering correctly and ask a proof group to check for spellings or design issues too. However, just because there are limitations to HTML email design it doesnt mean you cant be creative or push the boundaries to see what impacts on delivery, open and click through rates. Remember the aim of any email is to achieve your goal and sometimes being safe with your design isnt the best option.

Advantages Of Tableless Websites

HTML was originally designed as a semantic markup language intended for sharing scientific documents and research papers online. However, as the Internet expanded from the academic and research world into the mainstream in the mid 1990s, and became more media oriented, graphic designers sought ways to control the visual appearance of the Web pages presented to end users. To this end, tables and spacers have been used to create and maintain page layout.

Problems then started to arise from the use of these techniques. As many webpages are build with tables nested within tables, this resulted in large HTML documents which use more bandwidth than documents with simpler formatting. With slower performance, the internet slowly begun to decline and the Web development industry shrank. Because of this, several UI development was carried out by coders with greater knowledge of good coding practice. It was around this time that many became critical of messy coding practices and the idea of tableless design began to grow.

Cascading Style Sheets (CSS) were developed to improve the separation between design and content, and move back towards a semantic organization of content on the Web. According to popular Web design outsourcing Philippiness companies, the term “tableless design implies the use of CSS to position HTML elements on the page but it should be noted that tables and CSS are not mutually exclusive. Many experienced HTML coders use CSS to manipulate tables frequently.

Advantages
There are several advantages through the use of tableless websites, these includes:

Accessibility
As a result of the separation of design (CSS) and structure (HTML), it is also possible to provide different layouts for different devices, e.g. handhelds, mobile phones, etc. According to different Web design outsourcing Philippiness companies, it is also possible to specify a different style sheet for print, e.g. to hide or modify the appearance of advertisements or navigation elements that are irrelevant and a nuisance in the printable version of the page.
Maintainability
In tableless layout using CSS, virtually all of the layout information resides in one place: the CSS document. Because the layout information is centralized, these changes can be made quickly and globally by default. The HTML files themselves do not, usually, need to be adjusted when making layout changes. If they do, it is usually to add class-tags to specific markup elements or to change the grouping of various sections with respect to one another.
Bandwidth Efficient
Clever implementation of tableless design can produce web pages with fewer HTML tags thus reducing page download times. According to web design consultants and Web design outsourcing Philippiness companies, using external style sheets to position page elements means more mark up language may be cached and further reduce download times for subsequent pages using the same resources.

Difference Between Web1.0, Web2.0 And Web3.0

After the invention of World Wide Web the idea behind the technology has been absolutely changed. It opens the new way to see the world through internet. It makes our day to day life easier in all around. We can easily operate our business globally. We can join a MNC and able to work from home easily.
Web1.0: In the beginning of web the information published in a static form well designed with the text and images. The main features of web w.1.0 are hyper-linking and bookmarking of the web pages. There are some design elements of web 1.0
HTML based Static page.
It consists of framesets.
Online guestbook.
HTML form sent through email.

The term Web2.0 was first introduced by OReilly during the brainstorming discussion MediaLive International. The information available in this form is quite different from the past web1.0. It began in 2002 with new ideas to exchange as well as share the content such as Wiki, Weblogs, Widgets, and Tagging etc.
Key difference between web1.0 and web2.0

In Web 1.0 it is only for read. But in web2.0 you can express yourself by writing.
The former was only for corporate bodies. And the later is about you and your communities.
In web.20 you not only interact with site and webmaster you can also communicate with others who access that website.
Web 1.0 was the age of one and only language i.e. HTML web 2.0 is the field of XML.
While web1.0 was depended on advertising, web 2.0 has been popularized by word of mouth.
Previously was meant for website but web 2.0 is not for site it is also about blogs.
In Web 1.0 there was nothing to exchange. Everything was about one way. Through the emergence of web 2.0 you can exchange your thoughts with other and easily converse with them.
The Web 3.0 could be defined as semantic web, personalization like iGoogle, My Yahoo etc.
The semantic web is a more developed extension of WWW. Wit the help of this technology the web content can be conveyed not only in form of natural language, but also be readable by software agent which letting them to locate, share and assemble information more easily. The concept comes out from Sir Tim Berners-Lee the director of W3C with the vision to make the web medium for exchanging the data, information knowledge.
Other features of web 3.0
It will be more portable and personal.
More focused on the preferences of individuals (Me-onomy)
Advertising oriented.
Widgets with drag and drop facilities.
Dynamic content.
User behavior, user engagement etc.
Though this technology not yet capture the whole web world. It has been spreading out slowly. Some big online business houses have started to follow the standard of web 3.0 few of them are spoke.com, twine.com, wink.com. mybloglog.com, friendfeed.com etc.
Some significant features of web 2.0 technology
Clean and Simple design
Number of columns is few.
Simple navigation which is fixed in every pages of the site.
Central layout