Cascade UX Day SF 2013
•
1 like•530 views
The document discusses rapid UX design and prototyping techniques. It recommends using low-fidelity paper prototypes for quick iteration and participatory design. Digital tools and open platforms allow for cross-device prototyping and testing partial functionality with customers to gain insights. The goal is to enable nimble teams to adapt quickly based on empirical learning.
Report
Share
Report
Share
Download to read offline
Recommended
Findability Bliss Through Web Standards
The document summarizes a presentation on findability given by Aaron Wall at An Event Apart in Boston on June 23, 2009. The presentation covered 3 simple goals for findability: finding your site, finding things within your site, and rediscovering your site. It discussed using semantic markup, accessibility, progressive enhancement, and microformats to improve findability. It provided tips for keyword placement, research, finding competitors, case studies, and checking rankings to build findable websites.
Take-aways from sxsw by v3
This document summarizes key trends from the 2013 SXSW conference. It discusses shifts from apps to open web APIs, iterations to "moonshots", digital integration to connecting the physical, user interfaces to no interfaces, augmented reality to 3D prototyping, and social media to brand narratives. New technologies like Google Glass, 3D printing, and augmented reality were also covered. The document concludes that the conference showed technology maturing to benefit humanity and that collaboration is needed to ensure relevance.
6 take aways from sxsw 2013 by venturethree
The document discusses 6 technology trends from 2013:
1) Moving from apps to open web and APIs
2) Shifting from iterations to "moonshots" or seemingly impossible ideas
3) Transitioning from digital integration to connecting the physical world
4) Changing from traditional user interfaces to "no interface"
5) Advancing from augmented reality to 3D prototyping
6) Moving from social media to brand narratives
The document also profiles innovators and new technologies, highlighting opportunities to rethink existing approaches using these emerging trends.
Inte Great Detailed Presentation Full V35 2
The document discusses inteGREAT, a tool for requirements development and knowledge management. It promotes building an integrated body of knowledge through features like requirements normalization, collaboration, and automation. This allows organizations to standardize processes, reuse knowledge, achieve agility and higher quality, and realize benefits like reduced documentation time and improved productivity. Customer testimonials praise inteGREAT's abilities to efficiently capture, format, share, and reuse requirements knowledge at both the project and enterprise levels.
Mock-ups in design af Lars Bo Larsen, AAU
Oplægget blev holdt ved InfinIT-arrangementet "temadag om interaktionsdesign", der blev afholdt den 20. januar 2011. Læs mere om arrangementet her: http://www.infinit.dk/dk/hvad_kan_vi_goere_for_dig/viden/reportager/goer_brugernes_behov_til_gode_produkter_02.htm
Everything You Know is Not Quite Right Anymore: Rethinking Best Practices to ...
We’re entering a new era where an increasing number of devices with wildly divergent features -- including phones, tablets, game consoles, and TVs -- are connected to the Internet. As the way people access the Internet changes, there is an urgent need to rethink how we use the web to communicate. This doesn't mean creating separate solutions for each device but rather preparing our existing content to meet this increasingly unpredictable future. Dave Olsen and Doug Gapinski will share and examine examples that show how responsive design will help institutions rethink and adjust for the future-friendly web.
Primary topics that are covered are: understanding the reality of web development today, example RWD design patterns, and understanding how to test and optimize the performance of your RWD website.
Everything You Know is Not Quite Right Anymore: Rethinking Best Web Practices...
We’ve entered a new era where an increasing number of devices with wildly divergent features— including phones, tablets, game consoles, and TVs—are connected to the Internet. As the way people access the Internet changes, there is an urgent need to rethink how we use the web to communicate.
This doesn't mean creating separate solutions for each device but rather preparing our existing content to meet an unpredictable future. Responsive web design means changing how we plan and evaluate performance. Dave Olsen and Doug Gapinski share and examine examples to help institutions rethink and adjust for the future-friendly web.
Presenters
Dave Olsen
Professional Technologist, West Virginia University
Doug Gapinski
Strategist, mStoner
WSO2CONMay2024OpenSourceConferenceDebrief.pptx
A recap of interesting points and quotes from the May 2024 WSO2CON opensource application development conference. Focuses primarily on keynotes and panel sessions.
Recommended
Findability Bliss Through Web Standards
The document summarizes a presentation on findability given by Aaron Wall at An Event Apart in Boston on June 23, 2009. The presentation covered 3 simple goals for findability: finding your site, finding things within your site, and rediscovering your site. It discussed using semantic markup, accessibility, progressive enhancement, and microformats to improve findability. It provided tips for keyword placement, research, finding competitors, case studies, and checking rankings to build findable websites.
Take-aways from sxsw by v3
This document summarizes key trends from the 2013 SXSW conference. It discusses shifts from apps to open web APIs, iterations to "moonshots", digital integration to connecting the physical, user interfaces to no interfaces, augmented reality to 3D prototyping, and social media to brand narratives. New technologies like Google Glass, 3D printing, and augmented reality were also covered. The document concludes that the conference showed technology maturing to benefit humanity and that collaboration is needed to ensure relevance.
6 take aways from sxsw 2013 by venturethree
The document discusses 6 technology trends from 2013:
1) Moving from apps to open web and APIs
2) Shifting from iterations to "moonshots" or seemingly impossible ideas
3) Transitioning from digital integration to connecting the physical world
4) Changing from traditional user interfaces to "no interface"
5) Advancing from augmented reality to 3D prototyping
6) Moving from social media to brand narratives
The document also profiles innovators and new technologies, highlighting opportunities to rethink existing approaches using these emerging trends.
Inte Great Detailed Presentation Full V35 2
The document discusses inteGREAT, a tool for requirements development and knowledge management. It promotes building an integrated body of knowledge through features like requirements normalization, collaboration, and automation. This allows organizations to standardize processes, reuse knowledge, achieve agility and higher quality, and realize benefits like reduced documentation time and improved productivity. Customer testimonials praise inteGREAT's abilities to efficiently capture, format, share, and reuse requirements knowledge at both the project and enterprise levels.
Mock-ups in design af Lars Bo Larsen, AAU
Oplægget blev holdt ved InfinIT-arrangementet "temadag om interaktionsdesign", der blev afholdt den 20. januar 2011. Læs mere om arrangementet her: http://www.infinit.dk/dk/hvad_kan_vi_goere_for_dig/viden/reportager/goer_brugernes_behov_til_gode_produkter_02.htm
Everything You Know is Not Quite Right Anymore: Rethinking Best Practices to ...
We’re entering a new era where an increasing number of devices with wildly divergent features -- including phones, tablets, game consoles, and TVs -- are connected to the Internet. As the way people access the Internet changes, there is an urgent need to rethink how we use the web to communicate. This doesn't mean creating separate solutions for each device but rather preparing our existing content to meet this increasingly unpredictable future. Dave Olsen and Doug Gapinski will share and examine examples that show how responsive design will help institutions rethink and adjust for the future-friendly web.
Primary topics that are covered are: understanding the reality of web development today, example RWD design patterns, and understanding how to test and optimize the performance of your RWD website.
Everything You Know is Not Quite Right Anymore: Rethinking Best Web Practices...
We’ve entered a new era where an increasing number of devices with wildly divergent features— including phones, tablets, game consoles, and TVs—are connected to the Internet. As the way people access the Internet changes, there is an urgent need to rethink how we use the web to communicate.
This doesn't mean creating separate solutions for each device but rather preparing our existing content to meet an unpredictable future. Responsive web design means changing how we plan and evaluate performance. Dave Olsen and Doug Gapinski share and examine examples to help institutions rethink and adjust for the future-friendly web.
Presenters
Dave Olsen
Professional Technologist, West Virginia University
Doug Gapinski
Strategist, mStoner
WSO2CONMay2024OpenSourceConferenceDebrief.pptx
A recap of interesting points and quotes from the May 2024 WSO2CON opensource application development conference. Focuses primarily on keynotes and panel sessions.
The ultimate guide to prototyping
This document provides an overview of prototyping and why it is important for product design. It discusses:
- 5 key reasons to prototype including improving communication, reducing waste, selling ideas, earlier testing, and prioritizing design.
- How prototypes improve collaboration and communication by allowing stakeholders to interact with ideas rather than just hear descriptions.
- How prototyping adds balance to the design process by merging conceptual goals with practical feedback.
- How prototyping enables earlier and easier usability testing which is important for refining a design.
- Why prototyping is especially important for mobile products due to the greater number of use cases and environments mobile devices are used in.
Blockchain Experience Design Meetup #1
This document announces the launch of the first Blockchain Experience Design meetup. It provides an overview of blockchains, protocols, decentralized applications, and how users currently interact with DApps via command lines, wallets, and DApp browsers. The document emphasizes designing for users and discusses challenges around clarifying which data comes from blockchains and which does not. It presents a design challenge around clarifying data sources and proposes a design thinking process to address the challenge through user research, idea generation, prototyping, and testing. The meetup agenda includes sharing emerging best practices, future design challenges, and using design thinking tools to solve blockchain user experience problems.
Poster - Tweaking HCI methods for m-desing
Poster - Tweaking HCI methods for m-desingOffice of Learning Technologies, Universitat Oberta de Catalunya
We sought to improve mobile design methods by tweaking HCI processes. Through three stages - background research, user prototyping, and user testing - we aimed to develop a better way to access messages and forums via mobile devices. Our paper prototypes were too abstract, so we transitioned to electronic mockups and high-fidelity paper prototypes. However, recording users' facial gestures, voices, and device interactions during testing proved challenging without proper setup. Observation of mobile testing was also difficult to follow."We are doing it wrong."
The document discusses problems with traditional software development approaches and proposes an alternative approach focused on continuous delivery. It argues that current practices prioritize resource utilization, projects, and technical possibilities over delivering value. Instead, it advocates for minimizing work-in-progress, focusing on flow over batching, establishing stable teams to continuously deliver working software, and making decisions based on learning rather than upfront estimates. The overall message is that software development needs to shift from a project mindset to prioritizing the delivery of valuable, working code.
JavaOne 2016 "Java, Microservices, Cloud and Containers"
Everyone is talking about building “cloud native” Java applications—and taking advantage of microservice architecture, containers, and orchestration/PaaS platforms—but there is surprisingly little discussion of migrating existing legacy (moneymaking) applications. This session aims to address this, and, using lessons learned from several real-world examples, it covers topics such when to rewrite applications (if at all), modeling/extracting business domains, applying the “application strangler” pattern, common misconceptions with “12-factor” application design, and the benefits/drawbacks of container technology.
6 Rules to Designing Amazing Mobile Apps (@media 2011)
THE PATH TO CREATING MEMORABLE MOBILE EXPERIENCES
Building a mobile app isn’t easy. Regardless of chosen platform or technology creating a memorable mobile experience has some pretty intense challenges throughout. However if you can get it right it can have some incredible rewards and propel your brand in more ways than one. After spending ten years building mobile apps for some of the biggest companies in the world, author and mobile designer Brian Fling shares his six rules for building amazing apps that will either you get you started or improve upon your next release.
TxJS 2011
This document provides an overview of building mobile applications using PhoneGap. It discusses how PhoneGap works by instantiating a chromeless browser and implementing a bridge to allow calling native device APIs from JavaScript. It also covers topics like plugins, debugging mobile apps, performance considerations, and the PhoneGap API for accessing device features like the camera, contacts, and geolocation. The document advocates for a mobile-first approach using modern web standards and technologies when building apps with PhoneGap.
Parents
The document summarizes the design process for creating a tracking device for children's belongings. It involved user research through an animated storyboard, ideating multiple concepts and selecting one through evaluation, developing wireframes and a visual design, creating 3D and physical prototypes using various tools, testing technologies, and laser cutting a final prototype. The process utilized lean UX and agile development principles of iterative design, validation with users, and parallel prototyping across interactive, physical, and electronic systems. The design process highlighted the challenges of managing development across different mediums in parallel and the importance of flexibility to change based on user feedback.
Towards Lensfield
Lensfield is a desktop and filesystem-based tool designed as a “personal data management assistant” for the scientist. It combines distributed version control (DVCS), software transaction memory (STM) and linked open data (LOD) publishing to create a novel data management, processing and publication tool. The application “just looks after” these technologies for the scientist, providing simple interfaces for typical uses. It is built with Clojure and includes macros which define steps in a common workflow. Functions and Java libraries provide facilities for automatic processing of data which is ultimately published as RDF in a web application. The progress of data processing is tracked by a fine-grained data structure that can be serialized to disk, with the potential to include manual steps and programmatic interrupts in largely automated processes through seamless resumption. Flexibility in operation and minimizing barriers to adoption are major design features.
Form Function Class 6, Manila, Philippines 14/11/2015
Sweating Details - Slides from my talk at Form Function Class 6 in Manila Philippines on Nov 14th, 2015.
This talk is about sweating details and how small tweaks and changes can make a big difference in any of the web design stages. From optimising the process, via UX and design all the way to performance, this talk covers possible tweaks and recommendations with some practical examples to improve the overall experience of our products.
Design Prototyping: Bringing Wireframes to Life
See how "design prototyping" differs from other techniques, and learn how to determine when a prototype is needed. Understand how to tailor your prototype to a particular audience, gather techniques for bringing paper sketches to life, and how interactive sketching can fit in an Agile process.
Expression Blend for Windows Phone
This document discusses how to wire up an application in Blend by walking through navigation, sample data, layout, user controls, real data, and dependency properties. It emphasizes getting the application structure and navigation correct during prototyping before coding. Specific techniques covered include importing designs from Expression Design and Photoshop, using sample data as a placeholder, exposing events and properties from user controls, and generating dependency properties. The goal is to facilitate collaboration between designers and developers in Blend.
Your first web application. From Design to Launch
Everyone has an idea for the next big web application, but what does it take to bring that application to life?
David Brooks walks you through the process from planning and design to launch. You'll learn what you need to know to build it, and how to fill the gaps you might have in your skill set.
Performance - a challenging craft
In my talk at socrates 2011, I descrived why performance is a craft and what to do to ensure great performance. I concluded with a few best practies and wonder if there are more
NoSQL Databases
During recent years it has appeared a new concept of databases more flexible and dynamic. They are called NoSQL. That kind of databases coexist with classical relational databases, but: What do they provide us? Why have they appeared ? Which is the wide variety we can choose? We will learn from MongoDB their use and functionalities.
Enterprise Testing in The Cloud
This slide contains a brief presentation of how Organizations can leverage Cloud to virtualize functional/performance testing and cost benefit from investing in hardware.
Rettig onprototyping
The document discusses the benefits of using low-fidelity or "lo-fi" prototyping, where interfaces are designed on paper and tested with real users early in the development process. This allows teams to go through many iterative design cycles in a short period of time to incorporate user feedback, as paper prototypes can be created and modified much faster than digital prototypes. The key benefits outlined are that lo-fi prototyping (1) is extremely fast, (2) brings user testing results very early in the process when changes are cheap to make, and (3) allows teams to try far more design ideas than with digital prototypes. The document provides guidance on assembling materials for building paper prototypes and preparing for useful user testing
Sandeep-portfolio-2016
This document provides a portfolio of projects by Sandeep Zechariah George K. It includes 13 projects in various fields including science, art, and technology. For each project there is a brief description of the motivation, process, challenges, and value added. The projects cover a range of areas such as cloud-based holter monitoring, shape displays, mobile application development, virtual and augmented reality, interactive toys, service design, and more. Skills developed include prototyping, software architecture, design, electronics, and more.
MoneySafe-FinalReport
This document summarizes an individual project report for an online banking system. The project involved designing and developing a web application to demonstrate skills in web development, database design, and user interaction. Key aspects included using the Laravel framework with PHP for the backend and a MySQL database. Testing was conducted to identify flaws. The project aimed to gain experience in areas like requirements gathering, design, implementation, and testing of a full-stack web application. Overall, the author was happy with meeting the goals of the project to showcase their technical abilities.
Interoperability in forge - fossa2010
This document discusses interoperability between software forges and preventing data lock-in. It defines the types of data shared on forges like source code, documentation, bug trackers, and community information. The Coclico project aims to establish standards for exchanging this data between forges to avoid issues when a forge shuts down or changes. The first step uses existing forge data formats. Work done includes exporting and importing data between FusionForge instances. Future work involves refining the process and integrating it with additional forges.
More Related Content
Similar to Cascade UX Day SF 2013
The ultimate guide to prototyping
This document provides an overview of prototyping and why it is important for product design. It discusses:
- 5 key reasons to prototype including improving communication, reducing waste, selling ideas, earlier testing, and prioritizing design.
- How prototypes improve collaboration and communication by allowing stakeholders to interact with ideas rather than just hear descriptions.
- How prototyping adds balance to the design process by merging conceptual goals with practical feedback.
- How prototyping enables earlier and easier usability testing which is important for refining a design.
- Why prototyping is especially important for mobile products due to the greater number of use cases and environments mobile devices are used in.
Blockchain Experience Design Meetup #1
This document announces the launch of the first Blockchain Experience Design meetup. It provides an overview of blockchains, protocols, decentralized applications, and how users currently interact with DApps via command lines, wallets, and DApp browsers. The document emphasizes designing for users and discusses challenges around clarifying which data comes from blockchains and which does not. It presents a design challenge around clarifying data sources and proposes a design thinking process to address the challenge through user research, idea generation, prototyping, and testing. The meetup agenda includes sharing emerging best practices, future design challenges, and using design thinking tools to solve blockchain user experience problems.
Poster - Tweaking HCI methods for m-desing
Poster - Tweaking HCI methods for m-desingOffice of Learning Technologies, Universitat Oberta de Catalunya
We sought to improve mobile design methods by tweaking HCI processes. Through three stages - background research, user prototyping, and user testing - we aimed to develop a better way to access messages and forums via mobile devices. Our paper prototypes were too abstract, so we transitioned to electronic mockups and high-fidelity paper prototypes. However, recording users' facial gestures, voices, and device interactions during testing proved challenging without proper setup. Observation of mobile testing was also difficult to follow."We are doing it wrong."
The document discusses problems with traditional software development approaches and proposes an alternative approach focused on continuous delivery. It argues that current practices prioritize resource utilization, projects, and technical possibilities over delivering value. Instead, it advocates for minimizing work-in-progress, focusing on flow over batching, establishing stable teams to continuously deliver working software, and making decisions based on learning rather than upfront estimates. The overall message is that software development needs to shift from a project mindset to prioritizing the delivery of valuable, working code.
JavaOne 2016 "Java, Microservices, Cloud and Containers"
Everyone is talking about building “cloud native” Java applications—and taking advantage of microservice architecture, containers, and orchestration/PaaS platforms—but there is surprisingly little discussion of migrating existing legacy (moneymaking) applications. This session aims to address this, and, using lessons learned from several real-world examples, it covers topics such when to rewrite applications (if at all), modeling/extracting business domains, applying the “application strangler” pattern, common misconceptions with “12-factor” application design, and the benefits/drawbacks of container technology.
6 Rules to Designing Amazing Mobile Apps (@media 2011)
THE PATH TO CREATING MEMORABLE MOBILE EXPERIENCES
Building a mobile app isn’t easy. Regardless of chosen platform or technology creating a memorable mobile experience has some pretty intense challenges throughout. However if you can get it right it can have some incredible rewards and propel your brand in more ways than one. After spending ten years building mobile apps for some of the biggest companies in the world, author and mobile designer Brian Fling shares his six rules for building amazing apps that will either you get you started or improve upon your next release.
TxJS 2011
This document provides an overview of building mobile applications using PhoneGap. It discusses how PhoneGap works by instantiating a chromeless browser and implementing a bridge to allow calling native device APIs from JavaScript. It also covers topics like plugins, debugging mobile apps, performance considerations, and the PhoneGap API for accessing device features like the camera, contacts, and geolocation. The document advocates for a mobile-first approach using modern web standards and technologies when building apps with PhoneGap.
Parents
The document summarizes the design process for creating a tracking device for children's belongings. It involved user research through an animated storyboard, ideating multiple concepts and selecting one through evaluation, developing wireframes and a visual design, creating 3D and physical prototypes using various tools, testing technologies, and laser cutting a final prototype. The process utilized lean UX and agile development principles of iterative design, validation with users, and parallel prototyping across interactive, physical, and electronic systems. The design process highlighted the challenges of managing development across different mediums in parallel and the importance of flexibility to change based on user feedback.
Towards Lensfield
Lensfield is a desktop and filesystem-based tool designed as a “personal data management assistant” for the scientist. It combines distributed version control (DVCS), software transaction memory (STM) and linked open data (LOD) publishing to create a novel data management, processing and publication tool. The application “just looks after” these technologies for the scientist, providing simple interfaces for typical uses. It is built with Clojure and includes macros which define steps in a common workflow. Functions and Java libraries provide facilities for automatic processing of data which is ultimately published as RDF in a web application. The progress of data processing is tracked by a fine-grained data structure that can be serialized to disk, with the potential to include manual steps and programmatic interrupts in largely automated processes through seamless resumption. Flexibility in operation and minimizing barriers to adoption are major design features.
Form Function Class 6, Manila, Philippines 14/11/2015
Sweating Details - Slides from my talk at Form Function Class 6 in Manila Philippines on Nov 14th, 2015.
This talk is about sweating details and how small tweaks and changes can make a big difference in any of the web design stages. From optimising the process, via UX and design all the way to performance, this talk covers possible tweaks and recommendations with some practical examples to improve the overall experience of our products.
Design Prototyping: Bringing Wireframes to Life
See how "design prototyping" differs from other techniques, and learn how to determine when a prototype is needed. Understand how to tailor your prototype to a particular audience, gather techniques for bringing paper sketches to life, and how interactive sketching can fit in an Agile process.
Expression Blend for Windows Phone
This document discusses how to wire up an application in Blend by walking through navigation, sample data, layout, user controls, real data, and dependency properties. It emphasizes getting the application structure and navigation correct during prototyping before coding. Specific techniques covered include importing designs from Expression Design and Photoshop, using sample data as a placeholder, exposing events and properties from user controls, and generating dependency properties. The goal is to facilitate collaboration between designers and developers in Blend.
Your first web application. From Design to Launch
Everyone has an idea for the next big web application, but what does it take to bring that application to life?
David Brooks walks you through the process from planning and design to launch. You'll learn what you need to know to build it, and how to fill the gaps you might have in your skill set.
Performance - a challenging craft
In my talk at socrates 2011, I descrived why performance is a craft and what to do to ensure great performance. I concluded with a few best practies and wonder if there are more
NoSQL Databases
During recent years it has appeared a new concept of databases more flexible and dynamic. They are called NoSQL. That kind of databases coexist with classical relational databases, but: What do they provide us? Why have they appeared ? Which is the wide variety we can choose? We will learn from MongoDB their use and functionalities.
Enterprise Testing in The Cloud
This slide contains a brief presentation of how Organizations can leverage Cloud to virtualize functional/performance testing and cost benefit from investing in hardware.
Rettig onprototyping
The document discusses the benefits of using low-fidelity or "lo-fi" prototyping, where interfaces are designed on paper and tested with real users early in the development process. This allows teams to go through many iterative design cycles in a short period of time to incorporate user feedback, as paper prototypes can be created and modified much faster than digital prototypes. The key benefits outlined are that lo-fi prototyping (1) is extremely fast, (2) brings user testing results very early in the process when changes are cheap to make, and (3) allows teams to try far more design ideas than with digital prototypes. The document provides guidance on assembling materials for building paper prototypes and preparing for useful user testing
Sandeep-portfolio-2016
This document provides a portfolio of projects by Sandeep Zechariah George K. It includes 13 projects in various fields including science, art, and technology. For each project there is a brief description of the motivation, process, challenges, and value added. The projects cover a range of areas such as cloud-based holter monitoring, shape displays, mobile application development, virtual and augmented reality, interactive toys, service design, and more. Skills developed include prototyping, software architecture, design, electronics, and more.
MoneySafe-FinalReport
This document summarizes an individual project report for an online banking system. The project involved designing and developing a web application to demonstrate skills in web development, database design, and user interaction. Key aspects included using the Laravel framework with PHP for the backend and a MySQL database. Testing was conducted to identify flaws. The project aimed to gain experience in areas like requirements gathering, design, implementation, and testing of a full-stack web application. Overall, the author was happy with meeting the goals of the project to showcase their technical abilities.
Interoperability in forge - fossa2010
This document discusses interoperability between software forges and preventing data lock-in. It defines the types of data shared on forges like source code, documentation, bug trackers, and community information. The Coclico project aims to establish standards for exchanging this data between forges to avoid issues when a forge shuts down or changes. The first step uses existing forge data formats. Work done includes exporting and importing data between FusionForge instances. Future work involves refining the process and integrating it with additional forges.
Similar to Cascade UX Day SF 2013 (20)
JavaOne 2016 "Java, Microservices, Cloud and Containers"
JavaOne 2016 "Java, Microservices, Cloud and Containers"
6 Rules to Designing Amazing Mobile Apps (@media 2011)
6 Rules to Designing Amazing Mobile Apps (@media 2011)
Form Function Class 6, Manila, Philippines 14/11/2015
Form Function Class 6, Manila, Philippines 14/11/2015
Cascade UX Day SF 2013
- 1. UX Toolkit: Rapid Design and Prototyping Megan O’Rorke UX/Product @leggomymego 1
- 3. History of User Research Long lead times High cost Opaque Real time 3
- 4. Low Fidelity Rapid iteration Participatory design 4
- 5. The Power of Paper 5
- 6. Prototypes interactions behaviors limitations 6
- 7. Digital Tools 7
- 8. Open Platforms cross-device pair prototype high fidelity 8
- 9. Test with Customers Partial functionality Fake landing pages Workarounds 9
- 10. Shared Understanding Actionable insights Empathy Context awareness Nimble team 10
- 11. Adaptability New features Murphy’s law 11
- 12. Findability 12
- 13. voice cloud video biosensors - body as medium 3D printing 13
- 14. More HTML/CSS: Anna Debenham http://www.netmagazine.com/tutorials/building-prototypes-html-and-css Cross-device design: Future Friendly futurefriend.ly 14
- 15. Thank You Continue the conversation: @leggomymego megororke@gmail.com 15