Know Your Apps

Evolution of Web Apps

Not long ago, the web was for ‘surfing’; its main purpose was to provide information. To perform set tasks, users bought and installed software onto their desktop. Key to knowing your web apps is understanding how technologies have shaped the evolution of web apps; web apps are now offering as much, if not more than the desktop application.

HTML5 has enabled developers to break free of the limits they were used to when building web applications

Asynchronous web apps have transformed user interaction

Things have fundamentally changed since the early days of the web, when web page content was static. Today, page’s load or change dynamically, rather than performing an entire round-trip of all content.

New language standards provide richer user experience

Prior to HTML5 support in modern browsers, the features needed to build web applications was inconsistent, and often required the use of plug-ins like Flash, ActiveX or Java. New open web platform standards like CSS3, HTML5, and JavaScript ensure that developers have the tools and features they need to build more beautiful and interactive web apps than ever before.

Figure 1.1 - New technology broadens our capabilities!

The Future of Web Apps

Critics of the web app are quick to point out one of the main drawbacks - web application users must have an internet connection to get stuff done. Given that the web is not accessible all the time and everywhere, users cannot be fully reliant on web applications to do their work. Or at least, that has been the assumption.

It is up to you to make sure your web apps use the technologies available.

The future of web apps is about flexibility - having all the benefits of performing tasks over the web, while also being able to perform those tasks offline. Offline support is already possible - HTML5 offers features like application cache and client-side storage (e.g., local storage, indexed databases) so that your application can run even without a network connection.

The cloud offers users more than a desktop

The cloud provides a platform on which server side functionality can be hosted and shared. Using web apps hosted in the cloud, users can collaborate with others and themselves across multiple devices, saving data in secured servers. Without heavy overhead costs, web apps can be distributed at a fraction of the cost of desktop applications.

Figure 1.2 - Use your device to its fullest potential!

Properties of Web Apps

Web applications are redefining what it means to be ‘on the web’; the web is becoming an equal mix of web sites and web applications. Here are three main factors that distinguish web apps from web sites:

Web Applications can be as complex as spreadsheets, document editors or as simple as to-do list manager. Whatever it is, it should do something!

1.A web application provides a great user experience, making it easy for users to complete their tasks and takes advantage of the device’s native capabilities.
2.A web application provides rich visual experiences that will delight the eye without distracting the mind; it puts a premium on aesthetics and uses similar design paradigms as native applications without sacrificing usability.
3.A web application has a tight focus encouraging people to interact, engage, and accomplish something, rather than passively view content. The application is self-contained, allowing the user to complete their tasks without navigating to other sites or apps.

Figure 1.3 - Small, big, simple, complex? Just do something!

Checklist for Identifying Web Apps

Is it mostly self-contained, without redirecting me to a completely different experience to complete what I set out to do?
Can I interact, engage and accomplish something by using the application?
Does it have a rich user interface that looks nice, and takes advantage of the full size of the window available to it?

If you answered yes to most of these questions, then what you're looking at is most likely a web application.

Does it use the same paradigms as native applications for buttons, dialogs and other components?
Does it work offline?
Is it using the capabilities of the device it’s running on, for example location data through the GPS and motion sensors?
Are traditional website navigation elements and links hidden from view?
Is the app designed around a primarily client-side architecture model?

Self Contained!
Functional!
Immersive!
Interactive!
Work Offline!
Device Aware!
New Navigable!
Ajaxcellent!
Excellent!

Figure 1.4 - Checked them all? Excellent!