Slides from my talk at Emerce Conversion, Amsterdam on the importance of performance(page speed) for conversion.
Explore some of the performance issues we face when relying on third-party CRO products / services
Slides from my talk at NCC Group's Web Performance Day in May 2016.
Compares the features of apps and the web, what's great about each and explores some of the technologies that will allow us to build websites that can deliver native like experiences.
Building an Appier Web - Velocity Amsterdam 2016Andy Davies
Explores progressive web apps, what advantages they have versus native apps, how to build, and test them, and some of the challenges we still have ahead.
Slides from talk at Velocity Amsterdam 2016
The Case for HTTP/2 - GreeceJS - June 2016Andy Davies
HTTP/2 is here but why do we need it, how is it different to HTTP/1.1 and what does the mean for developers?
Slides from my talk at GreeceJS in Athens, June 2016
Adaptive Input — Breaking Development Conference, San DiegoJason Grigsby
Windows 8. Chromebook Pixel. Ubuntu Phone. These devices shatter another consensual hallucination that we web developers have bought into: mobile = touch and desktop = keyboard and mouse.
We have tablets with keyboards; laptops that become tablets; laptops with touch screens; phones with physical keyboards; and even phones that become desktop computers. Not to mention new forms of input like cameras, voice control, and sensors.
We've learned how to respond to screen size. Our next challenge is learning how to adapt to different forms of input.
When responsive web design meets the real worldJason Grigsby
The document discusses responsive web design and some of the challenges it faces. It recommends adopting a mobile first approach where the mobile styles are defined first before desktop styles, allowing for a progressive enhancement. It also emphasizes the importance of performance and ensuring responsive designs are not just focused on layout but also on optimizing for speed. Key techniques discussed include building mobile first, reordering media queries, keeping basic styles outside queries, and scoping images within media queries to avoid unnecessary downloads.
1. Mobile devices have become the primary way people access media through smartphones, tablets, and other screens. Most media interactions are with mobile screens and smartphone ownership continues to rise rapidly.
2. Opportunities on mobile go beyond apps to considering how mobile usage has changed user behavior and discovering the paths users take to content across multiple devices. User research is key to understanding this.
3. Design for mobile must optimize for thumb and eyeball-only interactions, use touch targets large enough for fingers, and consider network limitations. Images should be optimized for recognition or description.
Adapting to Input — Smashing Conference NYCJason Grigsby
Input is constantly evolving and expanding beyond traditional keyboard and mouse. The document discusses 7 principles for adapting web design to different inputs:
1. Design for the largest target by default.
2. Design for modes of interaction instead of specific inputs.
3. Make designs accessible to all inputs.
4. Support multiple concurrent inputs.
5. Abstract baseline inputs like tap, click, and point.
6. Progressively enhance with new inputs like gestures and sensors.
7. Include different inputs in testing plans.
The key message is that input cannot be detected, is a continuum, and is always changing. Web design needs to be adaptable and not assume certain inputs based on device properties.
Slides from my talk at NCC Group's Web Performance Day in May 2016.
Compares the features of apps and the web, what's great about each and explores some of the technologies that will allow us to build websites that can deliver native like experiences.
Building an Appier Web - Velocity Amsterdam 2016Andy Davies
Explores progressive web apps, what advantages they have versus native apps, how to build, and test them, and some of the challenges we still have ahead.
Slides from talk at Velocity Amsterdam 2016
The Case for HTTP/2 - GreeceJS - June 2016Andy Davies
HTTP/2 is here but why do we need it, how is it different to HTTP/1.1 and what does the mean for developers?
Slides from my talk at GreeceJS in Athens, June 2016
Adaptive Input — Breaking Development Conference, San DiegoJason Grigsby
Windows 8. Chromebook Pixel. Ubuntu Phone. These devices shatter another consensual hallucination that we web developers have bought into: mobile = touch and desktop = keyboard and mouse.
We have tablets with keyboards; laptops that become tablets; laptops with touch screens; phones with physical keyboards; and even phones that become desktop computers. Not to mention new forms of input like cameras, voice control, and sensors.
We've learned how to respond to screen size. Our next challenge is learning how to adapt to different forms of input.
When responsive web design meets the real worldJason Grigsby
The document discusses responsive web design and some of the challenges it faces. It recommends adopting a mobile first approach where the mobile styles are defined first before desktop styles, allowing for a progressive enhancement. It also emphasizes the importance of performance and ensuring responsive designs are not just focused on layout but also on optimizing for speed. Key techniques discussed include building mobile first, reordering media queries, keeping basic styles outside queries, and scoping images within media queries to avoid unnecessary downloads.
1. Mobile devices have become the primary way people access media through smartphones, tablets, and other screens. Most media interactions are with mobile screens and smartphone ownership continues to rise rapidly.
2. Opportunities on mobile go beyond apps to considering how mobile usage has changed user behavior and discovering the paths users take to content across multiple devices. User research is key to understanding this.
3. Design for mobile must optimize for thumb and eyeball-only interactions, use touch targets large enough for fingers, and consider network limitations. Images should be optimized for recognition or description.
Adapting to Input — Smashing Conference NYCJason Grigsby
Input is constantly evolving and expanding beyond traditional keyboard and mouse. The document discusses 7 principles for adapting web design to different inputs:
1. Design for the largest target by default.
2. Design for modes of interaction instead of specific inputs.
3. Make designs accessible to all inputs.
4. Support multiple concurrent inputs.
5. Abstract baseline inputs like tap, click, and point.
6. Progressively enhance with new inputs like gestures and sensors.
7. Include different inputs in testing plans.
The key message is that input cannot be detected, is a continuum, and is always changing. Web design needs to be adaptable and not assume certain inputs based on device properties.
Presented at Web Directions Code, Melbourne
If you have a website—particularly one that generates revenue for your organization—you need a Progressive Web App. So where do you begin? How do you decide which features of a Progressive Web App make sense for your users? What tools can make the process easier (or harder)? In this practical session, Jason will guide you through the key design decisions you’ll need to make about your Progressive Web App and how those decisions impact the scope of your project. He'll also teach you how to avoid common pitfalls and help you take full advantage of Progressive Web App technology.
Device Agnostic Design - UCD2014, London 25 Oct 2014Anna Dahlström
Slides from my Device Agnostic Design talk at UCD London
http://2014.ucduk.org/session/device-agnostic-design-how-to-get-your-content-to-go-anywhere/
ABSTRACT:
There was a time when we did glossy page designs and when those designs were pretty much what we saw in our desktop browsers. With the introduction and rise of smartphones, tablets, phablets there isn’t one view of our designs anymore.
Instead, what we create needs to be able to adapt in a way that is suitable for the device as well as where and how it’s being used.
With responsive design we’ve learnt the basics of how to adapt content, interactions and layouts so that it works across devices. But with further developments in technology and screens, our content is going to go anywhere. As a result we need to move away from designing for specific devices to solutions that are device agnostic. For us as UX designers this means means letting content rather than devices guide layouts, and also increasingly moving away from designing and wireframing pages to focusing on the modules that those views are made up of. But there are other aspects to consider in device agnostic design.
In this talk I walk through why device agnostic design matters, what it means and how we go about it.
Why Progressive Web Apps will transform your websiteJason Grigsby
Progressive web apps (PWAs) can transform websites by making them more like native apps through the use of service workers, web app manifests, and other modern web capabilities. Some key benefits of PWAs include providing fast and reliable experiences even on slow mobile networks, working regardless of a network connection, and engaging users through web app banners and push notifications. Early results show that PWAs can significantly reduce data usage and increase user engagement, conversion rates, and sales compared to mobile websites. While PWAs work across browsers, including on iOS, their full capabilities are still progressively being adopted.
February 2018: Sustainable UX ConferenceLisa Huang
The document is a slide presentation about AMP (Accelerated Mobile Pages) that discusses:
- Mobile web challenges like slow devices and networks where JavaScript does heavy lifting.
- How AMP addresses these with techniques like inlined CSS, prioritized resource loading, and async JavaScript to make pages load instantly.
- Examples of companies that use AMP and the types of content it works for.
- How AMP can be used as an entry point or data source to build progressive web apps with features like service workers for offline use.
The document discusses improving performance for mobile web experiences. It begins by outlining some of the key reasons why mobile web is typically slower than desktop, such as network latency and bandwidth limitations. It then examines the current state of the mobile web, including average page sizes and number of requests. The document proposes that responsive design alone is not enough to optimize for mobile and introduces the concept of adaptive or responsive design with server-side components (RESS). Some techniques discussed for RESS include device detection, image optimization, and CSS processing to remove unnecessary styles. The overall message is that a hybrid approach considering server capabilities alongside responsive design can help create faster, lighter mobile web experiences.
This document discusses techniques for optimizing image delivery on websites for faster performance. It outlines four simple optimizations: adjusting image quality, choosing optimal file formats like WebP and SVG, sizing images responsively, and lazy loading images below the fold. The document shows how these techniques can significantly reduce image file sizes and page load times based on analyzing 500,000 mobile websites. Common tools for implementing the optimizations are also presented.
Smart Design - Content-first, Fast, Informed, Refined. WordCamp NYC 2014
Fast, simple, SMART. Mobile devices have forever changed the way we interact with content. Now we have to consider many things such as HiDPI graphics, responsive design, speed, UI/UX patterns, touch target sizes, gestures, and more. All while not losing track of what’s important: Content.
We’re going to discuss the influence of mobile on design trends and learn implementation techniques of smart design.
In 2016, mobile internet usage exceeded desktop for the first time! With over 50% of users on mobile, is your web app optimized for them?
Let’s learn about Accelerated Mobile Pages, how AMP address mobile user challenges and build a valid AMP app together!
http://nodevember.org/speaker/Lisa%20Huang
SMX@adtech: Mobile Local and Video Search — Cindy Krumadtech_fan
The document provides tips for optimizing websites for mobile search engines. It discusses the differences between mobile and desktop search, including that mobile has carrier search engines that are often white-labeled versions of other engines. It also outlines strategies for mobile search engine optimization, including appropriate site architecture, clean code, relevant mobile content, and submitting the site to various mobile directories and search engines.
The document discusses responsive images and issues around their implementation. It begins by outlining the new <picture> element and srcset/sizes attributes that allow images to adapt based on screen size and resolution. It then discusses challenges like managing many images, the need for image breakpoints to determine appropriate file sizes, and the tension between responsive images and the browser's lookahead parser. Overall, the document examines both the promise and difficulties of responsive images on the modern web.
This document discusses how corporations can leverage digital technologies to enhance their intelligence. It suggests that a corporation's intelligence (IQcorp) depends on factors like fluid intelligence (Gf), crystallized intelligence (Gc), quantitative reasoning (Gq), memory (Gsm/Glr), processing speed (Gs), and decision speed (Gt). While humans currently excel in areas like fluid intelligence, digital technologies can augment corporations in other factors like crystallized intelligence, memory, and processing speed through techniques such as analytics, machine learning, and collaborative workflows. The document argues that through a symbiotic human-machine relationship, corporations can develop super-human levels of intelligence.
Making users happy is a goal that unifies everyone on the team. The key then is to establish metrics that reflect user happiness. In the world of performance, we haven’t always done a great job of this. Often, performance metrics track how our pages are built which might not be correlated with a joyous user experience, and we start optimizing our stack for the sake of optimizing our stack. Luckily, momentum is building around UX-centered metrics such as start render time, time-to-interact, and first meaningful paint. Steve Souders discusses these new metrics that help us build web apps that produce the fast, joyous experiences our users want.
Taking a tour through 1.0, 2.0 and 3.0 - blogs for content, Facebook for distribution and Google Earth for centralising location based information in the travel and tourism industry.
AB Testing, Ads and other 3rd party tags - SmashingConf London - 2018Andy Davies
Talk at Smashing Conf - 7th Feb 2018 (Video - https://vimeo.com/254703766)
Explores some of the issues that 3rd-party tags introduce when we add them to our sites, some ways of measuring the impact, and challenges we still have
Is the buzz around Progressive Web Apps real or are they simply the latest fad? In this talk, you’ll learn exactly what Progressive Web Apps are, what problems they solve, and what new design challenges they present. Jason will show how organizations are using Progressive Web Apps to provide better and faster user experiences.
Mobile Web Performance - Getting and Staying FastAndy Davies
Slides from mine and Aaaron Peter's talk at QCon London (Mar 2014) on how to measure mobile web performance, things that affect in and how to improve it
Building an Appier Web - London Web Standards - Nov 2016Andy Davies
Explores progressive web apps, what advantages they have versus native apps, how to build, and test them, and some of the challenges we still have ahead.
Slides from talk at London Web Standards, Nov 2016
Presented at Web Directions Code, Melbourne
If you have a website—particularly one that generates revenue for your organization—you need a Progressive Web App. So where do you begin? How do you decide which features of a Progressive Web App make sense for your users? What tools can make the process easier (or harder)? In this practical session, Jason will guide you through the key design decisions you’ll need to make about your Progressive Web App and how those decisions impact the scope of your project. He'll also teach you how to avoid common pitfalls and help you take full advantage of Progressive Web App technology.
Device Agnostic Design - UCD2014, London 25 Oct 2014Anna Dahlström
Slides from my Device Agnostic Design talk at UCD London
http://2014.ucduk.org/session/device-agnostic-design-how-to-get-your-content-to-go-anywhere/
ABSTRACT:
There was a time when we did glossy page designs and when those designs were pretty much what we saw in our desktop browsers. With the introduction and rise of smartphones, tablets, phablets there isn’t one view of our designs anymore.
Instead, what we create needs to be able to adapt in a way that is suitable for the device as well as where and how it’s being used.
With responsive design we’ve learnt the basics of how to adapt content, interactions and layouts so that it works across devices. But with further developments in technology and screens, our content is going to go anywhere. As a result we need to move away from designing for specific devices to solutions that are device agnostic. For us as UX designers this means means letting content rather than devices guide layouts, and also increasingly moving away from designing and wireframing pages to focusing on the modules that those views are made up of. But there are other aspects to consider in device agnostic design.
In this talk I walk through why device agnostic design matters, what it means and how we go about it.
Why Progressive Web Apps will transform your websiteJason Grigsby
Progressive web apps (PWAs) can transform websites by making them more like native apps through the use of service workers, web app manifests, and other modern web capabilities. Some key benefits of PWAs include providing fast and reliable experiences even on slow mobile networks, working regardless of a network connection, and engaging users through web app banners and push notifications. Early results show that PWAs can significantly reduce data usage and increase user engagement, conversion rates, and sales compared to mobile websites. While PWAs work across browsers, including on iOS, their full capabilities are still progressively being adopted.
February 2018: Sustainable UX ConferenceLisa Huang
The document is a slide presentation about AMP (Accelerated Mobile Pages) that discusses:
- Mobile web challenges like slow devices and networks where JavaScript does heavy lifting.
- How AMP addresses these with techniques like inlined CSS, prioritized resource loading, and async JavaScript to make pages load instantly.
- Examples of companies that use AMP and the types of content it works for.
- How AMP can be used as an entry point or data source to build progressive web apps with features like service workers for offline use.
The document discusses improving performance for mobile web experiences. It begins by outlining some of the key reasons why mobile web is typically slower than desktop, such as network latency and bandwidth limitations. It then examines the current state of the mobile web, including average page sizes and number of requests. The document proposes that responsive design alone is not enough to optimize for mobile and introduces the concept of adaptive or responsive design with server-side components (RESS). Some techniques discussed for RESS include device detection, image optimization, and CSS processing to remove unnecessary styles. The overall message is that a hybrid approach considering server capabilities alongside responsive design can help create faster, lighter mobile web experiences.
This document discusses techniques for optimizing image delivery on websites for faster performance. It outlines four simple optimizations: adjusting image quality, choosing optimal file formats like WebP and SVG, sizing images responsively, and lazy loading images below the fold. The document shows how these techniques can significantly reduce image file sizes and page load times based on analyzing 500,000 mobile websites. Common tools for implementing the optimizations are also presented.
Smart Design - Content-first, Fast, Informed, Refined. WordCamp NYC 2014
Fast, simple, SMART. Mobile devices have forever changed the way we interact with content. Now we have to consider many things such as HiDPI graphics, responsive design, speed, UI/UX patterns, touch target sizes, gestures, and more. All while not losing track of what’s important: Content.
We’re going to discuss the influence of mobile on design trends and learn implementation techniques of smart design.
In 2016, mobile internet usage exceeded desktop for the first time! With over 50% of users on mobile, is your web app optimized for them?
Let’s learn about Accelerated Mobile Pages, how AMP address mobile user challenges and build a valid AMP app together!
http://nodevember.org/speaker/Lisa%20Huang
SMX@adtech: Mobile Local and Video Search — Cindy Krumadtech_fan
The document provides tips for optimizing websites for mobile search engines. It discusses the differences between mobile and desktop search, including that mobile has carrier search engines that are often white-labeled versions of other engines. It also outlines strategies for mobile search engine optimization, including appropriate site architecture, clean code, relevant mobile content, and submitting the site to various mobile directories and search engines.
The document discusses responsive images and issues around their implementation. It begins by outlining the new <picture> element and srcset/sizes attributes that allow images to adapt based on screen size and resolution. It then discusses challenges like managing many images, the need for image breakpoints to determine appropriate file sizes, and the tension between responsive images and the browser's lookahead parser. Overall, the document examines both the promise and difficulties of responsive images on the modern web.
This document discusses how corporations can leverage digital technologies to enhance their intelligence. It suggests that a corporation's intelligence (IQcorp) depends on factors like fluid intelligence (Gf), crystallized intelligence (Gc), quantitative reasoning (Gq), memory (Gsm/Glr), processing speed (Gs), and decision speed (Gt). While humans currently excel in areas like fluid intelligence, digital technologies can augment corporations in other factors like crystallized intelligence, memory, and processing speed through techniques such as analytics, machine learning, and collaborative workflows. The document argues that through a symbiotic human-machine relationship, corporations can develop super-human levels of intelligence.
Making users happy is a goal that unifies everyone on the team. The key then is to establish metrics that reflect user happiness. In the world of performance, we haven’t always done a great job of this. Often, performance metrics track how our pages are built which might not be correlated with a joyous user experience, and we start optimizing our stack for the sake of optimizing our stack. Luckily, momentum is building around UX-centered metrics such as start render time, time-to-interact, and first meaningful paint. Steve Souders discusses these new metrics that help us build web apps that produce the fast, joyous experiences our users want.
Taking a tour through 1.0, 2.0 and 3.0 - blogs for content, Facebook for distribution and Google Earth for centralising location based information in the travel and tourism industry.
AB Testing, Ads and other 3rd party tags - SmashingConf London - 2018Andy Davies
Talk at Smashing Conf - 7th Feb 2018 (Video - https://vimeo.com/254703766)
Explores some of the issues that 3rd-party tags introduce when we add them to our sites, some ways of measuring the impact, and challenges we still have
Is the buzz around Progressive Web Apps real or are they simply the latest fad? In this talk, you’ll learn exactly what Progressive Web Apps are, what problems they solve, and what new design challenges they present. Jason will show how organizations are using Progressive Web Apps to provide better and faster user experiences.
Mobile Web Performance - Getting and Staying FastAndy Davies
Slides from mine and Aaaron Peter's talk at QCon London (Mar 2014) on how to measure mobile web performance, things that affect in and how to improve it
Building an Appier Web - London Web Standards - Nov 2016Andy Davies
Explores progressive web apps, what advantages they have versus native apps, how to build, and test them, and some of the challenges we still have ahead.
Slides from talk at London Web Standards, Nov 2016
HTTP/2 is a new version of the HTTP network protocol that aims to improve website performance. It uses a single TCP connection to allow multiple requests and responses to be multiplexed together. This improves efficiency over HTTP/1.1. Additionally, HTTP/2 allows servers to push critical resources like CSS files to clients, potentially reducing load times. While HTTP/2 brings performance benefits, challenges remain around widespread server support and differing optimizations between HTTP/1.1 and HTTP/2.
Performance Testing using Real Browsers with JMeter & WebdriverBlazeMeter
Learn how to easily run performance tests with real browsers using Selenium WebDriver.
Ophir Prusak, BlazeMeter’s Chief Evangelist, gives step-by-step instructions on doing this using BlazeMeter and/or JMeter.
Learn how to:
- Correlate actual browser-based user experience with the load tests
- Run multiple Selenium Webdriver tests in parallel at scale by using the power of the cloud
- Do it all without any prior JMeter knowledge or experience!
How Slow Load Times Hurt Your Bottom Line (And 17 Things You Can Do to Fix It)Tammy Everts
This document discusses how slow page load times can hurt a website's bottom line. It notes that a 2% increase in conversions is seen for every 1 second improvement in load times. Examples are given of companies that cut load times in half and increased conversions by 9% and increased downloads by 15.4%. The document outlines two main causes of slow performance: pages being too big in size and pages being too complex. It provides tips on how to address these issues, such as compressing assets, lazy loading images, consolidating resources, and optimizing third-party scripts.
Sadece uygulamalarınızın değil database sorgularınızın da performansını ölçmek için JMeter kullanabilirsiniz.
Güçlü bir teknik test ürünü olan JMeter ile hangi sorgunuzun daha sorunlu olduğunu bulalım.
You can use JMeter not only for measuring your applications performance but also your database queries.
With this powerfull technical test tool, you can discover which database queries takes most of the time.
Speed matters, So why is your site so slow?Andy Davies
Slides from my talk at ReDevelop 2015
Covers business case for web performance, along with the fundamentals of how latency and the critical rendering path affect page load performance
This document discusses improving mobile user experiences. It notes that mobile is the primary way people access the internet in some countries. Constraints on mobile like form factor and battery life must be considered. Simple interfaces work best for mobile. Native apps have advantages over mobile web, but the line is blurring. Windows Mobile was replaced by Windows Phone 7 which improved the user experience. The document emphasizes understanding user behaviors and focusing on usability.
How to Design for the Future - Cross Channel Experience DesignOSCON Byrum
This document discusses cross-channel experience design. It begins by asking who the audience members are and what they hope to learn. It then discusses some key principles of cross-channel design such as providing a consistent, convenient, connected, and contextual experience across different channels over time. The document provides examples of both good and bad cross-channel experiences. It concludes by outlining five methods for designing cross-channel experiences, such as thinking in terms of services rather than individual channels, sharing resources between teams, starting with small experiments, embracing challenges, and focusing on why changes are being made rather than just what is being changed.
How to Design for the Future - Cross Channel Experience DesignSamantha Starmer
This document discusses cross-channel experience design. It begins by asking who the audience members are and what they hope to learn. It then discusses some of the key challenges of designing experiences across multiple channels like websites, mobile apps, physical stores, etc. The document presents five principles for cross-channel design: providing a consistent experience, making the experience convenient across channels, ensuring transitions between channels are connected, tailoring the experience to the user's current context, and designing experiences that span time across different touchpoints. It concludes by offering five methods for approaching cross-channel design, such as thinking in terms of services rather than individual channels, collaborating across organizational boundaries, testing designs by observing user behaviors, being comfortable with ambiguity and iteration
This document provides credits and sources for the images used in a slide presentation. Pictures were sourced from websites related to sports, business, finance, and law. Stock images depicted topics like money, handshakes, contracts, fees, conflicts, and regulations. Information about sports law was sourced from a 2010 textbook.
Endpoint Security Fundamentals Part 3: Building the Endpoint Security ProgramLumension
In the final part of this series, Mike Rothman, analyst with Securosis, takes the steps and enforcement controls discussed from parts 1 and 2 and examines how to build a real-world, defense-in-depth security program – one that is sustainable and one the does not impede business productivity.
The document discusses designing experiences for multiple devices. It notes that users now own and switch between multiple devices throughout the day, from phones to tablets to wearables. As such, designers must consider how to provide equal, continuous experiences across different platforms and prioritize building modular content that can be adapted for any device or input method. Navigation and usability must work seamlessly regardless of screen size or input type.
Beyond The Hamburger Menu - MOBX, 13 Sep 2014Anna Dahlström
The document discusses designing experiences for multiple devices. It notes that users now own and switch between multiple devices throughout the day, from phones to tablets to wearables. As such, designers must consider how to provide equal, continuous experiences across different platforms and prioritize building modular content that can be adapted for any device or input method. Navigation and usability must work seamlessly regardless of device.
This document summarizes how information technology (IT) infrastructure and operations have changed from expensive and slow on-premise systems to cheaper and faster cloud-based systems. It notes that IT used to require renting and maintaining thousands of servers, but now services allow provisioning servers quickly and returning them just as fast. Where systems used to support small numbers of users, they now must scale to massive "web scale." Tool usage has proliferated from using just a few tools to manage dependencies to using many different monitoring and analytics tools. Delivery cycles have accelerated from biannual releases to continuous delivery. It promotes a next-generation monitoring solution to help development and operations teams address these modern cloud-era challenges through data aggregation, correlation, collaboration
The document describes the need for designing cross-channel experiences that are consistent, convenient, connected, contextual, and span different touchpoints and times. It discusses examples of both good and bad cross-channel experiences, and outlines five principles for designing holistic experiences. Tools mentioned for mapping cross-channel experiences include stakeholder interviews, field research, touchpoint matrices, service inventories, and experience maps. The overall message is that users interact with brands through many different channels, so the design must consider the entire experience across all touchpoints.
UCD14 Talk - Anna Dahlstrom - Device Agnostic Design: How to get your content...UCD UK Ltd
The document discusses device agnostic design, which aims to create content that can be accessed and displayed well on any device. It emphasizes building with reusable modular components rather than bespoke designs for each device. The key aspects are understanding content stacking strategies across screens, using content-based rather than device-based breakpoints, and designing interactive elements that work for both touch and non-touch interfaces. The goal is to provide users with a continuous experience regardless of the device they use.
This presentation is divided into the following sections:
- A brief history of collaboration and sharing
- An introduction into "2.0" and consumer tools reaching into the business world
- Attention. Collaboration. Discovery.
- A quick demo of Socialtext Dashboard, Workspaces, and People
- Best practices for successful implementation and adoption of social software
- Things to look for in choosing a vendor
The Future of Design is Not Just the Web - Web Visions Workshop 2011Samantha Starmer
The document discusses designing cross-channel experiences. It begins by explaining that customers experience brands across multiple touchpoints and channels, both digital and physical. The key is to design experiences that are convenient, connected, consistent, contextual, and span across time.
The document then provides five principles and five methods for cross-channel design. The principles are to make experiences convenient, connected, consistent, contextual, and spanning across time. The methods are to think in terms of services, share design work across teams, start by observing customer behaviors, be comfortable with ambiguity, and focus on customer needs rather than specific solutions.
Finally, the document discusses various discovery and solution activities for cross-channel design, such as stakeholder interviews
This document lists and summarizes various 1 trick productivity tools including tools for copyright friendly image search, scheduling meetings, converting PDFs, shortening URLs, speed reading, and editing YouTube videos. Links are provided for each tool described.
This document lists various one-trick productivity tools organized by category, including alarms, backchannels, cloud backup, image search, cropping pictures, email scheduling, finding broken links, WiFi locations, Google 411, highlighting on the web, password management, scheduling meetings, converting PDFs, resizing pictures, pronunciation help, polling, quick polls, paper printing, reading the web later, reminders, screencasting, shortening URLs, speed reading, text to speech, weather reports, checking web status, white noise generators, and editing YouTube videos. Each tool is briefly described and includes a URL.
Semantics, Deep Learning, and the Transformation of BusinessSteve Omohundro
Deep learning is likely to have a big impact on business. McKinsey predicts that AI and robotics will create $50 trillion of value over the next 10 years. Over $1 billion of venture investment has gone to 250 deep learning startups over the past year. Deep learning systems have recently broken records in speech recognition, image recognition, image captioning, translation, drug discovery and other tasks. Why is this happening now and how is it likely to play out? We review the development of AI and the pendulum swings between the "neats" and the "scruffies". We describe traditional approaches to semantics through logics and grammars and the new deep learning vector semantics. We relate it to Roger Shepard's cognitive geometry and the structure of biological networks. We also describe limitations of deep learning for safety and regulation. We show how it fits into the rational agent framework and discuss what the next steps may be.
Up close and personal - Future of Digital 2010Rob Manson
This document discusses the emergence of the personal platform in 2010, as mobile devices, wireless speeds, screens, cameras, augmented reality, and wearable displays advance. It notes that by the 2000s, all the components for the next computing platform existed, and 2010 will bring "jedi computing" as these technologies converge. The personal platform will allow for always-on connectivity, enhanced access to information, hyper-social connectivity, and the ability to see multiple perspectives and capture rich digital histories. The conclusion asks what each person's personal platform will be like.
Endpoint Security Fundamentals Part 2: Leveraging the Right Enforcement ControlsLumension
This document discusses various endpoint security controls that organizations can leverage to protect their endpoints. It recommends that patching and secure configuration deliver significant protection while having the best cost-benefit ratio. Application whitelisting is highlighted as a way to address weaknesses in anti-malware solutions, though it can impact the user experience. USB device control and full disk encryption are also presented as methods for keeping data secure by restricting where it can be used or accessed. The document encourages organizations to evaluate which endpoint security controls are most needed based on their specific threat environment and business needs.
More people are using mobile platforms to access information - can your business afford to be left behind in an age of rapid digital transformation?
When once it was acceptable to be in the late majority when it came to adjusting your business to technological advancements, nowadays you have to lead the pack in order to be a viable business.
AB Testing, Ads and other 3rd party tags - London WebPerf - March 2018Andy Davies
Talk at Smashing Conf - 7th Feb 2018 (Video - https://vimeo.com/254703766)
Explores some of the issues that 3rd-party tags introduce when we add them to our sites, some ways of measuring the impact, and challenges we still have
Inspecting iOS App Traffic with JavaScript - JSOxford - Jan 2018Andy Davies
This document discusses inspecting iOS app traffic with JavaScript by injecting scripts using Frida. It demonstrates capturing encrypted network traffic from an iOS app, extracting the TLS master secret and client/server randoms using a Frida script, and sending these values to the host computer to allow decrypting the traffic with Wireshark. The key steps are: using Frida to inject a script into an app, hooking the TLS PRF function to extract secret values, and sending these to the host to decrypt the HTTPS traffic in Wireshark. With these techniques, patterns in encrypted app traffic can be observed.
Slides from my talk at Bristol WebPerf Meetup 2017-07-20 where I talked about some of the approaches I use to persuade people that they should invest in making their sites faster
Speed: The 'Forgotten' Conversion FactorAndy Davies
Speed is a critical factor when it comes to converting browsers into buyers but it's often forgotten and other factors prioritised instead. Using real data from UK retailers this talk explores the relationship between speed and conversion
The Case for HTTP/2 - Internetdagarna 2015 - StockholmAndy Davies
HTTP/2 is here but why do we need it, how is it different to HTTP/1.1 and what does the mean for developers?
Slides from my talk at Internetdagarna 2015, Stockholm
The document discusses how mobile sites are getting slower due to larger page sizes from images, CSS, JavaScript and fonts. It provides tips for optimizing images, such as using responsive images and smaller image sizes. It also recommends prioritizing critical content over non-essential elements like unnecessary JavaScript and web fonts to improve page load times.
The Case for HTTP/2 - EpicFEL Sept 2015Andy Davies
HTTP/2 is here but why do we need it, and how is it different to HTTP/1.1?
Video - https://www.youtube.com/watch?v=ob-CnA9YmiI
These are the slides from my talk at Front-End London's one day conference, EpicFEL
HTTP/2 addresses limitations in HTTP/1.x by multiplexing requests over a single TCP connection, compressing headers, and allowing servers to push responses. It leads to more efficient use of network resources and faster page loads. While browser support is good, server implementations are still maturing and need to fully support HTTP/2 features like streams, dependencies, and server push to provide optimizations. Efficient TLS is also important to avoid delays in taking advantage of HTTP/2 performance benefits.
HTTP/2 provides improvements over HTTP/1.1 such as multiplexed requests, header compression and priority hints from browsers that can reduce latency. While it shows benefits in testing, real-world impacts may be more modest depending on server and client configurations. Further optimizations are still needed and HTTP/2 opens up new possibilities around features like server pushing and progressive content delivery that could enhance performance.
This document discusses the importance of website speed and performance. It notes that most top retail sites take over 3 seconds to load critical content, and median page load times have slowed by 23% year-over-year. Faster sites see benefits like 10% higher conversions. Network latency has a greater impact on performance than bandwidth. Techniques like preloading fonts and images can help mitigate latency. Frameworks and features like service workers may also help if designed deliberately for performance. Regular measurement and setting performance budgets are recommended to build fast user experiences.
Talk from The Web Is in Cardiff, October 2014 exploring the business case for web performance, and some of the underlying factors that can make sites slow
Are Today’s Good Practices… Tomorrow’s Performance Anti-Patterns?Andy Davies
Talk from Akamai Edge 2014 looking at some of our current web performance optimisation practices and how they may need to change as new standards and protocols emerge
The document discusses improving page load performance on websites. It notes that many sites are currently too slow and outlines some strategies to minimize latency, round trips, and blocking of page loads. These include prioritizing important content in the first round trip, automating optimization processes, and measuring performance directly in the user's browser to better understand why pages are slow and how to fix those issues. The document emphasizes that performance is an important part of user experience that needs more consideration in website design.
Are Today’s Good Practices… Tomorrow’s Performance Anti-Patterns?Andy Davies
This document discusses how performance best practices may become anti-patterns as technologies evolve. It explores how techniques like data URIs, domain sharding, and CSS sprites could be negatively impacted by new protocols like SPDY. The author advocates experimenting with modern tools like mod_pagespeed to test different optimizations under various conditions and sharing results. Continued improvement of debugging tools is also important to help evaluate new approaches as the network landscape changes. Overall, the message is that situational optimization will become more important over rigid rules as complexity increases.
Web Performance Workshop - Velocity London 2013Andy Davies
The document summarizes a hands-on web performance workshop. It discusses tools and techniques that will be covered, including live analysis of websites. Attendees are encouraged to ask questions and suggest sites to test. Various tools for performance testing like PhantomJS, Phantomas, and WebPageTest are introduced. The workshop also discusses integrating performance tests with TAP and Jenkins. Additional topics include processing performance data in R, looking at live sites, issues like unnecessary repainting, and lessons learned in web performance optimization.
Are Today’s Good Practices... Tomorrow’s Performance Anti-Patterns?Andy Davies
The web is ever changing… browsers are evolving, new protocols are emerging and mobile continues its relentless rise. We’re already starting to bend some of the original performance rules and as the web changes further will our current good practices last, or will some become barriers that hinder performance?
Are Today's Good Practices… Tomorrow's Performance Anti-PatternsAndy Davies
The document discusses how current web performance optimization practices may become obsolete or anti-patterns with new web technologies like HTTP/2 and SPDY. It summarizes results of tests comparing HTTP/1.1 to SPDY, finding that SPDY is faster with minimal optimizations. The document also examines how practices like sharding assets and inline JavaScript may not work as expected or introduce new issues with these protocols. It recommends starting to experiment now with tools like mod_pagespeed and mod_spdy to understand the effects of new technologies on performance best practices.
Corporate Open Source Anti-Patterns: A Decade LaterScyllaDB
A little over a decade ago, I gave a talk on corporate open source anti-patterns, vowing that I would return in ten years to give an update. Much has changed in the last decade: open source is pervasive in infrastructure software, with many companies (like our hosts!) having significant open source components from their inception. But just as open source has changed, the corporate anti-patterns around open source have changed too: where the challenges of the previous decade were all around how to open source existing products (and how to engage with existing communities), the challenges now seem to revolve around how to thrive as a business without betraying the community that made it one in the first place. Open source remains one of humanity's most important collective achievements and one that all companies should seek to engage with at some level; in this talk, we will describe the changes that open source has seen in the last decade, and provide updated guidance for corporations for ways not to do it!
The "Zen" of Python Exemplars - OTel Community DayPaige Cruz
The Zen of Python states "There should be one-- and preferably only one --obvious way to do it." OpenTelemetry is the obvious choice for traces but bad news for Pythonistas when it comes to metrics because both Prometheus and OpenTelemetry offer compelling choices. Let's look at all of the ways you can tie metrics and traces together with exemplars whether you're working with OTel metrics, Prom metrics, Prom-turned-OTel metrics, or OTel-turned-Prom metrics!
this resume for sadika shaikh bca studentSadikaShaikh7
I am a dedicated BCA student with a strong foundation in web technologies, including PHP and MySQL. I have hands-on experience in Java and Python, and a solid understanding of data structures. My technical skills are complemented by my ability to learn quickly and adapt to new challenges in the ever-evolving field of computer science.
Tool Support for Testing as Chapter 6 of ISTQB Foundation 2018. Topics covered are Tool Benefits, Test Tool Classification, Benefits of Test Automation and Risk of Test Automation
Metadata Lakes for Next-Gen AI/ML - DatastratoZilliz
As data catalogs evolve to meet the growing and new demands of high-velocity, unstructured data, we see them taking a new shape as an emergent and flexible way to activate metadata for multiple uses. This talk discusses modern uses of metadata at the infrastructure level for AI-enablement in RAG pipelines in response to the new demands of the ecosystem. We will also discuss Apache (incubating) Gravitino and its open source-first approach to data cataloging across multi-cloud and geo-distributed architectures.
Dev Dives: Mining your data with AI-powered Continuous DiscoveryUiPathCommunity
Want to learn how AI and Continuous Discovery can uncover impactful automation opportunities? Watch this webinar to find out more about UiPath Discovery products!
Watch this session and:
👉 See the power of UiPath Discovery products, including Process Mining, Task Mining, Communications Mining, and Automation Hub
👉 Watch the demo of how to leverage system data, desktop data, or unstructured communications data to gain deeper understanding of existing processes
👉 Learn how you can benefit from each of the discovery products as an Automation Developer
🗣 Speakers:
Jyoti Raghav, Principal Technical Enablement Engineer @UiPath
Anja le Clercq, Principal Technical Enablement Engineer @UiPath
⏩ Register for our upcoming Dev Dives July session: Boosting Tester Productivity with Coded Automation and Autopilot™
👉 Link: https://bit.ly/Dev_Dives_July
This session was streamed live on June 27, 2024.
Check out all our upcoming Dev Dives 2024 sessions at:
🚩 https://bit.ly/Dev_Dives_2024
Balancing Compaction Principles and PracticesScyllaDB
Compaction is a crucial component for preventing storage consumption from exploding. In this session, we’ll talk about why compaction is required and its principles of operation, the main compaction strategies available for use, when they should be used, and how they can be configured. Finally, we’ll present new compaction features recently introduced in ScyllaDB Enterprise and ScyllaDB Cloud.
What is an RPA CoE? Session 4 – CoE ScalingDianaGray10
How to scale a COE to meet organizational missions.
Topics covered:
• What is the original focal area?
• How to expand the COE globally.
• Is a centralized or decentralized model better for scaling?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/efficiency-unleashed-the-next-gen-nxp-i-mx-95-applications-processor-for-embedded-vision-a-presentation-from-nxp-semiconductors/
James Prior, Senior Product Manager at NXP Semiconductors, presents the “Efficiency Unleashed: The Next-gen NXP i.MX 95 Applications Processor for Embedded Vision” tutorial at the May 2024 Embedded Vision Summit.
Machine vision is the most obvious way to help humans live better, enabling hundreds of applications spanning security, monitoring, inspection and more. Modern edge processors need private on-device and scalable hybrid machine learning capabilities to offer enough longevity to stay relevant in industrial and commercial IoT markets. In this talk, Prior presents the upcoming i.MX 95 family of applications processors.
The i.MX 95 features a new, self-developed neural processing unit from NXP—the eIQ Neutron NPU. Designed to scale from today’s conventional neural networks to tomorrow’s transformer-based models, the eIQ Neutron NPU scalable architecture delivers edge AI capabilities at high efficiency with award-winning tools, combined with chip-level security and privacy features. The i.MX 95 applications processor family features powerful processing and vision capabilities combined with safety, security and expandable high-speed interfaces.
Database Management Myths for DevelopersJohn Sterrett
Myths, Mistakes, and Lessons learned about Managing SQL Server databases. We also focus on automating and validating your critical database management tasks.
Brightwell ILC Futures workshop David Sinclair presentationILC- UK
As part of our futures focused project with Brightwell we organised a workshop involving thought leaders and experts which was held in April 2024. Introducing the session David Sinclair gave the attached presentation.
For the project we want to:
- explore how technology and innovation will drive the way we live
- look at how we ourselves will change e.g families; digital exclusion
What we then want to do is use this to highlight how services in the future may need to adapt.
e.g. If we are all online in 20 years, will we need to offer telephone-based services. And if we aren’t offering telephone services what will the alternative be?
Call Girls Kochi 💯Call Us 🔝 7426014248 🔝 Independent Kochi Escorts Service Av...
The Fast, The Slow and The Unconverted - Emerce Conversion 2016
1. The Fast, The Slow, and the Unconverted
https://www.flickr.com/photos/dvanzuijlekom/14579895325/
@AndyDavies, NCC Group
2. “Has it loaded yet?”
http://www.flickr.com/photos/kindofindie/4099768084
3. Response Time in Man-computer Conversational Transactions
Robert B. Miller, 1968
How we perceive response times
100ms 1s 10s
IRUK Retail Top 100 : Average 1.8s delay before page starts showing content
4. “50% more concentration when using
badly performing web sites”
Foviance
http://www.flickr.com/photos/yourdon/3366991042
10. Increased conversions by 10%
Shaved 1 second off median home page time
6 seconds off 98th percentile
http://www.slideshare.net/cliffcrocker/velocity-ny-how-to-measure-revenue-in-milliseconds
11. Improved load time from 1.2s to 0.5s
+28% page views / session
+21% time on site / visit
+20% conversion rate
http://blog.quanta-computing.com/etam-earns-20-of-conversion-by-optimising-its-online-store/
12. “We reduced latency by 0.3s across the funnel and
customers spent 8m a year in additional revenue”
Mark Holt, CTO, Trainline
New Relic London Summit 2016