Accusoft's Blog

Part 3: Media Query Pitfalls – Watch Out for These!

This blog post is Part 3 of a three-part series in which we explore the concept of responsive web design. In Part 1, we looked at how the evolution of web technologies has collided with consumer demands to create the problem responsive design solves. In Part 2, we showed how media queries enable responsive design. Now we’ll wrap things up by steering you clear of some of the most common pitfalls in a responsive design implementation.

So now you’re thinking, “this is great, look how much easier my life just got!” You knew that wouldn’t last long right?

Read more to learn about the media query pitfalls to watch.

It’s hard to imagine any single item that could please a web developer, an IT infrastructure manager, and an end user all at once. Ice cream or a good joke excepted, anything that makes one of these people happy usually makes at least one of the others miserable.

Tighten security to please the infrastructure maven, and you’ve made extra work for the developer and possibly compromised the user’s experience. Amp up the user experience and you’ve created bandwidth problems for the infrastructure maven and, again, more work for the web developer. (Everything makes more work for the web developer.)

Read more to see how a cloud document viewer makes everybody happy.

Part 2: Responsive Design and Media Queries

This blog post is Part 2 of a three-part series in which we explore the concept of responsive web design. In Part 1, we looked at how the evolution of web technologies has collided with consumer demands to create the problem responsive design solves. In this part, we’ll show an example of how media queries enable responsive design, and in Part 3 we’ll wrap things up by steering you clear of some of the most common pitfalls in a responsive design implementation.

Read more to see how media queries enable responsive design.

Part 1: How We Got Here

Driverless cars. 3-D printing. Large hadron colliders. As mankind surges toward Singularity, technological growth is occurring at break-neck speed in seemingly every industry there is. Information is being disseminated faster than ever over the Internet and is being consumed on multitudes of devices. Desktops, PCs, tablets, smartphones, TVs, and even cameras... with more undoubtedly in the pipeline. Consumers of online content, in large part, no longer view content on only one particular type of device. This dissemination of content to who-knows-what kind of device has resulted in new challenges for managers of online content.

Read more to explore the concept of responsive web design.

A preference for native file formats in eDiscovery – the electronic exchange of information in the discovery process in litigation – is now nearly the norm, despite some resistance in years past. When electronically stored information (ESI) is preserved throughout the discovery process in its native format, all potentially relevant information – including searchable text, annotations, and metadata – is preserved as well, and is readily available to sharp legal eyes and to the growing array of eDiscovery analysis tools.

Of those tools, one of the most talked-about today is predictive coding, the application of artificial intelligence and workflow processes to keyword search, filter, and sample eDiscovery content to identify what’s most relevant to the case, in order to make the process quicker and less labor-intensive. Critics say predictive coding amounts to replacing a lawyer’s experienced eyes and judgment with inferior programming, while proponents argue that it’s not only faster (hence cheaper), but also less likely to miss something small and important, when applied smartly. Although the jury is still out and challenges remain, recent word from federal and state benches points to growing acceptance of predictive coding, especially in cases involving thousands or millions of pages of discovery.

Read more to learn about predictive coding.