Presented at Mobilism.nl
Device diversity is about to get an order of magnitude worse. SmartTVs are hitting the market in mass this year. Sony, LG, Vizio, and Samsung are all shipping televisions with Google TV built in.
And if the rumors that Apple will release a TV this year are true, 2012 will turn out to be the year web developers start to tackle the glass screen hanging on our walls.
Why should web developers focused on mobile learn about the web on TVs? Because TVs represent the next challenge in device proliferation. They share common characteristics with their smaller brethren. They create new challenges and opportunities we haven't encountered yet. And most importantly, learning how to build for TVs helps inform our practices of building for mobile devices.
- Melinda Lini and Felipe Kaufmann strive to make users' lives easier through digital tools.
- They discuss the rise of mobile usage and the need for responsive web design to adapt content for various screen sizes.
- The key principles of responsive design are to use a fluid grid system, media queries for breakpoints, and progressive enhancement.
This document discusses designing websites for mobility. It provides an overview of mobile web usage statistics and trends. It also covers various design considerations for mobile websites such as responsive design, progressive enhancement, and performance optimization techniques like image resizing and testing on actual devices. The document promotes a mobile-first approach to design and outlines Stanford's mobile aware web project.
Mobile Web vs. Native Apps | Design4MobileJason Grigsby
This document provides an overview of a presentation on native mobile apps versus mobile web apps. It includes slides on why developers were fighting over the two approaches, Apple's announcement allowing third-party apps on the iPhone, and the surprise success of the iPhone App Store. It also discusses factors that contributed to the App Store's success like its openness, revenue split, and fewer restrictions compared to mobile carriers. The document debates questions around whether apps create platform lock-in, if app stores are essential to a platform's success, and challenges of developing for multiple mobile platforms. It suggests that HTML5 and WebKit may become the dominant mobile platform.
The document discusses responsive, adaptive, and mobile web design. It provides an overview of the differences between responsive and adaptive approaches. It notes that context is changing as mobile usage increases and discusses tools and techniques for liquid, responsive design including visual frameworks, prototyping tools, and testing on real devices. The document recommends embracing this changing context by measuring user behavior across devices and taking a different approach to data analysis and content delivery.
Three part series: Designing for multiple devices - GA, London, 20 Jan 2014Anna Dahlström
Slides from my three-part series Designing for Multiple Devices class run on the 20th of January with General Assembly in London.
The rise in mobiles and tablets have not only changed the way we consume and interact with content, but also the way we design and what we base our design approach on.
This series of classes will cover how user expectations as well as behaviour and consumption patterns have shifted—and what that means for designing products that will be used on multiple devices. Coming out of these classes, you'll be equipped with the essential principles and tools to tackle the multiple device jungle.
Pokemon Woe: A Botched Rollout or AR Growing Pains?Doug MacFaddin
Pokemon Go launched last month to extreme popularity, but a recent software update and a crippling glitch have led some people to turn against the game.
Managing State in Single Page WebApps with Ember.jsMark Mansour
This document provides an overview of managing state in a single page application with Ember.js. It discusses how Ember uses models, controllers and bindings to connect user interfaces and keep data in sync across components. Key aspects covered include Ember objects, computed properties, observers, controllers, bindings and the Ember run loop which handles updating the DOM efficiently.
- Melinda Lini and Felipe Kaufmann strive to make users' lives easier through digital tools.
- They discuss the rise of mobile usage and the need for responsive web design to adapt content for various screen sizes.
- The key principles of responsive design are to use a fluid grid system, media queries for breakpoints, and progressive enhancement.
This document discusses designing websites for mobility. It provides an overview of mobile web usage statistics and trends. It also covers various design considerations for mobile websites such as responsive design, progressive enhancement, and performance optimization techniques like image resizing and testing on actual devices. The document promotes a mobile-first approach to design and outlines Stanford's mobile aware web project.
Mobile Web vs. Native Apps | Design4MobileJason Grigsby
This document provides an overview of a presentation on native mobile apps versus mobile web apps. It includes slides on why developers were fighting over the two approaches, Apple's announcement allowing third-party apps on the iPhone, and the surprise success of the iPhone App Store. It also discusses factors that contributed to the App Store's success like its openness, revenue split, and fewer restrictions compared to mobile carriers. The document debates questions around whether apps create platform lock-in, if app stores are essential to a platform's success, and challenges of developing for multiple mobile platforms. It suggests that HTML5 and WebKit may become the dominant mobile platform.
The document discusses responsive, adaptive, and mobile web design. It provides an overview of the differences between responsive and adaptive approaches. It notes that context is changing as mobile usage increases and discusses tools and techniques for liquid, responsive design including visual frameworks, prototyping tools, and testing on real devices. The document recommends embracing this changing context by measuring user behavior across devices and taking a different approach to data analysis and content delivery.
Three part series: Designing for multiple devices - GA, London, 20 Jan 2014Anna Dahlström
Slides from my three-part series Designing for Multiple Devices class run on the 20th of January with General Assembly in London.
The rise in mobiles and tablets have not only changed the way we consume and interact with content, but also the way we design and what we base our design approach on.
This series of classes will cover how user expectations as well as behaviour and consumption patterns have shifted—and what that means for designing products that will be used on multiple devices. Coming out of these classes, you'll be equipped with the essential principles and tools to tackle the multiple device jungle.
Pokemon Woe: A Botched Rollout or AR Growing Pains?Doug MacFaddin
Pokemon Go launched last month to extreme popularity, but a recent software update and a crippling glitch have led some people to turn against the game.
Managing State in Single Page WebApps with Ember.jsMark Mansour
This document provides an overview of managing state in a single page application with Ember.js. It discusses how Ember uses models, controllers and bindings to connect user interfaces and keep data in sync across components. Key aspects covered include Ember objects, computed properties, observers, controllers, bindings and the Ember run loop which handles updating the DOM efficiently.
Adapting to Input — Smashing Conference NYCJason Grigsby
Input is constantly evolving and expanding beyond traditional keyboard and mouse. The document discusses 7 principles for adapting web design to different inputs:
1. Design for the largest target by default.
2. Design for modes of interaction instead of specific inputs.
3. Make designs accessible to all inputs.
4. Support multiple concurrent inputs.
5. Abstract baseline inputs like tap, click, and point.
6. Progressively enhance with new inputs like gestures and sensors.
7. Include different inputs in testing plans.
The key message is that input cannot be detected, is a continuum, and is always changing. Web design needs to be adaptable and not assume certain inputs based on device properties.
This document summarizes a student project investigating the development of smartphones. It outlines the history of mobile phones from 1946 to recent iPhone and Android models. It describes popular smartphone brands and operating systems. Features, advantages, and drawbacks of smartphones are compared to older mobile phones. The document also describes entertainment apps, includes screenshots, and analyzes survey results on smartphone usage. In conclusion, smartphones are found to provide more functions than older phones, with price and features being primary considerations for consumers.
The document discusses the hype around HTML5 and examines what it actually is and how well browsers support its features. While HTML5 enables rich interactive experiences, full support across devices is still limited. Mobile browsers in particular lag desktop browsers in HTML5 support. The document advocates that HTML5 is an opportunity but is not a magic solution, and developers still face challenges like fragmentation.
What lies ahead of HTML5_Ooop Munich 2013_Krzysztof SzafranekWooga
The document discusses the future of HTML5 and the debate between developing mobile applications using native apps vs. web technologies like HTML5. It notes that while HTML5 was not ready for advanced mobile games in 2012 due to performance and feature limitations, the mobile web is catching up thanks to new web APIs and standards. Within 10 years, the mobile web may be comparable to native apps, though app stores' long term role is uncertain. The document also outlines the tradeoffs between native, web, and hybrid app development approaches.
The document discusses tools and strategies for mobile journalism using smartphones. It provides examples of video and audio equipment that can enhance smartphone reporting abilities, such as external microphones and rigs to stabilize video. It also lists video, audio, editing, and storage apps that journalists can use to capture, process and share multimedia content on the go. Tips are provided for organizing apps and gear, avoiding disruptions, and improving video quality.
Fairfax Sydney #mojo #mojocon Feb 2017 Meetup - 360 video production basicsJamie Andrei
Fairfax Sydney #mojo #mojocon Feb 2017 Meetup - 360 video production basics
An introduction to 360 video / VR basics, introducting the concept, several approach & technologies, through to 2x key 360 social platforms (fish where the fish are), through to a basic workflow & some hands on Google Cardboard demos.
This document summarizes the latest mobile news from March 2012. It discusses the growth of smartphones and their increasing market share over "dumb phones". It provides market share numbers for Android, iOS, and other platforms. It also summarizes new products like the new iPad and Samsung Galaxy S3, updates to platforms like Android and Windows Phone, and other miscellaneous mobile news stories from March 2012.
This document provides an overview of emerging technologies and trends from 2005-2010 as presented by Stephen P. Anderson and Jeremy Johnson from Bright Corner. Key points discussed include the future of the web, user experience design, visioning techniques, current and future technologies such as wireless power, augmented reality, mobile apps, touch interfaces, and more. Various concepts, products and emerging trends are illustrated through links to videos and articles.
PhoneGap allows developers to build mobile apps using standard web technologies like HTML, CSS, and JavaScript. It works by embedding a webview component within a native container, and provides a bridge for JavaScript to access some device APIs. PhoneGap has grown a large community and supports many mobile platforms. While it allows cross-platform development, apps are still packaged natively and some limitations remain. The future roadmap includes improved plugin support and new features like web sockets and background services to enhance the capabilities of hybrid mobile apps.
This document discusses how to optimize Android apps for Honeycomb and later versions by using fragments. It notes that fragments were introduced in Android 3.0 to help structure apps for both phones and tablets. While only available on newer versions initially, the support package backports fragments to older devices. The document outlines problems developers face with fragmentation and how to address it using fragments, event listener interfaces, and frame layouts to dynamically add fragments. It provides statistics on device platforms and screen sizes and recommends sample code and resources for learning more.
The document discusses the state of the smartphone market in 2008 and provides guidance on developing applications for various smartphone platforms. It notes that in 2008, Nokia, RIM, and Samsung dominated the global smartphone market, with Apple growing 245%. It then provides an overview of tools and considerations for developing apps for platforms like iPhone, Android, Blackberry, and mobile Flash, noting that HTML, CSS, and JavaScript can be used to develop for many platforms. Challenges and differences between platforms like screen sizes, SDKs, and programming languages are outlined.
Andrew gave a presentation on GNOME, Linux mobile stacks, and engaging with open source communities. He discussed the growth of the mobile market and importance of open platforms. GNOME's role in providing tools for developers on mobile was covered. Finally, he compared GNOME and Qt frameworks, emphasizing the need for fair evaluation of open source options. Developers should find accessible SDKs to get involved in building for open platforms.
From custom hardware to Android TV and beyond. A brief introduction on how to develop apps for Android TV using React Native.
Talk at Reat Native London Meetup - July 2019: https://youtu.be/wm56XCtMw40
Your boss has an iPhone, so of course he wants an app. But does an app really make business sense? Or is a responsive design website enough?
And with hundreds of thousands of apps out there, what will make people choose and use yours? What makes a good mobile user interface? And how can you make sure your company actually delivers one?
Responsive design might make sense if you've got a content driven website. But how should your web team work together when every web page they are making needs to work at any width and resolution? And can you get the content under control to make pages that really make sense on small screens and big ones?
- Android is an open source operating system developed by Google and the Open Handset Alliance. It was originally developed by Android Inc which was acquired by Google in 2005.
- The first Android phone was launched in 2008. Since then Android has seen many updates and versions from 1.0 to the current 10.0.
- Android is based on a modified Linux kernel and allows developers to write managed code in Java. It uses Dalvik as its virtual machine instead of the standard Java virtual machine.
- The Android software stack consists of applications, an application framework, libraries and the Linux kernel. Key frameworks include activity manager, notification manager, and window manager.
- Android provides features like multi-touch, cameras,
PhoneGap allows developers to build native mobile apps using web technologies like HTML, CSS, and JavaScript. It works by wrapping web content in a native container on each mobile platform, allowing developers to write code once and deploy it across iOS, Android, BlackBerry, and other platforms. PhoneGap uses a plugin architecture that enables accessing native device APIs like the camera, contacts, and geolocation from JavaScript. It supports many mobile browsers and platforms, while providing tools for compiling, debugging, and deploying apps.
Mobile devices are increasingly popular while PCs decline. Smartphones now outsell PCs and their screens, processors, and networks continue advancing. Mobile networks are transitioning to high-speed 4G LTE. Worldwide, Android and iOS dominate the smartphone market. Content providers like the BBC are developing mobile strategies including responsive websites and apps targeting various mobile platforms and form factors.
HTML5 is the Future of Mobile, PhoneGap Takes You There Todaydavyjones
PhoneGap allows developers to build mobile apps using HTML, CSS and JavaScript instead of relying on platform-specific languages like Objective-C or Java. The document discusses PhoneGap's capabilities and advantages, including writing apps once that run on multiple platforms, using web technologies that are widely known by developers, and leveraging growing browser capabilities on mobile through HTML5. It also outlines PhoneGap's APIs, tools, libraries, and community to help developers get started building cross-platform mobile apps.
Presented at Web Directions Code, Melbourne
If you have a website—particularly one that generates revenue for your organization—you need a Progressive Web App. So where do you begin? How do you decide which features of a Progressive Web App make sense for your users? What tools can make the process easier (or harder)? In this practical session, Jason will guide you through the key design decisions you’ll need to make about your Progressive Web App and how those decisions impact the scope of your project. He'll also teach you how to avoid common pitfalls and help you take full advantage of Progressive Web App technology.
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.
Adapting to Input — Smashing Conference NYCJason Grigsby
Input is constantly evolving and expanding beyond traditional keyboard and mouse. The document discusses 7 principles for adapting web design to different inputs:
1. Design for the largest target by default.
2. Design for modes of interaction instead of specific inputs.
3. Make designs accessible to all inputs.
4. Support multiple concurrent inputs.
5. Abstract baseline inputs like tap, click, and point.
6. Progressively enhance with new inputs like gestures and sensors.
7. Include different inputs in testing plans.
The key message is that input cannot be detected, is a continuum, and is always changing. Web design needs to be adaptable and not assume certain inputs based on device properties.
This document summarizes a student project investigating the development of smartphones. It outlines the history of mobile phones from 1946 to recent iPhone and Android models. It describes popular smartphone brands and operating systems. Features, advantages, and drawbacks of smartphones are compared to older mobile phones. The document also describes entertainment apps, includes screenshots, and analyzes survey results on smartphone usage. In conclusion, smartphones are found to provide more functions than older phones, with price and features being primary considerations for consumers.
The document discusses the hype around HTML5 and examines what it actually is and how well browsers support its features. While HTML5 enables rich interactive experiences, full support across devices is still limited. Mobile browsers in particular lag desktop browsers in HTML5 support. The document advocates that HTML5 is an opportunity but is not a magic solution, and developers still face challenges like fragmentation.
What lies ahead of HTML5_Ooop Munich 2013_Krzysztof SzafranekWooga
The document discusses the future of HTML5 and the debate between developing mobile applications using native apps vs. web technologies like HTML5. It notes that while HTML5 was not ready for advanced mobile games in 2012 due to performance and feature limitations, the mobile web is catching up thanks to new web APIs and standards. Within 10 years, the mobile web may be comparable to native apps, though app stores' long term role is uncertain. The document also outlines the tradeoffs between native, web, and hybrid app development approaches.
The document discusses tools and strategies for mobile journalism using smartphones. It provides examples of video and audio equipment that can enhance smartphone reporting abilities, such as external microphones and rigs to stabilize video. It also lists video, audio, editing, and storage apps that journalists can use to capture, process and share multimedia content on the go. Tips are provided for organizing apps and gear, avoiding disruptions, and improving video quality.
Fairfax Sydney #mojo #mojocon Feb 2017 Meetup - 360 video production basicsJamie Andrei
Fairfax Sydney #mojo #mojocon Feb 2017 Meetup - 360 video production basics
An introduction to 360 video / VR basics, introducting the concept, several approach & technologies, through to 2x key 360 social platforms (fish where the fish are), through to a basic workflow & some hands on Google Cardboard demos.
This document summarizes the latest mobile news from March 2012. It discusses the growth of smartphones and their increasing market share over "dumb phones". It provides market share numbers for Android, iOS, and other platforms. It also summarizes new products like the new iPad and Samsung Galaxy S3, updates to platforms like Android and Windows Phone, and other miscellaneous mobile news stories from March 2012.
This document provides an overview of emerging technologies and trends from 2005-2010 as presented by Stephen P. Anderson and Jeremy Johnson from Bright Corner. Key points discussed include the future of the web, user experience design, visioning techniques, current and future technologies such as wireless power, augmented reality, mobile apps, touch interfaces, and more. Various concepts, products and emerging trends are illustrated through links to videos and articles.
PhoneGap allows developers to build mobile apps using standard web technologies like HTML, CSS, and JavaScript. It works by embedding a webview component within a native container, and provides a bridge for JavaScript to access some device APIs. PhoneGap has grown a large community and supports many mobile platforms. While it allows cross-platform development, apps are still packaged natively and some limitations remain. The future roadmap includes improved plugin support and new features like web sockets and background services to enhance the capabilities of hybrid mobile apps.
This document discusses how to optimize Android apps for Honeycomb and later versions by using fragments. It notes that fragments were introduced in Android 3.0 to help structure apps for both phones and tablets. While only available on newer versions initially, the support package backports fragments to older devices. The document outlines problems developers face with fragmentation and how to address it using fragments, event listener interfaces, and frame layouts to dynamically add fragments. It provides statistics on device platforms and screen sizes and recommends sample code and resources for learning more.
The document discusses the state of the smartphone market in 2008 and provides guidance on developing applications for various smartphone platforms. It notes that in 2008, Nokia, RIM, and Samsung dominated the global smartphone market, with Apple growing 245%. It then provides an overview of tools and considerations for developing apps for platforms like iPhone, Android, Blackberry, and mobile Flash, noting that HTML, CSS, and JavaScript can be used to develop for many platforms. Challenges and differences between platforms like screen sizes, SDKs, and programming languages are outlined.
Andrew gave a presentation on GNOME, Linux mobile stacks, and engaging with open source communities. He discussed the growth of the mobile market and importance of open platforms. GNOME's role in providing tools for developers on mobile was covered. Finally, he compared GNOME and Qt frameworks, emphasizing the need for fair evaluation of open source options. Developers should find accessible SDKs to get involved in building for open platforms.
From custom hardware to Android TV and beyond. A brief introduction on how to develop apps for Android TV using React Native.
Talk at Reat Native London Meetup - July 2019: https://youtu.be/wm56XCtMw40
Your boss has an iPhone, so of course he wants an app. But does an app really make business sense? Or is a responsive design website enough?
And with hundreds of thousands of apps out there, what will make people choose and use yours? What makes a good mobile user interface? And how can you make sure your company actually delivers one?
Responsive design might make sense if you've got a content driven website. But how should your web team work together when every web page they are making needs to work at any width and resolution? And can you get the content under control to make pages that really make sense on small screens and big ones?
- Android is an open source operating system developed by Google and the Open Handset Alliance. It was originally developed by Android Inc which was acquired by Google in 2005.
- The first Android phone was launched in 2008. Since then Android has seen many updates and versions from 1.0 to the current 10.0.
- Android is based on a modified Linux kernel and allows developers to write managed code in Java. It uses Dalvik as its virtual machine instead of the standard Java virtual machine.
- The Android software stack consists of applications, an application framework, libraries and the Linux kernel. Key frameworks include activity manager, notification manager, and window manager.
- Android provides features like multi-touch, cameras,
PhoneGap allows developers to build native mobile apps using web technologies like HTML, CSS, and JavaScript. It works by wrapping web content in a native container on each mobile platform, allowing developers to write code once and deploy it across iOS, Android, BlackBerry, and other platforms. PhoneGap uses a plugin architecture that enables accessing native device APIs like the camera, contacts, and geolocation from JavaScript. It supports many mobile browsers and platforms, while providing tools for compiling, debugging, and deploying apps.
Mobile devices are increasingly popular while PCs decline. Smartphones now outsell PCs and their screens, processors, and networks continue advancing. Mobile networks are transitioning to high-speed 4G LTE. Worldwide, Android and iOS dominate the smartphone market. Content providers like the BBC are developing mobile strategies including responsive websites and apps targeting various mobile platforms and form factors.
HTML5 is the Future of Mobile, PhoneGap Takes You There Todaydavyjones
PhoneGap allows developers to build mobile apps using HTML, CSS and JavaScript instead of relying on platform-specific languages like Objective-C or Java. The document discusses PhoneGap's capabilities and advantages, including writing apps once that run on multiple platforms, using web technologies that are widely known by developers, and leveraging growing browser capabilities on mobile through HTML5. It also outlines PhoneGap's APIs, tools, libraries, and community to help developers get started building cross-platform mobile apps.
Presented at Web Directions Code, Melbourne
If you have a website—particularly one that generates revenue for your organization—you need a Progressive Web App. So where do you begin? How do you decide which features of a Progressive Web App make sense for your users? What tools can make the process easier (or harder)? In this practical session, Jason will guide you through the key design decisions you’ll need to make about your Progressive Web App and how those decisions impact the scope of your project. He'll also teach you how to avoid common pitfalls and help you take full advantage of Progressive Web App technology.
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.
Why Progressive Web Apps will transform your websiteJason Grigsby
Progressive web apps (PWAs) can transform websites by making them more like native apps through the use of service workers, web app manifests, and other modern web capabilities. Some key benefits of PWAs include providing fast and reliable experiences even on slow mobile networks, working regardless of a network connection, and engaging users through web app banners and push notifications. Early results show that PWAs can significantly reduce data usage and increase user engagement, conversion rates, and sales compared to mobile websites. While PWAs work across browsers, including on iOS, their full capabilities are still progressively being adopted.
Is the buzz around Progressive Web Apps real or are they simply the latest fad? In this talk, you’ll learn exactly what Progressive Web Apps are, what problems they solve, and what new design challenges they present. Jason will show how organizations are using Progressive Web Apps to provide better and faster user experiences.
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.
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.
When responsive web design meets the real worldJason Grigsby
The document discusses responsive web design and some of the challenges it faces. It recommends adopting a mobile first approach where the mobile styles are defined first before desktop styles, allowing for a progressive enhancement. It also emphasizes the importance of performance and ensuring responsive designs are not just focused on layout but also on optimizing for speed. Key techniques discussed include building mobile first, reordering media queries, keeping basic styles outside queries, and scoping images within media queries to avoid unnecessary downloads.
Adaptive Input — Breaking Development Conference, San DiegoJason Grigsby
Windows 8. Chromebook Pixel. Ubuntu Phone. These devices shatter another consensual hallucination that we web developers have bought into: mobile = touch and desktop = keyboard and mouse.
We have tablets with keyboards; laptops that become tablets; laptops with touch screens; phones with physical keyboards; and even phones that become desktop computers. Not to mention new forms of input like cameras, voice control, and sensors.
We've learned how to respond to screen size. Our next challenge is learning how to adapt to different forms of input.
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.
No matter how much we try to put ourselves into a mobile first mentality, it is hard for us to do so fully. Our access to PCs prevents us from experiencing mobile the way many in the world do.
We're currently fighting for parity among experiences. We're arguing that the mobile version shouldn't be a dumbed down version of the desktop site.
But we've set our sights too low. In a true Mobile First world, the mobile version should be the best experience. Mobile shouldn't just match the desktop experience, it should exceed it.
Mobile: The Market, The Web and Windows Phone’s Future Jason Grigsby
1. Mobile internet usage is growing exponentially, surpassing traditional internet usage.
2. Smartphone apps represent a huge opportunity, but mobile web apps can also be very powerful if designed well for the mobile context.
3. There is no consensus on whether native apps or mobile web apps have an advantage, and the debate touches on issues like user experience, business models, and platform lock-in.
Where 2.0 -- Get me a mobile strategy or you’re fired!Jason Grigsby
Mobile is a disruptive technology that requires companies to develop a mobile strategy or risk losing customers. Companies should understand the mobile context including what devices customers use and not assume everyone has downloaded their app. They should look beyond just native apps to also use mobile web, SMS and MMS to reach customers. Apps should be focused on serving the most loyal customers and adding real value through mobile capabilities. Developing products specifically for mobile, not just porting desktop products, is key to success.
The document discusses how mobile technology is transforming journalism and media. Some key points:
- Mobile devices are the most important communication technology since the printing press.
- Mobile is the 7th mass media, with over 4.6 billion mobile subscribers worldwide, more than half the planet.
- Mobile represents a disruptive technology that is changing how media companies operate and distribute news/content.
- Usage of mobile internet and apps like Opera Mini are growing dramatically, showing people increasingly consuming media on mobile.
Why You Should Make Mobile Your Career | Clark CollegeJason Grigsby
A variation of my talk on mobile strategy given to Clark College to encourage students to pursue mobile and to encourage the college to adopt mobile curriculum.
Google Talk: DOs and DON'Ts of Mobile StrategyJason Grigsby
Presented at Google on October 8, 2010 as part of the Google Talks series.
Updated from previous presentations to talk about legacy content management systems and more ways our iPhone lens skews our perception of the world.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
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.
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.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Project Management Semester Long Project - Acuityjpupo2018
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
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.
16. People often use mobile while watching tv.
88% 86%
tablet smartphone
owners say they use their device while
watching TV at least once a month.
http://blog.nielsen.com/nielsenwire/online_mobile/double-vision-global-trends-in-tablet-
and-smartphone-use-while-watching-tv/
27. [People] “don’t want a computer on their
TV,” Apple CEO Steve Jobs said today.
“They have computers. They go to their
wide-screen TVs for entertainment. Not to
have another computer. This is a hard one for
people in the computer industry to
understand, but it's really easy for consumers
to understand. They get it.”
http://www.flickr.com/photos/acaben/541334636/
28. And so, it turns out people want keyboards. I
mean, when I started in this business one of
the biggest challenges was that people
couldn’t type.…
And if you do email of any volume, you gotta
have a keyboard. So we look at the tablet and
we think it’s gonna fail.
—Steve Jobs, 2003
http://www.flickr.com/photos/acaben/541334636/
36. Apps = Embedded Web Views =
http://www.flickr.com/photos/34818713@N00/1314251273/
37. Apps = Embedded Web Views = 3rd Party Browsers
http://www.flickr.com/photos/34818713@N00/1314251273/
38. Apps = Embedded Web Views = 3rd Party Browsers
If that is true, don’t you think Apple will ship Safari?
http://www.flickr.com/photos/34818713@N00/1314251273/
39. “By the summer of 2012, the
majority of the televisions you
see in stores will have Google
TV embedded in it”
Photo by JD Lasica/Socialmedia.biz
http://www.flickr.com/photos/jdlasica/5181380514/
50. Will Google TV follow Android’s path?
http://www.unwiredview.com/2011/12/21/andy-rubin-%E2%80%9Candroid-daily-activations-top-700k-a-day%E2%80%9D-on-the-way-to-1-million-a-day-in-q2-2012/
51. Considering
TVs helps
inform how
we build for
mobile.
http://www.flickr.com/photos/revdancatt/3789612273/
52. And can help us avoid
short-sighted solutions
http://www.flickr.com/photos/pss/4876189045/
90. The TV Context
Yes, I said “Context.”
http://www.flickr.com/photos/imnohero/2330548144
91. Our vision of mobile
context is often wrong.
http://www.flickr.com/photos/brunauto/5062644167/
92. 80% during
misc downtime
76% while
waiting in lines
62% while
watching TV
69% for point of
sale research
http://www.flickr.com/photos/missmeng/5327470961
99. Designing for a 10-foot UI
http://www.flickr.com/photos/chrisbartow/5835428673
100. Making text easy to read
Google Opera
• Limit paragraphs to 90 words • Minimum font size of 22px
• Break into small chunks • Line length: 10 words or less
• Line length: 5-7 words • Generous leading
• Body text around 21pt on 720p
and 28pt on 1080p
• Add more leading
101.
102. “A good rule of thumb is to increase the
size of an element (such as an image or
font) 1.5x for 720p and 2.0x for 1080p
relative to the size of that element in a
normal PC browser experience.”
—Google TV Guide
103. Optimize for tasks
Google Opera
• When designing a web page for • Primary activity often revolves
TV, the viewable area should around quick information look-
display less information overall, up (for instance, cast and crew
and what's there should focus on details for a particular movie,
a confined set of tasks (even weather reports, TV listings) and
consider performing their quick access to services. Web
desired task automatically or content for TV should therefore
select by default). be optimised — in terms of
overall presentation, navigation
and functionality — and task-
focused, giving quick and clear
access to all relevant features
and information.
106. “The main interface of Google TV encourages the
use of the D-pad on the remote to make selections
on a screen -- it's likely that users will keep this
habit even on the web.”
107. CSS3 Basic User Interface specification for
directional focus navigation
/* CSS */
#copyright {
nav-down: #logo;
}
http://dev.opera.com/articles/view/tweaking-spatial-navigation-for-tv-browsing/
110. Google TV jQuery UI Library
http://code.google.com/p/gtv-resources/
111. Unfortunately, I had trouble getting the Google TV
jQuery UI library to work on non-Google TVs.
Needs more testing.
112. Both solutions require adding a layer of CSS or JS
specifically to support TV interaction.
113. Performance Challenges
Google Opera
• Google TV may not be able to • Modest hardware. Somewhere
render a page as quickly as between high-end smart
your workstation. phones and low end laptops.
• Avoid overly heavy and
complex JavaScript.
• Avoid layering and opacity.
• Low limit on caching. Cannot
assume assets cached. Cannot
rely on cookies for subsequent
session.
115. Horizontal paging is preferred
http://gtv-resources.googlecode.com/svn/trunk/gtv-jquery-demo/index.html
116. Supporting different screen resolutions
Google Opera
• Only HDTVs. • Most modern web-enabled
TVs support 1280×720 as a
• 720p and 1080i/p minimum resolution.
• 720p content is usually
• The exact pixel dimensions of upscaled
the display varies by TV
manufacturer. • Virtual resolutions — as an
example, the Nintendo Wii
• Provides an auto-zoom feature has a virtual width of 800
which you need to design for pixels. Height varies based on
or around. the type of TV (4:3 or 16:9
aspect ratio) and user settings.
125. Media types are useless except for screen and print.
https://twitter.com/#!/patrick_h_lauke/status/190078528568569856
https://twitter.com/#!/patrick_h_lauke/status/190078688287653889
126. Web developers are litter bugs.
http://www.flickr.com/photos/jpdaigle/3393858438/
132. Alright fine.
We’ll use device
detection.
http://www.flickr.com/photos/77799978@N00/5351372848/
133. User Agent String for a 2012 LG Smart TV
Mozilla/5.0 (DirectFB; Linux; ko-KR)
AppleWebKit/534.26+ (KHTML, like
Gecko) Version/5.0 Safari/534.26+
134. User Agent String for a 2012 LG Smart TV
Mozilla/5.0 (DirectFB; Linux; ko-KR)
AppleWebKit/534.26+ (KHTML, like
Gecko) Version/5.0 Safari/534.26+
Nothing we can use in that string!
135. That
sucks.
http://www.flickr.com/photos/plunkmasterknows/357836855/
140. Choosing responsiveness, as a characteristic
shouldn’t necessarily define the wider
implementation approach. Device
Experiences (i.e. standalone sites, aimed at a
group of devices) can also be responsive,
providing the flexibility to support a much
wider range of devices.
—Stephanie Rieger
141. No. ARTICLES TOPICS ABOUT CONTACT CONTRIBUTE FEED
320
DECEMBER 14, 2010 Search ALA
Smartphone Browser Landscape include discussions
by P E T E R - P A U L K O C H
Published in: User Interface Design , Mobile , Mobile Design , Mobile Development
Topics
Discuss this article » | Share this article » Code
Content
Culture
Design
Mobile
Process
User Science
Snapshot
Most web designers and
developers (not to
mention the entire
blogosphere) fall
squarely in the high-end
market. A cultural bias
Users expect websites to work on their mobile phones. In two to three years, mobile support
exists against OSs aimed
will become standard for any site. Web developers must add mobile web development to their at any other market. As
skill set or risk losing clients. a result, most people
focus on the struggle
How do you make websites mobile compatible? The answer is obvious: By testing them on all between iOS and
mobile phones, and by solving the problems you encounter. But, that’s a useless answer. It’s Android, and ignore the
rest. This has to change.
impossible to test your designs on every mobile phone out there. Within the mobile phone
landscape, there are at least ten operating systems (OSs) and fifteen browsers that require
consideration. Mobile devices are expensive, and not every web developer can afford to buy
five to ten of them. Testing “on all mobile phones” is impossible for most web developers.
In this article, I’ll give you an overview of the mobile web market, as well as phone platforms
and their browsers, so that you can decide which mobile devices to test on. Then, we’ll look at
how to set up a mobile test bed. Stay in better touch with
customers with
142. “Testing on as many devices as possible is a great
idea in theory, but in practice it is untenable. Even if we
buy a few devices to try to cover more ground, they will be
outdated in just a few months or a year at most. So are we
supposed to buy multiple devices per year?”
posted at 11:32 am on December 14, 2010 by klayon
“If that’s the mobile landscape, I want no part of it.”
posted at 07:22 am on December 15, 2010 by Polsonby
http://www.alistapart.com/comments/smartphone-browser-landscape/
143. If you thought phones were bad,
You ain’t seen nothing yet!
144. Most stores have no remotes and no wi-fi
http://www.flickr.com/photos/elmada/1431918753/
145. Bring your phone for tethering to TVs
http://www.flickr.com/photos/bendodson/3367856091/
165. “Some people at Netflix have been arguing
for a single experience across all devices. This
has never born out in any kind of testing.
Instead, Netflix has a variety of experiences
on different devices and even regions.”
http://www.lukew.com/ff/entry.asp?1339
166. • User posture: Stationary, Lean back, on-the-go, shared
• Input capabilities: pointer/keyboard, LRUD/OSK,
Gesture/OSK
• Navigation style: controls & windows, panes
• Display capabilities: Hi-Res, near, far away, small,
medium, large
• These constraints are really powerful. You need to
embrace them to get to appropriate designs.
http://www.lukew.com/ff/entry.asp?1339
167. When we need more control to craft an experience for a
given device, how can we do so in a sustainable manner?
168. Yes, Smart TVs
suck right now.
http://www.flickr.com/photos/nathaninsandiego/4829858186/
173. So even if we don’t
have to design for
TVs today…
174. It behooves us to start thinking about and
planning for what it will be like to do so…
175. So we won’t build solutions
for today’s problems and
then find ourselves surprised
by what comes next.
Flickr photo by Drift Words: http://www.flickr.com/photos/44124413076@N01/11846265/
176.
177. Thank You!
Special thanks to Patrick H. Lauke, the
Google TV team, Flickr users sharing
under creative commons & the kind
folks at Beaverton Video Only.
Jason Grigsby
@grigs • cloudfour.com
Slides: bit.ly/immobilism
http://www.flickr.com/photos/sualk61/4083223760/
178. Get 40% off of the print and 50% off of ebook
version using code AUTHD at oreilly.com.
OR Amazon link (no code): http://bit.ly/hf-mw