The document discusses responsive web design and developing for multiple devices. It recommends creating a single responsive website that adapts to different screens through techniques like fluid grids, flexible images, and media queries. It also suggests considering hybrid approaches that incorporate both web and native capabilities to deliver high-quality experiences across all devices.
Progressive enhancement is still an important approach for building responsive websites and web applications. While JavaScript can now be assumed to be widely available, progressive enhancement avoids single points of failure and improves performance by loading critical content first before non-essential enhancements. The distinction between websites and applications is also blurred, so progressive techniques remain applicable to most digital experiences on the web.
This document discusses various user experience (UX) patterns and antipatterns for multiplatform mobile app design. It begins with definitions of UX and provides overviews of common mobile navigation patterns like side drawers and tab menus. The document then covers antipatterns to avoid such as splash screens, forcing registration, and excessive confirmation messages. It also discusses dark patterns designed to mislead users. Throughout, it provides examples and recommendations for implementing positive patterns and avoiding antipatterns to create a good user experience.
Responsive web design involves creating layouts that adapt to different screen sizes using flexible grids and media queries. It allows for a device-agnostic approach and is easier to build than separate mobile sites. Key aspects of responsive design include planning with a mobile-first approach, prototyping, using consistent breakpoints based on content, usability testing, writing for different screens, designing visually hierarchical layouts, and addressing images and media. Testing is important throughout the process. While responsive design is a good base, other solutions like responsive or native apps may still be needed, and the job requires ongoing review.
The document discusses responsive web design and strategies for creating websites that adapt to different screen sizes. It recommends taking a mobile-first approach, using fluid layouts and media queries to make content responsive. Key tips include starting small and resizing the browser, using Chrome's device mode to emulate different devices, and the matchMedia API to bind JavaScript to breakpoints. The overall goal is to provide an optimal viewing experience across all devices.
A presentation about the Future of the Web at the Cold Front conference in Copenhagen, Denmark, Sep 1 2016.
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 provides a history of the development of the web from 1991 to the present. It discusses technologies like HTML, HTTP, XMLHttpRequest, AJAX, and mobile web development. It then introduces progressive web apps, which are web applications that are reliable, fast and engaging like native apps through the use of technologies like service workers, web app manifests and push notifications. Examples are given of companies like Flipkart that have seen success adopting progressive web apps.
Responsive web design allows a single website to be accessed from any device by dynamically adjusting the layout depending on screen size. The content remains the same across devices but is formatted appropriately for each screen width through techniques like adjusting column numbers and widths. Designing first for mobile forces focus on essential content and ensures parity across devices. Examples demonstrate how navigation, images and text restructure seamlessly for an optimized experience on any device.
You can improve how well your website works and looks across different devices using responsive web design techniques. But did you know you can also improve access for all users, including those with disabilities, by applying responsive techniques? Learn how.
The document discusses responsive web design and compares it to other approaches like adaptive web design. It addresses some myths around responsive design, including that every website should be responsive, that it hurts performance, and that it limits creativity. It also discusses technical aspects like media queries and their uses beyond mobile screens.
The document discusses jQTouch, a plugin for jQuery that allows developers to build mobile web apps with HTML, CSS, and JavaScript. It works by turning regular web pages into touch-friendly "apps" that can be added to a mobile device's home screen. Key points covered include: - jQTouch uses jQuery and adds iPhone-style UI elements and themes - It supports animations between "pages" and touch events - Combined with PhoneGap, web apps built with jQTouch can be wrapped into native mobile apps and distributed through app stores - The presentation demonstrates jQTouch's capabilities and provides information on getting started and further resources
This document contains the transcript of a presentation by Chris Heilmann on web development. Some of the key points discussed include: - The benefits of progressive enhancement and using HTML, CSS, and JavaScript together to build robust and accessible websites. - How limitations in early design can foster creativity. - The importance of error handling and defensive coding practices. - Embracing new technologies like Service Workers and Manifests to build Progressive Web Apps. - Rethinking the idea that JavaScript is unreliable and should not be depended on, as modern browsers have made it a capable tool.
// talk given at WordCamp Chicago 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 such as icon fonts, svg, and other helpful tips.
This document provides guidance on how to build effective mobile web apps. It discusses understanding the mobile landscape and user needs, designing for a mobile-first approach, leveraging HTML5 features, optimizing for touch interfaces, and using technologies like CSS3, JavaScript, and device APIs. The key recommendations are to focus on the most common user tasks, reduce content, and make all functionality accessible within 3 taps or clicks.
The document discusses progressive web apps (PWAs) and outlines key considerations for creating a PWA. It addresses questions around what a PWA is, how to make a website feel like an app, offline functionality, push notifications, and creating a roadmap. Examples from companies that implemented PWAs successfully are provided. The conclusion recommends developing a progressive roadmap that starts with baseline PWA features and builds out functionality over time based on priorities and initiatives.
“If Tetris has taught me anything, it’s that errors pile up and accomplishments disappear” is a common quote and it seems we’re living this to its full extend as web developers. We fail to celebrate the successes we have and the tools that are at our disposal but we’re never short of finding reasons why things don’t work. We also tend to pile on technology on technology to solve problems that may actually not exist and thus clog up the web. In this talk Chris Heilmann wants to remind us what we achieved and how we should celebrate it and how we should stop trying to solve problems that are simply beyond our control.
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.
「人」と「食」のしあわせな関係性について探究するクリエイティブでダイナミックでラディカルな若者の集まり、「スローフードユースネットワーク」。その日本チームの活動内容と今後の野望についてご紹介いたします。
In response to the Yale School of Architecture Symposium, Is Drawing Dead?, we present sketches, illustrations, and renderings by each member of our studio to show that drawing is not dead!
This presentation will introduce a system of new personas, places, systems, processes, tools, environments, and hearts for cooking in the Inclusively Creative city. These concepts and practices are inspired by the idea and theories of Pattern Language. Cooking, though widely conceived as either a household chore or a professional skill, is the simplest form of design that many of us go through on a daily basis. It is a creative process that requires abstract skills including generating ideas and solving problems. It may seem a highly complex set of skills, but many of us are able to overcome the difficulty with the process driven by hunger. This paper will explore the application of theories by Christopher Alexander into the field of cooking. We will especially take a close look at his principles described in his book The Production of Houses, including the idea of the Architect-Builder and the builder’s yard.
This study evaluated 36 cases of traumatic telecanthus (abnormal widening of the distance between the eyes) resulting from naso-orbito-ethmoid fractures that were treated primarily with either direct or indirect canthopexy. Direct canthopexy resulted in a smaller intercanthal distance and less relapse compared to indirect canthopexy. Early primary treatment within 2 weeks led to fewer cases of epiphora (watery eyes) or dacryocystitis (blocked tear duct) compared to later treatment. The study concludes that traumatic telecanthus should receive early primary treatment to achieve the best aesthetic and functional results.
伊作太一が掲げる、人間らしく創造的に生きるための、新しいかたちの料理について。
This presentation will explore the advantages of a kitchen setting as a place to enhance collaborative learning and design. We will then introduce a special persona present in such a collaborative cooking session – the Kitchen Captain – who enhances communication and ideas among the participants while giving cooking support to whoever might need it. We will introduce her traits as a pattern language. These concepts were all mined out from actual experiences of collaborative cooking – CoCooking – and were derived from a broader persona called the Generator.
冷蔵庫の中身から発想する日常的な創造行為を支援する料理のしくみについて。
This document discusses the management of complications from improperly treated mandibular fractures. It begins with an introduction on mandibular fractures and challenges in management. Key points include evaluating patients, analyzing initial unsatisfactory results due to errors or poor technique, and surgical considerations for reoperation in cases of non-union, mal-union/malocclusion, condylar fractures, and facial asymmetry. Reoperation techniques aim to achieve adequate reduction, fixation, bone contact and occlusion. Careful preoperative planning including imaging and models can help address post-traumatic mandibular deformities.
The document discusses wound healing in the maxillofacial region. It begins with an introduction to wound healing processes and the layers of soft tissue in the maxillofacial region, including skin, muscle, cartilage, nerve and mucosa. It then covers soft tissue reactions to trauma, the phases of healing for different tissue types, and factors that can affect wound healing such as infection, ischemia and medication. Improper healing can lead to complications like dehiscence or scarring. The conclusion emphasizes the importance of understanding wound healing to optimize outcomes after facial injuries.
This document provides an overview of maxillofacial bone biology and healing. It discusses the embryology and development of craniofacial bones, their structure and chemical composition, and biomechanical properties. Primary mechanisms of bone fracture and healing are described, including primary healing through contact or a small gap, and secondary healing involving callus formation. Complications of bone healing like non-union and malunion are also covered. The document concludes with sections on metals and implant surfaces, and potential future uses of biodegradable fixation materials.
Maxillofacial trauma requires aggressive airway management and preliminary care. The document outlines the steps for preliminary care which include: 1) Initial assessment of the patient using ABCDE to evaluate airway, breathing, circulation, disability and exposure. 2) Securing the airway through basic maneuvers like jaw thrust or advanced techniques like endotracheal intubation if needed. 3) Assessing breathing and managing thoracic injuries. 4) Controlling hemorrhage through circulation management and fluid resuscitation to restore perfusion. 5) Conducting a full secondary survey to identify all injuries.
1. The document discusses negative pressure wound therapy (NPWT), including its history, mechanisms of action, clinical applications, and future perspectives. 2. NPWT uses subatmospheric pressure to promote wound healing through mechanisms like hemostasis, modulation of inflammation, angiogenesis, and granulation tissue formation. 3. Studies show NPWT can effectively treat wounds in complex areas like the head and neck region, and may help close submandibular fistulas. However, wounds with pockets or deep shapes are more prone to infection with NPWT.
The document discusses various surgical approaches for the facial skeleton, including extraoral and intraoral incisions. It covers key principles for placing incisions such as following natural lines and avoiding vital structures. Specific approaches are described for the mandible, condyle, orbit, maxilla, and nasal skeleton. Factors to consider for any facial incision include scar visibility, underlying anatomy, and adequate surgical access. Both open and endoscopic techniques are presented.
The document discusses various graft materials that can be used for head and neck reconstruction. It covers bone grafts, cartilage grafts, muscle grafts, skin grafts, nerve grafts, vessel grafts, fat grafts, and alloplastic graft materials. For each type of graft, it discusses principles of harvesting and placement, as well as outcomes. Regional sites are described for harvesting bone grafts. Principles of skin graft healing and nerve repair techniques are also summarized. Common alloplastic graft materials discussed include silicone, expanded polytetrafluoroethylene, and high-density polyethylene.
This document outlines Advanced Trauma Life Support (ATLS) guidelines. It covers the initial assessment and management of trauma patients, including the primary and secondary surveys, as well as specific treatments for injuries like airway management, shock, head trauma, spinal trauma, thoracic trauma, abdominal trauma, burns, pediatric trauma, and geriatric trauma. It emphasizes the need for a systematic approach to rapidly triage and stabilize injured patients before transferring them to definitive care facilities.
Presented June 8, 2012 (Online) at the 'Access by Touch: Delivering Library Services Through Mobile Technologies' conference sponsored by Amigos Library Services. Description: By the end of 2012, it is expected that more than 80% of the world’s population will have access to a smartphone. Your library users will assume that your library can be accessible from anywhere, at any time, and on any device. Now is the time to be ready! During this webinar, you will: - learn what a mobile framework is. - acquire best practices in mobile Web development. - understand the various technologies (HTML, CSS, JavaScript) and how they work together to build mobile Web apps. - recognize the differences between native and web apps. - have an opportunity to continue to work with Chad after the webinar to demonstrate what you learned. - gain access after the webinar to a free Web server so you can see your mobile Web app live.
Slides from a presentation I gave at these conferences: — Big Design — Front Porch — Thunder Plains — Web Afternoon I co-presented at Big Design with Matt Baxter. http://twitter.com/mbxtr
This document discusses hybrid mobile app development. It defines hybrid apps as combining the best of mobile web apps and native apps by developing basic features with HTML, CSS, and JavaScript and leveraging native APIs for more advanced features. This allows for quicker development and updates across platforms while still accessing device-level capabilities. The document outlines several techniques hybrid apps can use such as URL modification and interception to trigger native functionality from web views and pass data between web and native components. It promotes choosing the right development approach for each feature rather than relying solely on web or native.
According to the International Telecommunication Union, at the end of 2011 there were more than 1 billion mobile‐broadband subscriptions worldwide! With more of your library users using mobile devices to access information they will assume that your library can be available from anywhere, at any time, and on most any device. Now is the time to be ready for this demand. In this webinar: - Explore some innovative library mobile website designs and see how they were built. - Understand how HTML, CSS, and JavaScript work together to build mobile websites. - Learn what a mobile framework is and why they are used. - Provide some existing mobile services/apps that can be included in library-created mobile websites. - Acquire best practices in mobile Web development from start to finish.
This document discusses the state of mobile UX and challenges in choosing a development approach. It outlines the options of native, web, and responsive design. Native apps offer rich features but require high costs and platform fragmentation. Web apps have broad reach but limited functionality. Responsive design provides continuity across devices but not all content is equally suited. The key is understanding user needs and balancing capabilities with costs for the optimal strategy.
This document discusses the state of mobile UX and challenges in choosing a development approach. It outlines the options of native apps, mobile web, and responsive design. Native apps provide the best experience but are more expensive, while mobile web has broader reach but limited features. Responsive design aims for continuity across devices but may not be optimal for all situations. The document emphasizes understanding user needs and having a clear strategy to determine the best approach for each use case and business goals.
This document discusses how to create mobile apps that feel native using only web technologies. It covers supporting features in Mobile Safari like local storage, CSS3 features, and geolocation. It recommends using web technologies over native due to quicker iteration times. Specific techniques covered include detecting browser type, adding home screen icons, startup images, going full screen, and viewport settings. The document also discusses frameworks like jQuery Mobile but notes native DOM APIs may be sufficient. It covers input features, touch vs click, animations, locking orientation, and performance tips. It acknowledges limitations of Android and webOS and recommends testing on actual devices. Finally, it discusses hybrid mobile frameworks like PhoneGap and Titanium that allow developing for multiple platforms using one code
The document discusses pushing the boundaries of user experience with Drupal. It talks about using responsive design and progressive enhancement to build websites that automatically adapt to different screen sizes like desktop, tablet, and mobile. Responsive design uses CSS media queries and a fluid, data-driven approach to layouts. This allows a single website to effectively serve users on any device. The document recommends using responsive frameworks like Omega or Mojo themes for Drupal, and discusses building custom "UX modules" to enhance the user experience for different devices.
A presentation I gave at D2WC on workflow for creating an experience that spans mobile web to mobile app.
An overview of web development essentials that will help you as a user experience designer to not only understand how to integrate designs with development components, but also to learn some tips on interacting effectively with developers.