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.
Role Of A Webmaster In Creating And Maintaining A Website
A webmaster is a person who handles the maintenance of a website making sure that the web servers, hardware and software function systematically. He is the sole architect of the information contained in a website that includes both words and pictures. He has other responsibilities like designing the website, generating and revising web pages, replying to user comments and analyzing traffic through the site. A webmaster is generally qualified in HTML and other scripting languages like JavaScript, PHP and Perl. They may also require a thorough knowledge of configuring web servers such as Apache (web server software that played a significant role in the development of the World Wide Web) and serve as the server administrator.
Companies that hire a webmaster usually have different roles for them that depend on their requirements or financial state. In a smaller company, typical webmaster is responsible for many functions simultaneously. In a larger company, a webmaster is hired on account of their sound technical knowledge and programming skills and who has specialized in a certain area of expertise. There may be a team of webmasters who take over the overall corporate web design and policies and work with people who provide the company with its network infrastructure and supervise the design of the companys website. There may be additional web developers whose duties are to organize and develop the web content. All these various departments of webmasters inter-relate the creation of a website, content and organization, for the corporations intranet.
The essential qualities to look for in an efficient webmaster are intelligence, enthusiasm for web technology, exceptionally good communication skills, thoroughness and an eye for detail, integrity, ability to be an efficient team player, courtesy, professionalism, experience in web development and finally knowledge of Perl, UNIX, HTML, CGI and JavaScript. Other than constant maintenance of websites and their designs and management of web servers, they must also possess knowledge of Perl programming, maintenance of site maps, maintenance of mirror sites, assistance in site promotion, writing entries for the glossary, providing top level user support, maintenance of search engine index, HTML validation, generation of the top 100 page from the access logs, monitoring the error logs and reporting potential problems, verification on the validity of the links on the site, checking presentation and readability in different browsers available at various platforms, editing the content, maintenance of the quality and style of the site, finding, creating and installing tools to develop web content and eventually check them for consistency and development of interactive web applications.
Some of the most basic roles of a webmaster in general are as follows:
– HTML Authoring: They need an understanding of HTML 2.0, 3.2, 4, Dynamic HTML including other extensions like tables, frames, server-push/client-pull, server-side includes etc.
– CGI Scripting: Includes having knowledge of Perl, C and UNIX shell scripts.
– Basic Graphic Designing: Must possess the ability to develop attractive web pages that live up to the given standards.
– Internet Awareness: Must be well acquainted with issues concerning the Internet and the World Wide Web.
– General UNIX and PC (MS-Windows) awareness
– Basic knowledge of TCP/IP and Networking
– Graphic Designing skills: An apprehension of graphics applications and techniques like Photoshop, Fractal Painter, 3D modeling and so on.
– Customer Awareness: Must have the capacity to manage a professional relationship with the customers and work within their requirements.
– WWW Server Configuration: Must show proficiency in NCSA, CERN, Apache, and Netscape Commercial Server – including NSAPI.
[Top]Web Team Roles And Responsibilities
Many people are involved in any web project. Different web projects require different web teams who have their roles and responsibilities.
Content Expert/Client:
Mostly a Content Expert is a Client who determines the project objectives, target audience and user needs, site information and its architecture, provides content materials and other additional resources, provide feedback on content, design and development. Client is the best person who knows the subject matters and requirements of the web site.
Requirements Modeler:
This person is responsible for the collection and maintenance of the system requirements. He is responsible to collect all necessary information of the requirements of the clients and understands how to utilize the design activities accordingly.
Project Manager:
Planning and management of all human and technological elements of the project. His responsibilities includes interaction with client, planning, budgeting, designing of basic concept, management of all other team members involved, supervising the content, technical development, site testing, release and its evaluation, and management of project completion within the time limit and within the budget.
System Architect:
Construction of structure on which the entire web project is to be build is the responsibility of System Architect. To perform this activity lot of skill is required which include excellent modeling skill and he should be experienced with various systems and various designs. His role includes deciding how to organize the content of the website, how to link different web pages and the navigation of all web pages.
System Developer:
He is responsible to build the functionality of the website. They are responsible for integrating components, developing new components and conducting the detailed design of the system.
Content Developer/Content Writer:
This person develops the content of the website that is the information to be provided on the website. His responsibilities includes knowing the content needs, designing the layout of content, research about the content and creating a new content, HTML coding and validating, processing images and maintenance of the content.
Web Designer:
Web Designer is responsible to configure the information and functionalities of the website for effective communication. They work with graphic designer and system developer to make the information and its layout more effective and more real.
Graphic Designer:
The responsibility of Graphic Designer is to prepare the content and layout for the final system which includes photographs, videos, music clips, and much more. He is responsible for developing the overall look of the website to make it more stylish and presentable. He solves the problems which are related to the graphic layout of the web pages, typography, color combinations and the overall consistency. Image processing and web optimization, developing HTML templates and browser/platform testing of the HTML layouts is also done by Graphic Designer.
Configuration Manager:
This person is responsible for the management of configuration which includes configuration identification, control, auditing and status accounting.
System Tester:
Verification and Validation of all the components of the system that whether they are constructed according to the requirements or not is done by system tester. He does the detailed study of each and every components of the website methodically.
All these persons are involved in the designing and development of the website and by the team work of all of them only it is possible to build a successful website which meets clients requirements.
[Top]How to Design a professional Web Site ….be simple!
It’s hard to find information on how to be a designer You can easily find loads of stuff in books or online to inspire you about beautiful graphics, and plenty of technical know-how on CSS, HTML and code. But if you want to find out how to be a web designer, structure a site that succeeds, decide on layout and craft pages that work, there are very few resources available.
Simple solutions are always the best.
The goals of each web design can vary greatly from one project to the next, but we should always strive for efficiency and simplicity. This will deliver a cleaner result that facilitates accurate communication with less margin for error. It also takes less work to make something simple than it does to make something complex. When crafting a web page, We aim to use as few -things- as I need to achieve the purpose. -Things- includes pages, words, pictures, choices, gradients, borders, boxes, graphics, columns etc. etc.. This helps make each step seem more obvious and feel easy.
This approach isn’t new. Economy has always been one of the core disciplines in Art and in Design. The Old Masters were masters of economy. Look at the brush strokes on an old painting, and you’ll see how much people achieved with so few strokes. It’s not that they didn’t have the talent, or the time, to do more strokes, it’s just that they knew that using as few strokes of the brush as possible to create the desired effect produces the best result. Using rougher strokes on areas like backgrounds or material on clothing helped the eye to focus on the finer detail.
The same goes for web design. While your mode of interaction with a web site is very different to a painting, a lot of the principles that artists have used for centuries can apply to any medium. Web designers should follow the same discipline to apply only as much detail as is necessary, putting it where it’s most needed, to manage viewers’ attention.
Our experience, along with a great passion for art and design, are the right and ideal solution to understand and meet your web requirements.
Ideen & label studios, Web Design Milano! Born to help you improve your business ! Visit us on www.ideeenlabel.com
[Top]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 (<td>), in paragraph tags (<p>) or span tags (<span>)
Below is an example of an inline style insert into a table cell tag:
<td width=”400″ align=”left” valign=”top” style=”color:#000000; font-family:Arial, Helvetica, sans-serif; font-size:11px;”>
This style would then apply to the text contents of that table cell. Other standard HTML formatting tags such as <strong>, <em>, <font> 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.
<td style=” Lucida Console, Arial, Helvetica, sans-serif; “>
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.
[Top]