Beyond Squishy: The Principles of Adaptive DesignBrad Frost
Responsive web design has hit the scene like a bomb, and now designers everywhere are showing off to their bosses and peers by resizing their browser windows. "Look! The site is squishy!"
While creating flexible layouts is important, there's a whole lot more that goes into truly exceptional adaptive web experiences. This session will introduce the Principles of Adaptive Design: ubiquity, flexibility, performance, enhancement and future-friendliness. We need go beyond media queries in order to preserve the web's ubiquity and move it in a future-friendly direction.
Atomic Design - An Event Apart San DiegoBrad Frost
Design systems, not pages. This is an introduction to atomic design (http://bradfrostweb.com/blog/post/atomic-web-design/), a methodology for crafting an effective interface design system. It also introduces Pattern Lab (http://patternlab.io/), a tool for implementing atomic design systems and pattern libraries.
This document discusses Atomic Design, a methodology for building design systems. It begins by explaining that interfaces are made of systems of components, not just pages. It then discusses frameworks like Foundation and Bootstrap, as well as their potential pitfalls. The document introduces Atomic Design and its principles of separating interfaces into abstract and concrete levels. It explains Pattern Lab as a tool for building design systems and provides examples of existing style guides. Overall, the document advocates for a systematic approach to design to improve collaboration and build reusable and scalable components.
The Server Side of Responsive Web DesignDave Olsen
Responsive web design has become an important tool for front-end developers as they develop mobile-optimized solutions for clients. Browser-detection has been an important tool for server-side developers for the same task for much longer. Unfortunately, both techniques have certain limitations. Depending on project requirements, team make-up and deployment environment combining these two techniques might lead to intriguing solutions for your organization. We'll discuss when it makes sense to take this extra step and we'll explore techniques for combining server-side technology, like server-side feature-detection, with your responsive web designs to deliver the most flexible solutions possible.
React Storybook, Atomic Design, and ITCSSTrevor Pierce
This document discusses the evolution of web design methodologies from static pages to dynamic single-page applications. It introduces Atomic Design and ITCSS as approaches to bring more structure and scalability to component-based design systems. The author learns to design directly in React using Atomic patterns, CSS Modules, and PostCSS to address challenges with CSS organization and scaling. They create a living style guide using Storybook to demonstrate these techniques.
MIMA 2014 - Changing your Responsive Design Workfloweaselsolutions
Presentation slides from Dustin Tauer's 2014 MIMA Session:
What is your Web workflow? If your situation mirrors that of most organizations, the process often begins with some initial planning and discovery, followed by the design phase. In the design phase, Photoshop is opened and wireframes evolve into static designs. Once approved, these designs are passed to the developer which leads to testing, tweaking, and finally, launch. This workflow is great for traditional websites, but major evolution is needed to account for the changing landscape that is responsive design.
This session will present different strategies and processes for effectively designing and developing responsive websites. We’ll look at how taking a content-first approach rather than a design-first approach can significantly reduce the number of issues and iterations throughout the process. With mobile traffic quickly surpassing desktop traffic, a new workflow process is imperative to helping us be better prepared for the constantly changing device landscape.
Beyond Squishy: The Principles of Adaptive DesignBrad Frost
Responsive web design has hit the scene like a bomb, and now designers everywhere are showing off to their bosses and peers by resizing their browser windows. "Look! The site is squishy!"
While creating flexible layouts is important, there's a whole lot more that goes into truly exceptional adaptive web experiences. This session will introduce the Principles of Adaptive Design: ubiquity, flexibility, performance, enhancement and future-friendliness. We need go beyond media queries in order to preserve the web's ubiquity and move it in a future-friendly direction.
Atomic Design - An Event Apart San DiegoBrad Frost
Design systems, not pages. This is an introduction to atomic design (http://bradfrostweb.com/blog/post/atomic-web-design/), a methodology for crafting an effective interface design system. It also introduces Pattern Lab (http://patternlab.io/), a tool for implementing atomic design systems and pattern libraries.
This document discusses Atomic Design, a methodology for building design systems. It begins by explaining that interfaces are made of systems of components, not just pages. It then discusses frameworks like Foundation and Bootstrap, as well as their potential pitfalls. The document introduces Atomic Design and its principles of separating interfaces into abstract and concrete levels. It explains Pattern Lab as a tool for building design systems and provides examples of existing style guides. Overall, the document advocates for a systematic approach to design to improve collaboration and build reusable and scalable components.
The Server Side of Responsive Web DesignDave Olsen
Responsive web design has become an important tool for front-end developers as they develop mobile-optimized solutions for clients. Browser-detection has been an important tool for server-side developers for the same task for much longer. Unfortunately, both techniques have certain limitations. Depending on project requirements, team make-up and deployment environment combining these two techniques might lead to intriguing solutions for your organization. We'll discuss when it makes sense to take this extra step and we'll explore techniques for combining server-side technology, like server-side feature-detection, with your responsive web designs to deliver the most flexible solutions possible.
React Storybook, Atomic Design, and ITCSSTrevor Pierce
This document discusses the evolution of web design methodologies from static pages to dynamic single-page applications. It introduces Atomic Design and ITCSS as approaches to bring more structure and scalability to component-based design systems. The author learns to design directly in React using Atomic patterns, CSS Modules, and PostCSS to address challenges with CSS organization and scaling. They create a living style guide using Storybook to demonstrate these techniques.
MIMA 2014 - Changing your Responsive Design Workfloweaselsolutions
Presentation slides from Dustin Tauer's 2014 MIMA Session:
What is your Web workflow? If your situation mirrors that of most organizations, the process often begins with some initial planning and discovery, followed by the design phase. In the design phase, Photoshop is opened and wireframes evolve into static designs. Once approved, these designs are passed to the developer which leads to testing, tweaking, and finally, launch. This workflow is great for traditional websites, but major evolution is needed to account for the changing landscape that is responsive design.
This session will present different strategies and processes for effectively designing and developing responsive websites. We’ll look at how taking a content-first approach rather than a design-first approach can significantly reduce the number of issues and iterations throughout the process. With mobile traffic quickly surpassing desktop traffic, a new workflow process is imperative to helping us be better prepared for the constantly changing device landscape.
Responsive Design Workflow (Breaking Development Conference 2012 Orlando)Stephen Hay
Slides from my presentation at Breaking Development 2012 in Orlando. This deck is not intended to be standalone, and probably made more sense in combination with my talk. At least, I hope so. I understand that video of the talk will be available in the near future on the Breaking Development website.
Mobile First Responsive Web Design — BD Conf Oct 2013Jason Grigsby
The document discusses responsive web design and mobile-first approaches. It advocates building responsive designs with a mobile-first mindset, where the mobile version is prioritized and expanded upon for larger screens rather than the desktop version being scaled down. It also emphasizes performance techniques like keeping images out of breakpoints to avoid unnecessary downloads, and using media queries to scope images to only the viewports that need them. The overall message is that responsive design should consider both layout and performance to provide the best experience across devices.
Atomic Design es una filosofía de creación de productos tecnológicos basada en la creación de elementos complejos utilizando elementos más sencillos. Pattern Lab es una plataforma basada en esta filosofía para crear sitios web con un diseño consistente. En esta presentación, explico un poco como funciona cada uno.
All matter, no matter how complex, can be broken down into molecules which can be broken down further into atomic elements. All web interfaces can be broken down down the same way. Atomic Design provides a methodology for building an effective design system. It consists of five distint stages: atoms, molecules, organisms, templates and pages.
Data science for infrastructure dev week 2022ZainAsgar1
The document discusses using data science and automation for infrastructure monitoring. It introduces Pixie, a tool that allows users to collect raw data, transform it into signals, and then take actions based on those signals. Two examples are provided: 1) detecting SQL injections from application logs and sending Slack alerts, and 2) automatically scaling a deployment based on HTTP request throughput metrics. Pixie uses an embedded domain-specific language called PxL to define logical data workflows and queries.
The document summarizes key techniques for responsible responsive web design, including building mobile-first responsive designs, keeping CSS images in their place, conditionally loading JavaScript based on screen size and capabilities, delivering different sized images at different screen sizes, and handling high-density images carefully. It also discusses debates around whether a one-size-fits-all responsive approach can compete with a tailored experience and ensuring responsive designs are optimized for performance.
Presentation by Clarissa Peterson for LVL Studio's UX Soiree, November 21, 2012, in Montreal, Quebec. Overview of responsive design with focus on user experience.
Websites are all about content. People can access your content many different ways and formats with mobile devices, iPads, phones, etc. The questions are: how can we maintain control over the display of our content and keep our brand consistent? How can we try to provide the best user experience on any platform? Enter Responsive Web Design. Many experts are not leaning on one static design but on structured content that adapts to its given environment. In this talk, we are going to take a look at responsive web design techniques out there including: progressive enhancement, flexible grids, media queries, flexible images & video, & other methods of implementation.
When it comes to CSS, the "sanctity" of the Separation of Concerns principle (SoC) has lead us to accept bloat, obsolescence, redundancy, poor caching, and more. We're introducing a new CSS architecture that we called "Atomic CSS". It challenges best practices to address many of these common issues.
Presentation to:
Madison Web Design & Development Meetup - February 11, 2013.
Web Content Mavens, Washington, DC - January 8, 2013.
NYC Web Design Meetup -January 24, 2013.
The document discusses designing experiences for the mobile web. It notes that the mobile web is profoundly different than the desktop experience due to different contexts and portability. Some key decisions for mobile web design include whether to have a single or dual-site approach, how to structure navigation and content for smaller screens, and usability testing approaches. It also describes a case study of redesigning a website for mobile and some of the challenges encountered.
Every URL visited from the Facebook iPhone app is done through a webview. Same with Twitter. Even if you don't have a mobile app, your website gets a lot of traffic from webviews. And yet, testing on webviews is challenging. There are significant performances differences between UIWebView vs WkWebView, and similarly for Android webview vs the new Chromium webview. And what about home screen apps?! In this talk, Steve Souders discusses the differences across webviews and how that affects performance of mobile web apps.
Stefan Judis "Did we(b development) lose the right direction?"Fwdays
Keeping up with the state of web technology is one of the biggest challenges for us developers today. We invent new tools; we define new best practices, everything’s new, always... And we do all that for good user experience! We do all that to build the best possible web – it’s all about our users.
But is it, really? Or do developers like to play with technology secretly loving the new and shiny? Or do we only pretend that it’s about users, and behind closed doors, it’s developer experience that matters to us? Did we lose direction? Is it time for a critical look at the state of the web and the role JavaScript plays in it?
Presented during Javascript MVC Amsterdam meetup, 29 Jan 2014: http://www.meetup.com/JavaScript-MVC-Meetup-Amsterdam/events/156767102/
At De Voorhoede (http://voorhoede.nl) I'm responsible for setting up new front-end projects in such a way that it's easy for teams to work with. This presentation explains how we structure these projects. The presentation includes some tips on structuring larger AngularJS projects.
The document discusses optimizing user experience across devices through responsive design. It explains that responsive design allows a single website to be accessed from any device by adjusting the layout. The key aspects of responsive design are flexibility and adjustability. It emphasizes starting with content and designing for the context of use through small-screen first approaches and testing on actual devices. Frameworks like Foundation can help with responsive design, and style tiles help communicate visual designs. The goal is to provide equal access to content on any device.
Covers frameworks, navigation patterns, preprocessors, responsive images, responsive data tables, polyfills. Presentation at the Cleveland Web Standards Association, October 30, 2012.
High Performance Mobile (SF/SV Web Perf)Steve Souders
1. The document discusses optimizing websites for high performance mobile experiences. It provides 14 best practices for mobile optimization, including making fewer HTTP requests, using content delivery networks, gzipping components, and optimizing images.
2. Mobile optimization is important because mobile internet usage is growing rapidly. Performance impacts metrics like user experience and revenue.
3. Tools for measuring and improving mobile performance are introduced, such as PcapPerf for analyzing network traffic and Weinre for debugging JavaScript on mobile devices. Faster mobile sites will have an advantage as mobile becomes the primary internet platform.
This document discusses responsive web design (RWD). RWD allows websites to automatically adjust their layout depending on the user's screen size using media queries. It is important for accessibility and usability as most internet users now access the web on mobile devices. The document recommends using a mobile-first and progressive enhancement approach where basic content and functionality work on all browsers and advanced features are progressively added. It provides examples of RWD techniques and tools to test responsive designs.
Responsive Design Workflow (Breaking Development Conference 2012 Orlando)Stephen Hay
Slides from my presentation at Breaking Development 2012 in Orlando. This deck is not intended to be standalone, and probably made more sense in combination with my talk. At least, I hope so. I understand that video of the talk will be available in the near future on the Breaking Development website.
Mobile First Responsive Web Design — BD Conf Oct 2013Jason Grigsby
The document discusses responsive web design and mobile-first approaches. It advocates building responsive designs with a mobile-first mindset, where the mobile version is prioritized and expanded upon for larger screens rather than the desktop version being scaled down. It also emphasizes performance techniques like keeping images out of breakpoints to avoid unnecessary downloads, and using media queries to scope images to only the viewports that need them. The overall message is that responsive design should consider both layout and performance to provide the best experience across devices.
Atomic Design es una filosofía de creación de productos tecnológicos basada en la creación de elementos complejos utilizando elementos más sencillos. Pattern Lab es una plataforma basada en esta filosofía para crear sitios web con un diseño consistente. En esta presentación, explico un poco como funciona cada uno.
All matter, no matter how complex, can be broken down into molecules which can be broken down further into atomic elements. All web interfaces can be broken down down the same way. Atomic Design provides a methodology for building an effective design system. It consists of five distint stages: atoms, molecules, organisms, templates and pages.
Data science for infrastructure dev week 2022ZainAsgar1
The document discusses using data science and automation for infrastructure monitoring. It introduces Pixie, a tool that allows users to collect raw data, transform it into signals, and then take actions based on those signals. Two examples are provided: 1) detecting SQL injections from application logs and sending Slack alerts, and 2) automatically scaling a deployment based on HTTP request throughput metrics. Pixie uses an embedded domain-specific language called PxL to define logical data workflows and queries.
The document summarizes key techniques for responsible responsive web design, including building mobile-first responsive designs, keeping CSS images in their place, conditionally loading JavaScript based on screen size and capabilities, delivering different sized images at different screen sizes, and handling high-density images carefully. It also discusses debates around whether a one-size-fits-all responsive approach can compete with a tailored experience and ensuring responsive designs are optimized for performance.
Presentation by Clarissa Peterson for LVL Studio's UX Soiree, November 21, 2012, in Montreal, Quebec. Overview of responsive design with focus on user experience.
Websites are all about content. People can access your content many different ways and formats with mobile devices, iPads, phones, etc. The questions are: how can we maintain control over the display of our content and keep our brand consistent? How can we try to provide the best user experience on any platform? Enter Responsive Web Design. Many experts are not leaning on one static design but on structured content that adapts to its given environment. In this talk, we are going to take a look at responsive web design techniques out there including: progressive enhancement, flexible grids, media queries, flexible images & video, & other methods of implementation.
When it comes to CSS, the "sanctity" of the Separation of Concerns principle (SoC) has lead us to accept bloat, obsolescence, redundancy, poor caching, and more. We're introducing a new CSS architecture that we called "Atomic CSS". It challenges best practices to address many of these common issues.
Presentation to:
Madison Web Design & Development Meetup - February 11, 2013.
Web Content Mavens, Washington, DC - January 8, 2013.
NYC Web Design Meetup -January 24, 2013.
The document discusses designing experiences for the mobile web. It notes that the mobile web is profoundly different than the desktop experience due to different contexts and portability. Some key decisions for mobile web design include whether to have a single or dual-site approach, how to structure navigation and content for smaller screens, and usability testing approaches. It also describes a case study of redesigning a website for mobile and some of the challenges encountered.
Every URL visited from the Facebook iPhone app is done through a webview. Same with Twitter. Even if you don't have a mobile app, your website gets a lot of traffic from webviews. And yet, testing on webviews is challenging. There are significant performances differences between UIWebView vs WkWebView, and similarly for Android webview vs the new Chromium webview. And what about home screen apps?! In this talk, Steve Souders discusses the differences across webviews and how that affects performance of mobile web apps.
Stefan Judis "Did we(b development) lose the right direction?"Fwdays
Keeping up with the state of web technology is one of the biggest challenges for us developers today. We invent new tools; we define new best practices, everything’s new, always... And we do all that for good user experience! We do all that to build the best possible web – it’s all about our users.
But is it, really? Or do developers like to play with technology secretly loving the new and shiny? Or do we only pretend that it’s about users, and behind closed doors, it’s developer experience that matters to us? Did we lose direction? Is it time for a critical look at the state of the web and the role JavaScript plays in it?
Presented during Javascript MVC Amsterdam meetup, 29 Jan 2014: http://www.meetup.com/JavaScript-MVC-Meetup-Amsterdam/events/156767102/
At De Voorhoede (http://voorhoede.nl) I'm responsible for setting up new front-end projects in such a way that it's easy for teams to work with. This presentation explains how we structure these projects. The presentation includes some tips on structuring larger AngularJS projects.
The document discusses optimizing user experience across devices through responsive design. It explains that responsive design allows a single website to be accessed from any device by adjusting the layout. The key aspects of responsive design are flexibility and adjustability. It emphasizes starting with content and designing for the context of use through small-screen first approaches and testing on actual devices. Frameworks like Foundation can help with responsive design, and style tiles help communicate visual designs. The goal is to provide equal access to content on any device.
Covers frameworks, navigation patterns, preprocessors, responsive images, responsive data tables, polyfills. Presentation at the Cleveland Web Standards Association, October 30, 2012.
High Performance Mobile (SF/SV Web Perf)Steve Souders
1. The document discusses optimizing websites for high performance mobile experiences. It provides 14 best practices for mobile optimization, including making fewer HTTP requests, using content delivery networks, gzipping components, and optimizing images.
2. Mobile optimization is important because mobile internet usage is growing rapidly. Performance impacts metrics like user experience and revenue.
3. Tools for measuring and improving mobile performance are introduced, such as PcapPerf for analyzing network traffic and Weinre for debugging JavaScript on mobile devices. Faster mobile sites will have an advantage as mobile becomes the primary internet platform.
This document discusses responsive web design (RWD). RWD allows websites to automatically adjust their layout depending on the user's screen size using media queries. It is important for accessibility and usability as most internet users now access the web on mobile devices. The document recommends using a mobile-first and progressive enhancement approach where basic content and functionality work on all browsers and advanced features are progressively added. It provides examples of RWD techniques and tools to test responsive designs.
This module introduces designing for mobile devices and all platforms using responsive design. Students will learn to design mobile sites without scripting using media queries and fluid layout techniques. Exercises include designing a mobile version of an existing site at 320px wide, making it usable on any size screen, and optimizing it for all screen sizes using responsive techniques.
Web Apps and Responsive Design for LibrariesMatt Machell
This document discusses responsive web design for libraries. It argues that responsive web design, which creates a single website that adapts to different screen sizes through flexible grids and media queries, is the best approach for libraries to take for their mobile presence. Native apps, separate mobile sites, and other approaches each have drawbacks, as they require more maintenance and do not allow for a unified experience across all devices. The document advocates for a responsive design that can provide a quality experience on any device using existing web skills.
This document discusses different approaches to mobile web development, including native apps, mobile web apps, and hybrid apps. It describes native apps as using device APIs and being optimized for performance but costly to maintain across platforms. Mobile web apps use HTML, CSS, and JavaScript and are low-cost with broad compatibility but lack access to device features. Hybrid apps combine web technologies with native wrappers to access device APIs and offer "write once, run everywhere" capabilities. The document also covers mobile development strategies, frameworks, and tools like Cordova that can help build hybrid mobile apps.
This is the Responsive Web Design presentation given to the CIDD, Chicago Interactive Design & Development Meetup group, (sponsored by the WunderLand Group) on 3-13-14 by Ryan Dodd, Design Director for Siteworx in Chicago.
This document discusses micro frontends, which divide large web applications into independent, standalone units. It outlines the issues with traditional monolithic applications, such as increased complexity and difficulty scaling. Micro frontends address these issues by allowing independent teams to work on separate application pieces with different technologies. The document covers micro frontend design considerations, communication patterns between units, and technical implementations using Angular Elements and the Frint framework.
10 stops towards a responsive web design mindsetMiika Puputti
The document outlines 10 steps towards developing a responsive web design mindset. It recommends starting with thinking about different devices and contexts, prototyping content for different screen sizes, collaborating cross-functionally, creating a consistent design language, simplifying content for mobile, using a mobile-first approach, extensively testing on devices, using tools to preview across devices, focusing on details, and designing with the future in mind. The overall goal is to create content that works well across a variety of devices and contexts.
This document discusses 6 rules for responsive web design:
1. Responsive design doesn't end with squishy layouts - optimize based on user capabilities rather than just screen size.
2. There is no responsive pixie dust - streamline workflows and use rapid prototypes and style tiles to communicate fluid layouts.
3. Your workflow will change - iterate designs quickly through prototypes rather than big reveals.
4. Your tools will change - leverage preprocessors like SASS and frameworks like Foundation for responsive coding.
5. The web is responsive by default - prioritize content and build APIs to support multiple platforms.
6. Embrace unpredictability - acknowledge the constraints of different devices
1 : https://www.eeoc.gov/eeoc/newsroom/release/10-7-19.cfm
2 : https://www.eeoc.gov/eeoc/newsroom/release/11-29-17c.cfm
3: https://www.eeoc.gov/eeoc/newsroom/release/10-2-19b.cfm
4: https://www.eeoc.gov/eeoc/newsroom/release/12-5-19a.cfm
5: https://www.eeoc.gov/eeoc/newsroom/release/10-22-19.cfm
6: https://www.eeoc.gov/eeoc/newsroom/release/10-2-18c.cfm
7: https://www.eeoc.gov/eeoc/newsroom/release/12-30-19.cfm
8: https://www.eeoc.gov/eeoc/newsroom/release/11-19-18.cfm
9: https://www.eeoc.gov/eeoc/newsroom/release/10-25-16.cfm
Usability Test Template
1. Create a document with the following areas. You will use your document during the usability test next week.
2. Goal of the site:
Explain the goal of your site in 2-3 sentences.
3. User testing detail:
Name, phone, age, employment, special interests, and any other items you are interested in.
4. Pre-test questions:
Create three questions to ask your tester prior to the test. These questions should be aimed to gather information regarding your test as a potential user of the site.
5. Test tasks and schedule
· Write a series of steps for the user to follow in using your site. At a minimum the user should be able to navigate the site, check out the specials and subscribe to the newsletter.
· Attempt to gain information regarding how the user feels about the site.
· Use the “Talk Aloud” method of gaining user feedback.
6. Post-test debrief:
Come up with 3 questions to ask the user regarding their input about the site
7. Usability Scale
Use these items to rate your test’s feeling about the site. You may use the items as questions in the post-test debrief.
· Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design?
· Efficiency: Once users have learned the design, how quickly can they perform tasks?
· Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency?
· Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors?
· Satisfaction: How pleasant is it to use the design?
Design Principles
Some content from:
The Principles of Beautiful Web Design
(Jason Beaird and James George)
Principles of Web Design
(Joel Sklar)
1
Learning Outcomes
apply user-centred design principles and methods
understand and be able to follow a suitable design process
appreciate the design principles that make a “good” website
be able to apply these principles at a basic level
2
Design Process
somewhere between art, science, and problem solving
the process of creating a design comp
can be boiled down to:
discovery
exploration
implementation
3
What's a comp?
the word comp is an abbreviation of the phrase “comprehensive dummy” –
a term that comes from the print design world.
complete simulation of a printed layout created before the layout goes to press.
in Web design, a comp is an image of a layout that’s created before we ...
Modern Digital Design: The power of Responsive DesignValtech UK
You've probably already heard of the term Responsive Design. Currently it's one of the hot topics being discussed in the digital space and something many businesses are trying to get their heads around.
So what exactly is Responsive Design? And why does it matter?
Inclusive design: real accessibility for everyoneChris Mills
Chris Mills gives a presentation on inclusive design and accessibility. He defines inclusive design as considering all users, including those with disabilities, using mobile devices, or with low bandwidth. He outlines 10 principles of inclusive design such as being equitable, flexible, simple and intuitive. He provides examples of how to implement these principles through techniques like adaptive layouts, alternative text, and consistent navigation. The overall message is that inclusive design benefits all users and is just good design.
How to create a mobile version of your websiteMahmoud Farrag
This document provides guidance on creating a mobile version of a website. It discusses considerations for mobile design including speed, dimensions, behavior, and designing. It emphasizes the importance of speed for mobile and provides tips for fluid layouts, CSS media queries, touch interfaces, short pages, and mobile development tools.
In this session, we will explore the how the recent explosion of devices has disrupted the process of designing a website that we've crafted over the past decade.
When designers only have one instance of website (i.e., desktop) to design, the layout is uniform. The header, content area, sidebar, and footer all remain static. Furthermore, the elements are relatively uniform as well. Buttons, navigation, typography, and images are all basically the same across across the various pages. But if you are designing a responsive website – one whose look and feel adapts depending whether you're using a phone, laptop, or tablet – then these elements and especially the layout begin to diverge.
After this session, you should leave with the confidence to argue the importance of responsive design to your client or boss – and that the with the proper strategy, the extra effort and costs can be justified (and hopefully minimized).
The browser has been called the "most hostile software development
environment imaginable." While at the same time, the ubiquity of the
browser is exactly what makes a web application so powerful. A good
web application is designed to run everywhere and for everyone. Today
that means supporting more browsers on more devices than any time in
history. This session will explore the challenges (and fun) of
building sites in a multi-platform and multi-device world while still enabling features of the Open Web like HTML5 and CSS3.
Ready to go Mobile? Today's Mobile Landscape: Responsive, Adaptive, Hybrid, a...Jeremy Johnson
There are a number of options when going mobile, and it's not slowing down. Why choose one over the other? What are the strengths and pitfalls? What's right for your customers and users? We'll go over each option, with examples of how you can come to the right strategy around your mobile offerings.
5 Simple Actions to Make a Measurable Impact on Your Responsive Site5th Finger
Our President, Patrick Collins, presented at eTail East 2013 in Philadelphia, PA, on 5 Simple Actions to Make a Measurable Impact on Your Responsive Site. Listen to what he had to say, and contact him with any questions or comments at patrick.collins@5thfinger.com.
Users spend most of their time using mobile apps rather than mobile web. Some key best practices for mobile development include considering hardware constraints like limited memory and storage, connectivity issues, and screen size variability. Apps can be monetized through paid downloads, ads, in-app purchases, or freemium models. Native, web, hybrid, and cross-platform are categories of mobile apps. User experience must be optimized for small screens and mobile contexts.
Web development is evolving at a breakneck speed every passing year. New website technologies are being discovered regularly as developers explore new ways of innovation.
To make it easier for you, I have analyzed the shifts across industries and created an ultimate list of some of the latest web development trends in 2022.
Similar to Responsive Webdesign - UXtour Microsoft (20)
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Building RAG with self-deployed Milvus vector database and Snowpark Container...Zilliz
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
20. A separate mobile website (3)
‣ You’ll have to manage all your
content twice
21. A separate mobile website (4)
‣ Users share links.
‣ Different users use different devices.
22. A separate mobile website
(conclusion)
‣ Only optimized for small screens
‣ Need to provide all content
‣ content has to be managed twice
‣ Issues when sharing content
‣ Pretty expensive for an unsatisfying result
27. Native apps (1)
Cfr. separate mobile website:
‣ What about tablet pc’s?
‣ Mobile users ≠ users on the road
‣ You’ll have to manage all your
content twice
28. Native apps (2)
‣ Which platforms will you support?
(iOS, Android, WindowsPhone)
‣ Each update:
- cost per platform
- might take time (approval)
30. Native apps (4)
‣ What about search engines?
‣ Your content won’t be indexed by them
31. Native apps (5)
‣ links to websites open in a new app (!)
‣ no native browser functions
(bookmarking!)
‣ non selectable text (no copy-paste)
‣ App’s often have their own interface
language
32. Remind you to something?
‣ issues with links to other websites
‣ no native browser functions like bookmarking
‣ non selectable text (no copy-paste)
‣ each interface is different
35. (of course native apps can
be the best answer)
‣ If you need hardware functions that
browsers don’t yet support (camera,
compass, gyroscope, gpu power, ...).
36. Native apps (conclusion)
‣ Different platforms to support
‣ Cut on in-app-purchases
‣ Content has to be managed twice and won’t
be indexed by search engines
‣ Risk on usability issues
‣ Only if you need specific hardware functions
37. In a lot of cases, neither separate
mobile websites nor native apps
provide an effective answer on
todays needs.
47. Why mobile first (1)
Mobile is harder to use
‣ Smaller screen
‣ Touch instead of keyboard and
mouse(pad)
‣ Slower internet connection
48. Why mobile first (2)
Mobile users have typically less
patience
‣ Because it’s harder to use
‣ Might be on the move
‣ Need that info to use it right now
49. Why mobile first (3)
Forces you to focus:
‣ No space for complexity
‣ No space for extra’s
‣ Focus on core features and simplicity
50. It’s easier to make a simple thing
more complex than to make a
complex thing more simple.
51. If you can support the mobile
web, you can support anything.
52. Our proces
1. Online strategy
2. Information architecture
3. Design
4. Front-end design
5. Development
54. Know the online strategy
3 basics:
‣ Target audience
‣ Goal of the client
‣ USP of the client
55. KISS: Keep it simple and
straightforward
‣ Top tasks (key services) in main menu
‣ Short and simple copy
‣ Throw away anything that isn’t needed
‣ White space is allowed
‣ Conclusion first, details later
56. “Don’t make me think” (1)
‣ At any point it should be clear how to
get closer to the wanted answer
‣ Extra click is way better than complex
navigation
57. “Don’t make me think” (2)
‣ 2 types of page: choice page and
action page
‣ Homepage is a choice page
60. Conclusion so far
‣ For content-driven websites, responsive
web design is the future
‣ Think mobile first
‣ KISS, focus on core tasks (starts with IA)
90. 1. The browser is our canvas
2. A static image doesn’t feel like a real page
3. Content organisation before design
4. Accessibility & appropriate hierarchy
91. 1. The browser is our canvas
2. A static image doesn’t feel like a real page
3. Content organisation before design
4. Accessibility & appropriate hierarchy
92. 1. The browser is our canvas
2. A static image doesn’t feel like a real page
3. Content organisation before design
4. Accessibility & appropriate
93. 1. The browser is our canvas
2. A static image doesn’t feel like a real page
3. Content organisation before design
4. Accessibility & appropriate hierarchy