Not all that sparkles is gold. It could be a really beautiful Wix website with images of gold, like these jewelry websites we have here today. The exquisite taste of the Wix users who created these sites is evident not only in the jewelry, but also in the web design itself. Beautiful photographs placed just right, wonderful use of typography and great product display are just some of the niceties these sites have to offer. These websites, created with the HTML5 website builder, do a terrific job in presenting jewelry pieces as prestige and desirable objects. This is not bling, this is class.
Archivo de la etiqueta: Adobe Flash
Con el término inglés plug-in se hace referencia normalmente a distintas funciones optativas que mejoran el funcionamiento de otros programas, de los que dependen, o que les dotan de pequeñas nuevas capacidades.
En internet, esta palabra suele hacer referencia a dos conceptos: al complemento necesario en un navegador web para poder ver o ejecutar material multimedia de distintas fuentes (por ejemplo, para ver los vídeos de YouTube, es necesario descargar el complemento para Flash de Adobe) y a los accesorios (también llamado en inglés add-on) que mejoran o amplían las funciones del propio navegador.
Además de por complemento, en algunos casos también se puede traducir por extensión.
El estandar web más popular de la historia sigue cediendo, sólo horas de vida le quedan a Flash para Android. Adobe confirma que a partir de mañana la aplicación no se podrá descargar y eliminarán cualquier vía oficial para instalarlo en los terminales basados en el SO móvil de Google.
Que moriría no es noticia nueva, ya lo sabíamos y el cese del soporte se recalcó hace unas semanas cuando se dio a conocer Android 4.1 Jelly Bean. Sin embargo, no fue hasta ahora que Adobe se manifestó y reveló el momento en que matará definitivamente a Flash para Android.
Esto no quiere decir que de tener el APK no lo podrán instalar más adelante y mucho menos dejará de funcionar a quienes ahora mismo lo tienen instalado en sus terminales. Sólo no habrá ningún tipo soporte para correcciones de fallos o futuras actualizaciones para mejorar la compatibilidad porque es inevitable el avance. Sigue leyendo
With close to a decade of experience in web design, I have come across plenty of mistaken beliefs about the latest design tools and technologies; but nothing beats the misconceptions surrounding the use of HTML 5.
As developers, we have our own set of misguided beliefs about a certain technology, but as we begin to use that technology we are able to understand what it is all about, its usage, and its scope.
Inspired by certain HTML5 requirements that I have come across through the course of time, I wanted to add my two cents to clear the air on certain aspects of HTML5. Most of the misconceptions surrounding HTML5 are because many people think it’s a replacement for Flash.
At the outset, I would like to make it clear that this is not an HTML5 vs. Flash post. The truth is that one cannot act as the replacement for the other, so there is no ‘us vs. them’ battle. But, therein is the nub of the misconceptions. The problem is that people believe HTML5 is an enhanced alternative to Flash. All misconceptions are a result of this thinking.
Landing pages have evolved a lot over the past five years.
Back in 2007, landing pages were almost cliché — what I would call Landing Pages 1.0. Take this example from Google — yes, Google — with the prototypical structure: a headline, a short description or some bullets, a small image (“hero shot”), and a form.
Adobe’s decision to cease development of the mobile Flash platform and increase their investment in HTML5-related efforts created perhaps the final piece of conclusive evidence that HTML5 is the current go-to technology for creating ubiquitous user experiences regardless of device.
While there’s been an abundant amount of discussion on what this means to developers, there’s been a lack of focus on what this means to the overall user experience (UX). If HTML5 thrives where Flash struggled and becomesthe dominator in the choice for new mobile and desktop technology, will users benefit from the transition? Yes, as long as designers and developers do their jobs right.
Different stroke for different folks
It might seem strange to compare Flash and HTML5 at all, since they are so inherently different. Whereas Flash is proprietary, HTML5 is continually developing through open source collaboration. If Flash is a seasoned monarchy, then HTML5 is the wild wild west. It’s important to note that there are tons of applications and sites in which Flash and native apps will remain the preferred choice of implementation. However, that doesn’t mean that we can’t explore the major differences between the two in order to discuss the gaps that HTML5 can fill where Flash is lacking.
Flash, by nature, is a control freak. It demands browsers have the latest plugin, or it will be sure to let you know if it’s unhappy with your version – perhaps even go on strike until you upgrade. It thrives on presenting a consistent, desktop-centric experience of typefaces and layout, and never bothers to worry about changing the user experience based on device nor the context of what you might want to do on that device. But Flash has had years to evolve from the land of bouncy ball demos and splash screens to the product for creating some fantastically innovative interfaces.
By contrast, HTML5 excels at giving users a delightfully inconsistent experience on any device through the concepts of “graceful degradation” and “progressive enhancement.” Both concepts are designed to provide users the best possible experience each browser allows for, whether a content area displays a static image in Internet Explorer 6, or a fully functional HTML5 video in Chrome. Since desktop browser usage runs the entire spectrum of worst- to best-case scenarios, this way of designing user experiences can help ensure that all users get the most bang for their buck out of their browsers. Gone are the days of being forced into creating identical experiences based on the best performance of the worst browser.
Those who advocate web standards also support the important role HTML5 plays in responsive web design, or the systematic display of content, tasks, and layout, depending on whether the user is viewing the site on a mobile or desktop-sized browser. The reasons why people view the same website on a mobile device versus a desktop is often very different. For example, a user viewing a site for a restaurant while sitting at their office desk could likely want to view a workflow more supportive of exploring the menu, reviews and other content that would help decide if it’s a good place to eat. On the other hand, a user viewing the site from the passenger seat of a car might want to quickly find content based on the assumption that they have already decided to eat there, such as directions or the phone number. Sigue leyendo