Responsive web design generates an optimal viewing experience across different devices by using fluid, proportion-based grids and flexible images. Media queries allow different CSS styles based on device characteristics like browser width. Tricon Infotech focuses on building websites that work well on any device now and in the future through responsive design using HTML5, CSS3, and Foundation frameworks. They are located in Bangalore, India and can be contacted via phone or email.
This document compares JavaScript libraries JQuery, Mootools, and Rialto. JQuery is the smallest at 16-94KB and supports back button navigation and rich text editing. Mootools is similar in size at 4-74KB but lacks back button support and rich text editing. Rialto is the largest at 520KB and does not support back button navigation, rich text editing, or animation. The document also notes advantages of these libraries are their extensibility and ability to quickly build interactive applications, while a disadvantage is potential browser compatibility issues.
This document provides an introduction to Microsoft Silverlight, including what it is, common uses, and comparisons to other technologies. Silverlight allows developing cross-browser rich internet applications using XAML and .NET. It provides rich media capabilities and supports multiple platforms and browsers via an optional plug-in. While HTML5 has advantages of being lightweight and having wider browser support, Silverlight enables richer user interfaces and experiences similar to desktop applications.
This document discusses different types of websites including static, dynamic, content managed, e-commerce, and flash websites. It notes that static websites are the simplest form and don't use server-side processing, while dynamic websites rely on server-side scripting and databases. Content managed websites allow numerous contributors to add, edit, and remove content through a password protected interface. E-commerce websites can process online transactions like an online store. The document also discusses website content management systems and their features like templates, access control, and collaboration tools.
AngularJS is a structural framework for building dynamic web applications. It uses HTML as a template language and extends HTML's syntax to build application components clearly. Angular's data binding and dependency injection reduce the code needed. It works entirely in the browser, making it compatible with any server technology. AngularJS addresses HTML's limitations for dynamic views by allowing declarative programming rather than imperative DOM manipulation. It provides structure, organization, modularity and reusable components for building applications.
Seam is more than just another web framework - it is a complete application stack. It pulls together standard Java EE APIs like EJB3, JSF, JPA and Hibernate and makes them more accessible, functional and attractive. Seam provides a full solution for building an application from start to finish, unlike web frameworks that are only focused on the user interface layer. Choosing Seam means opting for an integrated platform rather than just a framework.
Slide deck from my session at the London Customer Company Tour 2012. More details can be found in the accompanying blog post at:
http://bobbuzzard.blogspot.co.uk/2013/05/mobile-web-apps-with-html5-and-jquery.html
This document discusses a HTML5 framework optimized for mobile devices. It allows cross-platform development for Android, iPhone, tablets and more. Key features include stunning UI controls, hundreds of plugins, and the ability to access device hardware through PhoneGap. Developers need knowledge of HTML/HTML5, JavaScript, jQuery and CSS. The framework offers documentation, reusable code, built-in themes and an online UI builder. While it allows building one app to run on multiple platforms, HTML5 apps may be slower than native apps and unstable at times on lower-end devices. Resources mentioned for support include forums, tutorials and emulators.
Uniface Lectures Webinar - Extending Applications for Mobile Uniface
The Uniface Lectures are an ongoing series of free monthly technical webinars that cover a wide range of useful topics. In this Lectures webinar on extending applications for mobile we cover the following topics:
• Development approaches for mobile
• Using native mobile features
• Demo & code walk-through
Full webinar video recording can be found on: youtube.com/unifacesme
Progressive Web Apps provide an installable, app-like experience on desktop and mobile that are built and delivered directly via the web. Learn about PWAs basics and its components and how people are slowing moving towards PWAs over Native applications. Your website is your application!
This document provides an overview of several topics for a seminar:
1) Responsive web design which uses CSS media queries to dynamically adjust a website for different devices like mobile, tablet and desktop.
2) Cross-browser compatibility and ensuring websites render correctly across different browsers through standards-compliant coding and validation.
3) The Firefox extension Firebug which allows editing, debugging and monitoring of CSS, HTML and JavaScript on web pages.
4) Popular payment gateways like PayPal and Authorize.Net that allow accepting payments through websites.
5) Content management systems that enable centralized publishing, editing and maintenance of website content.
This document discusses responsive web design (RWD), which is a process that creates a single website compatible across devices with different screen sizes and orientations. RWD uses a flexible layout, media queries, and viewport meta tags to dynamically change the layout depending on screen size. Common frameworks that help with RWD include Bootstrap, Foundation, and Semantic UI. Websites can be tested for responsiveness using tools like Responsivetest.net and Responsinator.com.
This document discusses responsive web design. It begins by defining responsive design as using HTML and CSS to automatically resize and reformat web pages to look good on different devices. It then explains why responsive design is necessary today due to the rise of mobile usage. The document outlines how to check if a site is responsive, the benefits of responsive design like improved user experience, and the major components used to build responsive sites like meta tags, CSS media queries, grid systems, and frameworks. It concludes that responsive design improves the user experience by avoiding unnecessary resizing or scrolling across devices.
The document discusses how in-app payments work and breaks the process down into modules, including collecting user details, a payment gateway module, a payment logic module, a notification module, and a success/error interface module. It proposes using a mobile payments library to speed up engineering of a payments engine and provides links for more information on PayPal's payment products and developer tech support.
Sahi is an open source tool for automating web application testing. It uses an easy to use recorder to create test scripts without needing XPaths or waits. Sahi scripts can be written in Sahi Script, Java, or Ruby. It handles AJAX applications and identifies objects without needing developer involvement. Sahi provides advantages over other tools like Selenium and QTP through its recorder, implicit waits, object identification, and ability to run tests across multiple browsers and machines.
Responsive web design allows a single template to be delivered across all devices by using media queries to detect the device. It allows for longer page loads but existing websites do not need rebuilding. Adaptive web design delivers separate templates for each device through server-side detection, allowing for faster page loads but requiring alterations to existing websites. CSS media queries and breakpoints are important techniques for responsive design, along with fluid grids, modifying box size, spacing, fonts and images based on screen width. Common patterns include revealing, transforming, dividing, reflowing, expanding and positioning content. Single page applications load all necessary code at once allowing speedy secondary page loads but can increase initial load time and complexity.
Silverlight 4 includes many new features to improve the developer experience, UI/UX support, capabilities for building business applications, and out-of-browser functionality. It provides enhanced developer tools in Visual Studio 2010 and Expression Blend 4, new controls, drag and drop support, and data binding improvements. Silverlight 4 also features improved printing support, WCF RIA Services, MEF support, and internationalization features for building business applications. Additionally, it allows trusted out-of-browser applications with access to local files, the webcam, and notifications.
THE BREAK-UP - A user interface love storyconnectwebex
Presentation “THE BREAK-UP - A user interface love story“ by Raphael Wegmueller, Damien Antipa and Alexandre Capt at CQCON2013 in Basel on 19 and 20 June 2013.
This document discusses challenges in mobile development and exploring the mobile web. It covers topics like mobile device categories, mobile knowledge, browsing experiences, and differences between mobile web sites, hybrid applications, and native applications. Graphic toolkits and debuggers/emulators are mentioned as helpful development tools. Benefits of each approach like cross-platform compatibility, installation experience, and monetization options are compared.
Responsive web design is a technique that allows web page layouts to adapt to different screen sizes and devices. It uses flexible grids, images, and CSS media queries to automatically adjust the page layout depending on whether users are on laptops, tablets, or mobile phones. This makes the website easily accessible to users regardless of what device they are using.
Web Applications Are Technically Awesome!MediaFront
A web application utilizes web technologies like HTML, CSS, and JavaScript to create an application experience within a browser. Web applications allow for separation of the application from its resources, only requesting needed data to work offline. This future proofs the application because the application and its resources can be altered separately. Technologies like HTML5, AngularJS, and smart views allow developers to build rich experiences across different devices by dynamically switching templates and views based on factors like device size and user type.
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.
Responsive web design & mobile web development - a technical and business app...Atos_Worldline
The document discusses responsive web design and mobile web development. It recommends creating a single page web application that is optimized for all devices as a long term goal. It also discusses challenges like different screen sizes, browsers, and touch vs mouse interactions across diverse devices. The document advocates adapting the web experience according to the device using responsive design principles.
DISCLAIMER: The views are entirely that of the author of the presentation and ESS does not associate itself with the content whatsoever. ESS cannot be held liable in anyway for any claims arising out of the presentation or any repercussions from partial/complete implementation of any of the ideas presented.
Need a ten minute overview of responsive web design? In this talk we'll talk about the problem responsive web design (RWD) is trying to solve, what RWD is, the basic implementation aspects of RWD and some of the latest developments and sources of information if you want to learn more about RWD.
Responsive UX - One size fits all @BigDesign conference #BigD12touchtitans
The document discusses responsive UX, which is designing websites and applications that adapt to different screen sizes and devices using fluid grids, media queries, and responsive images; it provides examples of how to implement responsive design principles through fluid grids, image scaling, and media queries to build sites that automatically adjust for smartphones, tablets, and other devices.
Smarter HATS web application that automatically respond according to the scre...Royal Cyber Inc.
Experience the art of our unique HATS Responsive Design development that adjust automatically to any resolution, making the system best fit for all the devices and platforms. Inquire more: http://bit.ly/1d0Gj2A
The document discusses responsive web design (RWD), which is an approach to building websites that dynamically adapt their layout to different screen sizes and devices. It covers the key features of RWD, including flexible grids, images, and using CSS3 media queries to detect screen sizes and orientations. The benefits of RWD are also summarized, such as improved performance, saving time and money. Popular RWD frameworks like Foundation and Bootstrap are also mentioned.
This tutorial will explain Responsive Website Designing.
Key Concepts: Responsive Web Design, Website Designing, Mobile is the Future, What is Responsive Web Designs?, Why do we need responsive web design?, Adoptive vs Responsive web designs, Key benefits of Responsive web designs, How does it work?, How you can implement Responsive Websites?, Frameworks, Demo
For more detail visit Tech Blog:
https://msatechnosoft.in/blog/
The document discusses building mobile websites with Joomla and mobile web development in general. It notes that mobile internet usage is growing rapidly and introduces some solutions for creating mobile-optimized websites using Joomla extensions like Mobile Joomla, Mobilebot, and WAFL. It also describes the OSMOBI service which uses transcoding techniques to mobilize existing Joomla and other CMS-driven sites without coding.
Uniface Lectures Webinar - Extending Applications for Mobile Uniface
The Uniface Lectures are an ongoing series of free monthly technical webinars that cover a wide range of useful topics. In this Lectures webinar on extending applications for mobile we cover the following topics:
• Development approaches for mobile
• Using native mobile features
• Demo & code walk-through
Full webinar video recording can be found on: youtube.com/unifacesme
Progressive Web Apps provide an installable, app-like experience on desktop and mobile that are built and delivered directly via the web. Learn about PWAs basics and its components and how people are slowing moving towards PWAs over Native applications. Your website is your application!
This document provides an overview of several topics for a seminar:
1) Responsive web design which uses CSS media queries to dynamically adjust a website for different devices like mobile, tablet and desktop.
2) Cross-browser compatibility and ensuring websites render correctly across different browsers through standards-compliant coding and validation.
3) The Firefox extension Firebug which allows editing, debugging and monitoring of CSS, HTML and JavaScript on web pages.
4) Popular payment gateways like PayPal and Authorize.Net that allow accepting payments through websites.
5) Content management systems that enable centralized publishing, editing and maintenance of website content.
This document discusses responsive web design (RWD), which is a process that creates a single website compatible across devices with different screen sizes and orientations. RWD uses a flexible layout, media queries, and viewport meta tags to dynamically change the layout depending on screen size. Common frameworks that help with RWD include Bootstrap, Foundation, and Semantic UI. Websites can be tested for responsiveness using tools like Responsivetest.net and Responsinator.com.
This document discusses responsive web design. It begins by defining responsive design as using HTML and CSS to automatically resize and reformat web pages to look good on different devices. It then explains why responsive design is necessary today due to the rise of mobile usage. The document outlines how to check if a site is responsive, the benefits of responsive design like improved user experience, and the major components used to build responsive sites like meta tags, CSS media queries, grid systems, and frameworks. It concludes that responsive design improves the user experience by avoiding unnecessary resizing or scrolling across devices.
The document discusses how in-app payments work and breaks the process down into modules, including collecting user details, a payment gateway module, a payment logic module, a notification module, and a success/error interface module. It proposes using a mobile payments library to speed up engineering of a payments engine and provides links for more information on PayPal's payment products and developer tech support.
Sahi is an open source tool for automating web application testing. It uses an easy to use recorder to create test scripts without needing XPaths or waits. Sahi scripts can be written in Sahi Script, Java, or Ruby. It handles AJAX applications and identifies objects without needing developer involvement. Sahi provides advantages over other tools like Selenium and QTP through its recorder, implicit waits, object identification, and ability to run tests across multiple browsers and machines.
Responsive web design allows a single template to be delivered across all devices by using media queries to detect the device. It allows for longer page loads but existing websites do not need rebuilding. Adaptive web design delivers separate templates for each device through server-side detection, allowing for faster page loads but requiring alterations to existing websites. CSS media queries and breakpoints are important techniques for responsive design, along with fluid grids, modifying box size, spacing, fonts and images based on screen width. Common patterns include revealing, transforming, dividing, reflowing, expanding and positioning content. Single page applications load all necessary code at once allowing speedy secondary page loads but can increase initial load time and complexity.
Silverlight 4 includes many new features to improve the developer experience, UI/UX support, capabilities for building business applications, and out-of-browser functionality. It provides enhanced developer tools in Visual Studio 2010 and Expression Blend 4, new controls, drag and drop support, and data binding improvements. Silverlight 4 also features improved printing support, WCF RIA Services, MEF support, and internationalization features for building business applications. Additionally, it allows trusted out-of-browser applications with access to local files, the webcam, and notifications.
THE BREAK-UP - A user interface love storyconnectwebex
Presentation “THE BREAK-UP - A user interface love story“ by Raphael Wegmueller, Damien Antipa and Alexandre Capt at CQCON2013 in Basel on 19 and 20 June 2013.
This document discusses challenges in mobile development and exploring the mobile web. It covers topics like mobile device categories, mobile knowledge, browsing experiences, and differences between mobile web sites, hybrid applications, and native applications. Graphic toolkits and debuggers/emulators are mentioned as helpful development tools. Benefits of each approach like cross-platform compatibility, installation experience, and monetization options are compared.
Responsive web design is a technique that allows web page layouts to adapt to different screen sizes and devices. It uses flexible grids, images, and CSS media queries to automatically adjust the page layout depending on whether users are on laptops, tablets, or mobile phones. This makes the website easily accessible to users regardless of what device they are using.
Web Applications Are Technically Awesome!MediaFront
A web application utilizes web technologies like HTML, CSS, and JavaScript to create an application experience within a browser. Web applications allow for separation of the application from its resources, only requesting needed data to work offline. This future proofs the application because the application and its resources can be altered separately. Technologies like HTML5, AngularJS, and smart views allow developers to build rich experiences across different devices by dynamically switching templates and views based on factors like device size and user type.
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.
Responsive web design & mobile web development - a technical and business app...Atos_Worldline
The document discusses responsive web design and mobile web development. It recommends creating a single page web application that is optimized for all devices as a long term goal. It also discusses challenges like different screen sizes, browsers, and touch vs mouse interactions across diverse devices. The document advocates adapting the web experience according to the device using responsive design principles.
DISCLAIMER: The views are entirely that of the author of the presentation and ESS does not associate itself with the content whatsoever. ESS cannot be held liable in anyway for any claims arising out of the presentation or any repercussions from partial/complete implementation of any of the ideas presented.
Need a ten minute overview of responsive web design? In this talk we'll talk about the problem responsive web design (RWD) is trying to solve, what RWD is, the basic implementation aspects of RWD and some of the latest developments and sources of information if you want to learn more about RWD.
Responsive UX - One size fits all @BigDesign conference #BigD12touchtitans
The document discusses responsive UX, which is designing websites and applications that adapt to different screen sizes and devices using fluid grids, media queries, and responsive images; it provides examples of how to implement responsive design principles through fluid grids, image scaling, and media queries to build sites that automatically adjust for smartphones, tablets, and other devices.
Smarter HATS web application that automatically respond according to the scre...Royal Cyber Inc.
Experience the art of our unique HATS Responsive Design development that adjust automatically to any resolution, making the system best fit for all the devices and platforms. Inquire more: http://bit.ly/1d0Gj2A
The document discusses responsive web design (RWD), which is an approach to building websites that dynamically adapt their layout to different screen sizes and devices. It covers the key features of RWD, including flexible grids, images, and using CSS3 media queries to detect screen sizes and orientations. The benefits of RWD are also summarized, such as improved performance, saving time and money. Popular RWD frameworks like Foundation and Bootstrap are also mentioned.
This tutorial will explain Responsive Website Designing.
Key Concepts: Responsive Web Design, Website Designing, Mobile is the Future, What is Responsive Web Designs?, Why do we need responsive web design?, Adoptive vs Responsive web designs, Key benefits of Responsive web designs, How does it work?, How you can implement Responsive Websites?, Frameworks, Demo
For more detail visit Tech Blog:
https://msatechnosoft.in/blog/
The document discusses building mobile websites with Joomla and mobile web development in general. It notes that mobile internet usage is growing rapidly and introduces some solutions for creating mobile-optimized websites using Joomla extensions like Mobile Joomla, Mobilebot, and WAFL. It also describes the OSMOBI service which uses transcoding techniques to mobilize existing Joomla and other CMS-driven sites without coding.
This document provides best practices for developing websites and applications for multiple screen sizes. It discusses challenges like varying device sizes and browsers. It recommends a mobile-first approach, exploiting device capabilities, optimizing images, and using techniques like responsive design with media queries or server-side delivery of customized content. Media queries allow attaching different stylesheets based on screen properties, while server-side delivery fully customizes content for each device. The document also provides tips for navigation, interactions, and structuring content adaptably across devices.
IBM Web Experience Factory is a tool that automates the creation of mobile web applications using standard technologies like HTML, CSS, and JavaScript. It generates native-looking UIs for smartphones and tablets. The tool's dynamic profiling feature allows building multi-channel applications from a single code base that can be tailored for different device types. Web Experience Factory also supports creating hybrid applications that combine web and native features through tools like PhoneGap.
Responsive design aims to provide optimal viewing experiences for websites across different devices by adapting the layout. It uses fluid layouts with relative sizing, media queries to apply different CSS styles based on screen size, and viewport meta tags to control layout on mobile. Ethan Marcotte first described the challenges of responsive design. Now all websites should be developed with responsive characteristics to accommodate varying screen sizes and input types.
Web technology is undergoing one of the biggest advancements; the proliferation of front-end JavaScript frameworks. From bettering user experience to improving performance and productivity, front-end frameworks are transforming web and mobile app development. How to choose a front-end framework for your application? The answer is a click away.
Cross platform mobile application architecture for enterpriseVenkat Alagarsamy
The document discusses cross-platform mobile application architecture for enterprises. It covers the need for enterprise mobile apps due to workforce mobility trends. It compares native, web, and hybrid approaches and recommends hybrid for supporting multiple platforms. Key elements of hybrid apps include device and screen agnosticism, offline storage, security, and access to device capabilities. Frameworks like Phonegap and technologies like HTML5, CSS, and JavaScript enable hybrid development.
Device aware web frameworks for better programmingSuntae Kim
To capitalize on the explosion of multi-device web access, companies need to unify their web-based properties for desktop, tablets and mobile and implement a holistic, One Web approach. When evaluating solutions that support One Web, it is important to select technologies that support single code-base, offer seamless device-based optimization and deliver fast load times.
This document discusses how to create a responsive website. It recommends starting with a mobile-first approach and using relative typography, a flexible grid, and flexible images and video. It also recommends using viewport settings, media queries, and compressing content to make the site responsive across different screens. The key aspects are a mobile-first strategy, relative sizing with em and percent units, a fluid grid layout, responsive images and video, and media queries to adapt the design at different breakpoints.
My React Next 2023 talk about React-DOM code , details about the rendering and updating circle, how react-dom detects changes and how everything gets updated.
with screenshots from the debugger travelling through the code.
This document discusses background operations in web applications including background sync, periodic background sync, and background fetch. Background sync allows sending data whenever the network is available, periodic background sync gives the feeling of constant connection to the server even when offline, and background fetch allows downloading content from the network without stopping when the network throttles or stops. These background operations help make the user experience less dependent on the network status.
The document discusses the new Permission API which provides a unified way for websites to query, request, and revoke user permissions and handle changes. It allows developers to know the permission status without asking, and be notified of changes. Some permissions like camera and accelerometer may not work the same way yet as it is still an experimental API. Links are provided for the specification, MDN documentation, a polyfill, and demo code.
The presentation discusses the evolution of browsers, JavaScript, and frameworks. It argues that while frameworks provide useful features like data binding and routing, they can also lock developers into certain approaches. Reinventing the wheel with vanilla JavaScript is possible using browser APIs and standards like custom elements, attributes, events, and the History API. Programming directly with vanilla JavaScript ensures familiarity with underlying capabilities and flexibility to choose the best tools.
Web workers allow JavaScript to run in background threads to optimize performance. A worker runs in a separate global context and can communicate with the main thread via messaging. A shared worker can serve multiple browsing contexts and uses ports to send and receive messages between contexts. Workers parallelize work to speed up tasks while shared workers facilitate sharing state across contexts by using a single worker instance.
Ran Wahle discusses using micro frontends to integrate legacy code into a modern single page application (SPA) in a peaceful way. A demo is shown integrating three sample applications - one using jQuery, one using Angular 6, and one using Angular 5 and Firebase. Micro frontends allow each application to have its own URL routing and inner routing while reusing backend services. Wrapping applications as custom elements is also discussed as an alternative to iframes for less isolation while still maintaining independence. The talk concludes that micro frontends can help extend legacy code and blend applications together to achieve "world peace" between new and old approaches.
The document discusses async/await in JavaScript. It explains that async/await allows writing asynchronous code that looks synchronous by using the await keyword to "turn" a promise into its resolved value. Async functions always return promises, even though code below await reads synchronously. Async/await simplifies code by avoiding callback nesting and is supported in modern browsers.
The document discusses state management in web applications using Redux and MobX. It presents a call center management app to demonstrate both approaches. Redux uses actions, reducers, and middleware for state management with a defined data flow. MobX uses decorators to automatically manage state with less code but less testability. Best practices include connecting only smart components to the store and using the store for reusable data. While Redux is more complex and testable, MobX is more automatic but "magical".
The document discusses Angular 2.0 change detection. It describes how Angular 2.0 change detection is more efficient and predictable compared to Angular 1.x by using a component-based approach rather than a graph. Each component has its own change detector that is generated at compile time. Change detection occurs top-down via the change detection tree. The document also discusses strategies like OnPush, immutable objects, observables, and manually controlling change detection.
The document discusses various asynchronous patterns in JavaScript, including using events, callbacks with Socket.IO, promises, observables, iterators, generators, and async/await. It provides code examples for promise creation, using the Fetch API, ES2015 iterators, and TypeScript's async/await syntax. The presentation aims to demonstrate asynchronous patterns for event handling, promises, iterators/generators, and async/await in TypeScript and Angular 2.
AngularJs 2.0 introduces components as the fundamental building blocks, replacing directives. The presentation covers getting started with AngularJs 2.0, including dependencies, configuration, components, data binding, services, routing and migration from Angular 1. It emphasizes that Angular 2 is a rewrite built on newer standards to improve performance and reduce opinionation. Migration involves componentizing the application and using an upgrade adapter to support a hybrid Angular 1 and 2 app.
The document summarizes a presentation about using async/await to write asynchronous JavaScript code in a synchronous style. It begins with an introduction to promises as the standard pattern for asynchronous programming. It then demonstrates how async/await allows writing asynchronous code that looks synchronous using async functions and the await keyword. Under the hood, async/await uses generators produced by the TypeScript compiler. The presentation includes code examples and demos of geolocation and reverse geocoding using promises and async/await. It concludes with additional resources for learning more about iterators, generators, and async/await.
Angular 2.0 introduces significant changes from Angular 1.x including a new component-based architecture, use of TypeScript for static typing, and improved performance. The document discusses how to prepare Angular 1.x applications for migration by refactoring into components and using TypeScript. It also provides an overview of key differences in Angular 2.0 like bootstrapping, data binding, dependency injection and services.
6. Why Not?
Redundant elements and code downloaded to the client
Redundant data may be downloaded
Sometimes mobile pages need to look entirely different
8. Ways to do it
Screens for each device type
The same screen, looks different for each device type
9. Ways to do it (contd.)
Screen for each device Same screen, looks different
On server side, parse user agent Change styling according to device properties
Direct the user to another URL / Create another screen Relate only to device properties
Client side only
Pros Pros
More organized Less screens to maintain
Less elements to render No server side code
17. Viewport width related
font-size: 1vw; //1% of viewport width
font-size: 1vh; //1% of viewport height
font-size: 1vmin; //1% of the smaller dimension
font-size: 1vmax; //1% of the larger dimension
21. Bootstrap
CSS & Javascript library
Mobile first design
Built in media queries
Declarative and programmatic use of plugins
22. Bootstrap terminology
xs – Exrta small (Phones < 768px)
sm – Small Medium (Tablets, from 768px to 992px)
md – Medium (992px to 1200px)
lg – Large ( > 1200px)
23. Bootstrap visibility classes (from getBootstrap.com)
Extra small
devicesPhones
(<768px)
Small
devicesTablets
(≥768px)
Medium
devicesDesktop
s (≥992px)
Large
devicesDesktop
s (≥1200px)
.visible-xs-* Visible Hidden Hidden Hidden
.visible-sm-* Hidden Visible Hidden Hidden
.visible-md-* Hidden Hidden Visible Hidden
.visible-lg-* Hidden Hidden Hidden Visible
.hidden-xs Hidden Visible Visible Visible
.hidden-sm Visible Hidden Visible Visible
.hidden-md Visible Visible Hidden Visible
.hidden-lg Visible Visible Visible Hidden
33. We’ve started with an unresponsive app
Gradually added styles made it more responsive
Using HTML standards we can make our pages responsive
The same HTML & CSS can serve multiple device types
Our app still needs a designer’s touch
Well… I am not a UI guy
So…