Mobile & Tablet UX | NYU School of Professional Studies | Week 1 (Intro)Liz Filardi
These are my slides for the first week of the class "Mobile and Tablet UX" at the NYU School of Professional Studies. The course is taught online in 4 sessions.
An Introduction to Agile User Research and Testing #MW2015Liz Filardi
What do your visitors really want in a digital product? How do you know whether your product is intuitive to use? What do you do when stakeholder expectations differ from visitor needs? Led by a Producer and a Researcher, this half-day workshop is intended to help you answer these questions with confidence using tools that you can rapidly employ and learn from.
We will share methods for developing research tools, gathering data, and making the most of findings to inform your approach at key milestones in the production of apps, digital games, and websites. We will provide anecdotes from our own experiences to illustrate how these methods can pan out in the wild.
Participants will learn about research strategies including:
– Card Sorting- hone in on priorities and preferences
– User Testing- evaluate the response to your designs
– Surveys and Interviews- ask the right questions of the right people
– Observations- know what to watch for, and how to record what you see
Participants will work in small teams to identify a challenge of their own, strategically choose a research method, and adapt and test their instruments. Each participant will leave with tools and strategies that they can use to gather feedback for an informed and iterative design process.
This workshop is for producers, project managers, educators, designers, and developers involved in developing digital experiences.
http://www.museumsandtheweb.com/mw2015-workshop-an-introduction-to-agile-user-research-testing/
Programmers testing their own code is not a new phenomenon, but with the emergence of agile development practices and code craftsmanship, there has been a move towards Programmers visibly taking more accountability for the code they write.
This is great news for those Testers used to being the gatekeepers to quality and answering the “why wasn’t this found in test?” question.
Programmers and Testers are now helping to improve the quality of code, but there is still one anti-pattern I have observed in teams in which both Programmers and Testers are testing the code – they are not actually working with each other when establishing a unified testing strategy.
This results in gaps in test coverage and / or unnecessarily duplicated testing.
This slide deck is from my Agile North presentation.where I presented my ICEBERG model for helping Programmers & Testers work more collaboratively. I also introduced another model I use for helping teams work together - Virginia Satir's Interaction Model.
A basic primer on bringing Lean Startup techniques to technical teams and organizations. Talk centered on successful integration of engineers into small, cross-functional lean startup teams. Emphasis on addressing the resulting changes in the role of the engineer.
Optimizely Product Deep Dive: Experiment APIOptimizely
ERIC HIGGINS, SOFTWARE ENGINEER, OPTIMIZELY
Eric Higgins, software engineer at Optimizely, walks through some exciting enhancements to Optimizely’s developer platform.
Topics covered include:
Getting started with the API
Live demo
Example use–cases
The document discusses principles for agile software development. It advocates for an iterative development process of creating software, shipping it, observing user behavior, and repeating the process based on learnings. Specific principles discussed include not assuming the user's perspective, designing for target demographics, and focusing on passionate people to build software that users love.
Onboarding at scale @Booking.com focuses on improving the onboarding process for property owners through evolutionary experimentation. The presentation discusses testing individual elements of the onboarding journey, as well as combining elements, to identify the core value and pain points. User research is key to understanding problems and testing hypotheses. The goal is to help property owners achieve their goals faster by designing an onboarding experience that guides them through setup, use of the extranet, and accessing actionable data.
Mobile & Tablet UX | NYU School of Professional Studies | Week 1 (Intro)Liz Filardi
These are my slides for the first week of the class "Mobile and Tablet UX" at the NYU School of Professional Studies. The course is taught online in 4 sessions.
An Introduction to Agile User Research and Testing #MW2015Liz Filardi
What do your visitors really want in a digital product? How do you know whether your product is intuitive to use? What do you do when stakeholder expectations differ from visitor needs? Led by a Producer and a Researcher, this half-day workshop is intended to help you answer these questions with confidence using tools that you can rapidly employ and learn from.
We will share methods for developing research tools, gathering data, and making the most of findings to inform your approach at key milestones in the production of apps, digital games, and websites. We will provide anecdotes from our own experiences to illustrate how these methods can pan out in the wild.
Participants will learn about research strategies including:
– Card Sorting- hone in on priorities and preferences
– User Testing- evaluate the response to your designs
– Surveys and Interviews- ask the right questions of the right people
– Observations- know what to watch for, and how to record what you see
Participants will work in small teams to identify a challenge of their own, strategically choose a research method, and adapt and test their instruments. Each participant will leave with tools and strategies that they can use to gather feedback for an informed and iterative design process.
This workshop is for producers, project managers, educators, designers, and developers involved in developing digital experiences.
http://www.museumsandtheweb.com/mw2015-workshop-an-introduction-to-agile-user-research-testing/
Programmers testing their own code is not a new phenomenon, but with the emergence of agile development practices and code craftsmanship, there has been a move towards Programmers visibly taking more accountability for the code they write.
This is great news for those Testers used to being the gatekeepers to quality and answering the “why wasn’t this found in test?” question.
Programmers and Testers are now helping to improve the quality of code, but there is still one anti-pattern I have observed in teams in which both Programmers and Testers are testing the code – they are not actually working with each other when establishing a unified testing strategy.
This results in gaps in test coverage and / or unnecessarily duplicated testing.
This slide deck is from my Agile North presentation.where I presented my ICEBERG model for helping Programmers & Testers work more collaboratively. I also introduced another model I use for helping teams work together - Virginia Satir's Interaction Model.
A basic primer on bringing Lean Startup techniques to technical teams and organizations. Talk centered on successful integration of engineers into small, cross-functional lean startup teams. Emphasis on addressing the resulting changes in the role of the engineer.
Optimizely Product Deep Dive: Experiment APIOptimizely
ERIC HIGGINS, SOFTWARE ENGINEER, OPTIMIZELY
Eric Higgins, software engineer at Optimizely, walks through some exciting enhancements to Optimizely’s developer platform.
Topics covered include:
Getting started with the API
Live demo
Example use–cases
The document discusses principles for agile software development. It advocates for an iterative development process of creating software, shipping it, observing user behavior, and repeating the process based on learnings. Specific principles discussed include not assuming the user's perspective, designing for target demographics, and focusing on passionate people to build software that users love.
Onboarding at scale @Booking.com focuses on improving the onboarding process for property owners through evolutionary experimentation. The presentation discusses testing individual elements of the onboarding journey, as well as combining elements, to identify the core value and pain points. User research is key to understanding problems and testing hypotheses. The goal is to help property owners achieve their goals faster by designing an onboarding experience that guides them through setup, use of the extranet, and accessing actionable data.
This document provides an introduction and overview for a 3-day mobile app programming workshop to teach participants the basics of MIT App Inventor. The workshop goals are to teach participants about user interfaces, prototyping designs, and coding screens in App Inventor, with the overall goal of building a mobile app. The introductions section has participants share their name, age, preferred mobile platform, favorite artist/song, and programming experience. The document then provides an introduction to MIT App Inventor and examples of apps that can be built with it, such as games, quizzes, texting apps, and location-aware apps. It outlines reasons for learning to code like software being used in many careers, and skills
When Feature Flags Go Bad : How Not to Have Feature Flags Be Used Incorrectly...LaunchDarkly
When Feature Flags Go Bad:How Not to Have Feature Flags Be Used Incorrectly for Disastrous Results - Edith Harbaugh, LaunchDarkly - Feature flags are a continuous delivery best practice to get feedback faster, with less risk. With feature flags, engineering changes are pushed live to production “off”, and then turned on to different users, separating deployment from release. Learn how Behalf and CircleCI to use feature flags for opt-in early access, private beta, canary releases and dark launches.
Girls Can Code is holding a meeting to discuss developing an app to raise awareness of sudden infant death syndrome (SIDS) by aligning the app idea with health facts and statistics about SIDS from a medical website. They will create an app description and demo video showing the app in use, with juniors learning App Inventor and seniors learning both App Inventor and C# programming. The group will delegate tasks, brainstorm a business plan, and create a pitch video with a storyboard, script, and clips to present their app idea.
This document discusses DevOps principles and practices. It introduces DevOps as a culture emphasizing collaboration between software developers and IT professionals to automate software delivery and infrastructure changes. It then covers various DevOps topics like continuous integration, deployment, monitoring and product validation practices. It also provides examples of applications that could benefit from a DevOps pipeline and asks the reader to design such pipelines.
The founders of Heroku started with a vision for a new model of web application deployment, but after an initial successful launch and funding round, they realized they had gotten ahead of themselves and hadn't found true product-market fit. They pivoted the company's focus to be exclusively on application programming interfaces and deployment for production apps on Git, which required a major overhaul of their product nearly from scratch. The founders learned that early success can distract from finding a scalable business model and that truly understanding your users and pivoting, even if it means cutting beloved features, is crucial for a startup's survival.
Gil Zilberfeld introduces himself and provides an overview of DevOps. DevOps emphasizes collaboration between software developers and IT professionals while automating the process of software delivery and infrastructure changes. The document discusses new challenges with cloud, serverless environments, and governance. It also covers DevOps practices like source control, continuous integration, testing, deployment, monitoring, and product validation.
Makers and Menders: Putting the Right Developers on the Right ProjectsAndrea Goulet
As presented at the PhillyETE conference in April 2017.
When you think of a developer what comes to mind? A brogrammer living in San Francisco working 23 hours a day on the next Facebook? If so, you wouldn’t be alone. Like so many industries, software development is rife with stereotypes. And one that is particularly pervasive is the idea that all developers, if given the chance, would opt for a complete rewrite of an application.
While it’s true that there are many software developers who do enjoy starting with a clean slate, there is also a group who loves working on making existing applications better. Rather than starting from scratch and building an 80% solution, these developers are ideal for taking over a project once it’s become stable, and nurturing it for a long time. Neither developer is better. Both are needed in the software world. In this talk, you’ll learn what motivates the small but passionate group of “menders” — people who love taking an existing project and making it better over time.
This document discusses the need for smart testing approaches for smartphone apps. It notes that smartphones are the first real consumable computing devices and have changed the way people live and how testing must be done. Functional testing alone is no longer sufficient, and performance testing needs to consider more than just speed. The document presents models for testing the user interface of smartphone apps and recommends tools for testing. It emphasizes understanding mobile technologies, exploring app design guidelines, and having faith that people will use tools effectively.
Use The Source Join The Force by Mark Steve Samson | DevCon Summit 2015 #GoO...DEVCON
This document provides guidance on contributing to open source software projects. It discusses reasons to contribute such as sharing knowledge, career opportunities, learning, and scratching personal itches. The document also provides tips on finding projects to contribute to, such as contributing to projects you already use or following notable developers. Finally, it outlines various ways to contribute, including contributing code, submitting bug reports and feature requests, improving documentation, providing support, and donating money. The overall message is that open source development benefits both individual developers and society by promoting collaboration and advancing technology.
The Cultural Changes of Feature FlaggingLaunchDarkly
Edith Harbaugh, CEO LaunchDarkly discusses the cultural changes that happen - not just in engineering but across the organization - when you add feature flagging to your development cycle and stop relying on long-lived branching. This presentation is from DefragCon 2016.
Understanding Technical Debt: A Primer for Product Owners and FoundersAndrea Goulet
As presented at ProductCamp Boston June 2017.
Technical debt gets accrued when you move fast and break things, which is awesome in the early stages of a startup. Left unchecked, technical debt can slow a development team to a grinding halt, frustrating founders and product owners. In this session, we'll demystify technical debt. You'll leave with a good understanding of what it is, when to accrue it, and how to pay it down.
QConSF 2017: DevOps 2.0 - When Everyone Can Run What's Built LaunchDarkly
The cultural change of “DevOps” beyond just developers and operations is just at the beginning.
What happens when an entire organization changes from shipping once a year to once a month, then multiple times a month, week or even daily?
How do developers approach a sprint when their code can be live in real time?
How does product management change when features can evolve daily?
How does marketing change when the features of tomorrow can be immediately influenced by response to messaging today?
We’re at the very beginning of thinking of code as a living object instead of a static file thrown over the wall.
Este documento presenta resúmenes y citas de varios monasterios españoles. Cada entrada incluye el nombre de un monasterio seguido de una cita o reflexión sobre temas espirituales como la fe, la paciencia, el perdón y vivir en el presente. El documento ofrece perspectivas de diferentes figuras religiosas a lo largo de la historia sobre cómo vivir de manera virtuosa.
This document discusses the costumes and props for an interrogation scene in a film. It describes that the terrorist will sit in an uncomfortable chair to appear uncomfortable during interrogation. It notes that the terrorist will wear a dirty white vest to emphasize his poor treatment, while the interrogator will wear an open white shirt and black trousers to seem important but unprofessional. It also mentions that the protagonist will wear normal clothes in an earlier bus scene.
Is data secure on the password protected blackberry deviceSTO STRATEGY
The document discusses vulnerabilities in password protection on Blackberry devices. It describes how malware could use keystroke emulation and screen capturing to steal passwords and sensitive information by injecting fake key presses or taking screenshots, even when devices are locked. It provides code examples of how malware could be written to exploit these vulnerabilities by accessing the Blackberry API. The document aims to demonstrate how easily private data could be compromised and provide education on securing devices and applications.
Este documento contiene una serie de citas y reflexiones cortas sobre temas como la vida, el aprendizaje, el cambio y la felicidad. Las citas provienen de autores como Shakespeare, Kierkegaard y Chaplin. El documento finaliza deseando un abrazo al lector.
Энергосберегающее решение основанное на технологии LoRaWAN Soloten Energy Saver. Простое и недорогое решение контролировать открытые окна в офисном здании.
This document provides an overview of mobile device management (MDM) and mobile security across different mobile operating systems. It analyzes the native security features and permissions models of BlackBerry and iOS, identifying both controlled and uncontrolled activities. For both platforms, it shows the number of main and derived activities, and calculates the efficiency of each platform's permissions and controls. The analysis finds that the set of permitted activities is typically less than the set of all activities, indicating opportunities for improvement in granularity and unknown attacks.
This document outlines a proposed project to promote civic outcomes for Chadian youth. The project aims to develop and implement a civic education curriculum for youth ages 16-24 in Chad to educate them about their country's political processes and history of violence and instability. The curriculum would be developed in phases, starting with fact finding and consensus building in Chad and the U.S., followed by development and implementation of the curriculum in Chad. The goal is to increase youth's political knowledge, attitudes, values and participation in elections to help Chad progress toward a stable democracy.
This document provides an introduction and overview for a 3-day mobile app programming workshop to teach participants the basics of MIT App Inventor. The workshop goals are to teach participants about user interfaces, prototyping designs, and coding screens in App Inventor, with the overall goal of building a mobile app. The introductions section has participants share their name, age, preferred mobile platform, favorite artist/song, and programming experience. The document then provides an introduction to MIT App Inventor and examples of apps that can be built with it, such as games, quizzes, texting apps, and location-aware apps. It outlines reasons for learning to code like software being used in many careers, and skills
When Feature Flags Go Bad : How Not to Have Feature Flags Be Used Incorrectly...LaunchDarkly
When Feature Flags Go Bad:How Not to Have Feature Flags Be Used Incorrectly for Disastrous Results - Edith Harbaugh, LaunchDarkly - Feature flags are a continuous delivery best practice to get feedback faster, with less risk. With feature flags, engineering changes are pushed live to production “off”, and then turned on to different users, separating deployment from release. Learn how Behalf and CircleCI to use feature flags for opt-in early access, private beta, canary releases and dark launches.
Girls Can Code is holding a meeting to discuss developing an app to raise awareness of sudden infant death syndrome (SIDS) by aligning the app idea with health facts and statistics about SIDS from a medical website. They will create an app description and demo video showing the app in use, with juniors learning App Inventor and seniors learning both App Inventor and C# programming. The group will delegate tasks, brainstorm a business plan, and create a pitch video with a storyboard, script, and clips to present their app idea.
This document discusses DevOps principles and practices. It introduces DevOps as a culture emphasizing collaboration between software developers and IT professionals to automate software delivery and infrastructure changes. It then covers various DevOps topics like continuous integration, deployment, monitoring and product validation practices. It also provides examples of applications that could benefit from a DevOps pipeline and asks the reader to design such pipelines.
The founders of Heroku started with a vision for a new model of web application deployment, but after an initial successful launch and funding round, they realized they had gotten ahead of themselves and hadn't found true product-market fit. They pivoted the company's focus to be exclusively on application programming interfaces and deployment for production apps on Git, which required a major overhaul of their product nearly from scratch. The founders learned that early success can distract from finding a scalable business model and that truly understanding your users and pivoting, even if it means cutting beloved features, is crucial for a startup's survival.
Gil Zilberfeld introduces himself and provides an overview of DevOps. DevOps emphasizes collaboration between software developers and IT professionals while automating the process of software delivery and infrastructure changes. The document discusses new challenges with cloud, serverless environments, and governance. It also covers DevOps practices like source control, continuous integration, testing, deployment, monitoring, and product validation.
Makers and Menders: Putting the Right Developers on the Right ProjectsAndrea Goulet
As presented at the PhillyETE conference in April 2017.
When you think of a developer what comes to mind? A brogrammer living in San Francisco working 23 hours a day on the next Facebook? If so, you wouldn’t be alone. Like so many industries, software development is rife with stereotypes. And one that is particularly pervasive is the idea that all developers, if given the chance, would opt for a complete rewrite of an application.
While it’s true that there are many software developers who do enjoy starting with a clean slate, there is also a group who loves working on making existing applications better. Rather than starting from scratch and building an 80% solution, these developers are ideal for taking over a project once it’s become stable, and nurturing it for a long time. Neither developer is better. Both are needed in the software world. In this talk, you’ll learn what motivates the small but passionate group of “menders” — people who love taking an existing project and making it better over time.
This document discusses the need for smart testing approaches for smartphone apps. It notes that smartphones are the first real consumable computing devices and have changed the way people live and how testing must be done. Functional testing alone is no longer sufficient, and performance testing needs to consider more than just speed. The document presents models for testing the user interface of smartphone apps and recommends tools for testing. It emphasizes understanding mobile technologies, exploring app design guidelines, and having faith that people will use tools effectively.
Use The Source Join The Force by Mark Steve Samson | DevCon Summit 2015 #GoO...DEVCON
This document provides guidance on contributing to open source software projects. It discusses reasons to contribute such as sharing knowledge, career opportunities, learning, and scratching personal itches. The document also provides tips on finding projects to contribute to, such as contributing to projects you already use or following notable developers. Finally, it outlines various ways to contribute, including contributing code, submitting bug reports and feature requests, improving documentation, providing support, and donating money. The overall message is that open source development benefits both individual developers and society by promoting collaboration and advancing technology.
The Cultural Changes of Feature FlaggingLaunchDarkly
Edith Harbaugh, CEO LaunchDarkly discusses the cultural changes that happen - not just in engineering but across the organization - when you add feature flagging to your development cycle and stop relying on long-lived branching. This presentation is from DefragCon 2016.
Understanding Technical Debt: A Primer for Product Owners and FoundersAndrea Goulet
As presented at ProductCamp Boston June 2017.
Technical debt gets accrued when you move fast and break things, which is awesome in the early stages of a startup. Left unchecked, technical debt can slow a development team to a grinding halt, frustrating founders and product owners. In this session, we'll demystify technical debt. You'll leave with a good understanding of what it is, when to accrue it, and how to pay it down.
QConSF 2017: DevOps 2.0 - When Everyone Can Run What's Built LaunchDarkly
The cultural change of “DevOps” beyond just developers and operations is just at the beginning.
What happens when an entire organization changes from shipping once a year to once a month, then multiple times a month, week or even daily?
How do developers approach a sprint when their code can be live in real time?
How does product management change when features can evolve daily?
How does marketing change when the features of tomorrow can be immediately influenced by response to messaging today?
We’re at the very beginning of thinking of code as a living object instead of a static file thrown over the wall.
Este documento presenta resúmenes y citas de varios monasterios españoles. Cada entrada incluye el nombre de un monasterio seguido de una cita o reflexión sobre temas espirituales como la fe, la paciencia, el perdón y vivir en el presente. El documento ofrece perspectivas de diferentes figuras religiosas a lo largo de la historia sobre cómo vivir de manera virtuosa.
This document discusses the costumes and props for an interrogation scene in a film. It describes that the terrorist will sit in an uncomfortable chair to appear uncomfortable during interrogation. It notes that the terrorist will wear a dirty white vest to emphasize his poor treatment, while the interrogator will wear an open white shirt and black trousers to seem important but unprofessional. It also mentions that the protagonist will wear normal clothes in an earlier bus scene.
Is data secure on the password protected blackberry deviceSTO STRATEGY
The document discusses vulnerabilities in password protection on Blackberry devices. It describes how malware could use keystroke emulation and screen capturing to steal passwords and sensitive information by injecting fake key presses or taking screenshots, even when devices are locked. It provides code examples of how malware could be written to exploit these vulnerabilities by accessing the Blackberry API. The document aims to demonstrate how easily private data could be compromised and provide education on securing devices and applications.
Este documento contiene una serie de citas y reflexiones cortas sobre temas como la vida, el aprendizaje, el cambio y la felicidad. Las citas provienen de autores como Shakespeare, Kierkegaard y Chaplin. El documento finaliza deseando un abrazo al lector.
Энергосберегающее решение основанное на технологии LoRaWAN Soloten Energy Saver. Простое и недорогое решение контролировать открытые окна в офисном здании.
This document provides an overview of mobile device management (MDM) and mobile security across different mobile operating systems. It analyzes the native security features and permissions models of BlackBerry and iOS, identifying both controlled and uncontrolled activities. For both platforms, it shows the number of main and derived activities, and calculates the efficiency of each platform's permissions and controls. The analysis finds that the set of permitted activities is typically less than the set of all activities, indicating opportunities for improvement in granularity and unknown attacks.
This document outlines a proposed project to promote civic outcomes for Chadian youth. The project aims to develop and implement a civic education curriculum for youth ages 16-24 in Chad to educate them about their country's political processes and history of violence and instability. The curriculum would be developed in phases, starting with fact finding and consensus building in Chad and the U.S., followed by development and implementation of the curriculum in Chad. The goal is to increase youth's political knowledge, attitudes, values and participation in elections to help Chad progress toward a stable democracy.
El píxel es la unidad mínima de color que forma parte de una imagen digital. Se utiliza para expresar la resolución de cámaras digitales y aparece como pequeños cuadros de color al ampliar una imagen. Picasa es una herramienta para visualizar, organizar y editar fotografías digitales con efectos y compartirlas en un sitio web integrado.
El documento habla sobre el avance de la automatización y la inteligencia artificial. Menciona que aunque la tecnología ha mejorado vidas, también ha eliminado empleos. Concluye diciendo que debemos asegurarnos de que el progreso tecnológico mejore vidas y comunidades en lugar de dejar personas atrás.
This document summarizes security issues and vulnerabilities across BlackBerry devices. It discusses how BlackBerry smartphones were originally more secure but newer PlayBook and BlackBerry 10 devices have simplified security controls. It analyzes how malware can exploit file system, application management, clipboard, photoscreen, messages, and device password issues. It also examines how third-party security applications and GUI exploitation could be leveraged by hackers. The document concludes that the vendor's security vision does not match reality and has been aggravated by oversimplification of permissions and controls.
Denver Startup Week: Product Management from the TrenchesSean Porter
This document summarizes a presentation on product management and engineering relationships. It discusses establishing trust between the teams through clear expectations around commitments, responsibilities, and priorities. Specifically, it outlines that product management is responsible for what is built, the desired user experience and priorities, while engineering determines how it is built and the technologies used. Maintaining open communication and establishing accountability helps avoid dysfunctions that can hurt productivity and results.
Nicolás Fernández will share tips and tricks for preparing and performing an effective "WOW effect" demo of Dynamics 365 Customer Engagement and the Power Platform. Some key elements to focus on include knowing the platform capabilities well, keeping demo environments organized, tailoring scenarios and data to the specific customer, and being prepared to adapt to changes or issues during the demo. The overall goals are to solve real business needs of the customer, showcase benefits rather than just features, and manage expectations appropriately.
Rima Gerhard is the lead Web Design instructor at the Miami International University of Art & Design. She has over 10 years of practical experience planning, developing, and testing web applications.
This is her presentation deck from Open Source Fashion's Conversion Conference at Venture Hive Miami on April 29, 2015.
http://freestyleconference.com
Simply having an API available isn't enough. This presentation covers how to ensure you maximize your returns from developer interest in your APIs. Presented at Apps World London, November 2014.
IA Ondernemen met innovatieve apps. Sessie 1 Frederik de Wachter Lean startupIkinnoveer
This document discusses lessons learned from various companies' experiences with innovation and startups. It provides summaries of lessons from companies like Agoria App Alliance, TapCrowd, and Barco. It also discusses concepts like living labs, constant innovation, the lean startup methodology, and rapid iteration. Various tactics for prototyping mobile apps are presented, like concierge prototypes. The importance of testing assumptions and pivoting based on feedback is emphasized.
Building mobile applications with Meteor: Eat Local case studyRizky Syazuli
This is the presentation material from a Meteor Meetup in Jakarta. It contains a preview of an app called Eat Local which was built using Meteor. Including all the supporting tools & softwares used to build it.
Additionally, i've also shared several links & references for general mobile app development using Meteor and learning the Meteor framework.
Eat Local itself is a campaign to increase the awareness of the importance of local food product. Visit ayoeatlocal.com to find out more.
User Centered Design: guarantee that your business process automation project...Bonitasoft
Wide user acceptance is one of the biggest challenges companies face when launching a new project, product, or service. Any of these can fail for a variety of reasons, but failure is often due to a disappointing user experience.
The process of User Centered Design actively takes into account the needs, expectations, and characteristics of end users at each stage of the development process, leading ultimately to better user satisfaction.
The tools and processes manager of a large French automotive group recently noted, "You have to be user-centric to successfully digitize your processes." End users can feel, “This was actually designed with me in mind - my wants and needs were actually considered before a tool was imposed on me to use.”
From layout to delivery of the first iteration and through continuous improvement, learn how to use the Bonita UI Designer as an iteration tool to guarantee an ideal match with the actual needs of end users.
video: https://youtu.be/vmZgeJ86738
Event and meeting planners are currently experimenting with technology – but if we are honest, many are only playing with event tech on the periphery.
The application of digital innovation to the meeting and events world has the opportunity to completely transform how planners create their programs and interact with their attendees.
In this deck, originally presented at IMEX America 2015, learn which innovations are available within the hospitality marketplace that will help planners create more effective and impactful programs for their business, and their attendees.
Learning Outcomes:
- Review the changes our profession has experienced through technology.
- Identify the meeting planning process pyramid and technologies that support it.
- Distinguish the three levels of data your event needs to measure engagement.
APIs have become ubiquitous and they have profoundly changed the way we connect to the world. They have opened the doors to enterprise back-end infrastructure and made it possible for developers to build innovative mobile applications. But this IT revolution comes with its share of challenges. “If we build it they will come” is no longer an effective API launch strategy. AnyPresence and WIP Factory are joining forces to share valuable best practices on improving API adoption.
How to Hire Flutter Developers in India Quick Guide.pdfLaura Miller
Flutter developers offer the best solutions to develop hybrid applications. Read the blog to know how to hire flutter developers in India for your project.
APIs for Internal Innovation - Getting the Developer Experience RightCarlo Longino
This document discusses best practices for creating an effective internal API program. It recommends (1) clearly defining goals for what you want developers to achieve and metrics for success, (2) understanding target users and their needs and building relationships, and (3) creating a positive developer experience through documentation, support and soliciting feedback. It also stresses the importance of (4) promotion to raise awareness of the API program using internal communication channels and success stories, and (5) flexibility to evolve the program based on learning. The overall aim is to develop an API program that creates mutual benefits for both developers and the organization.
This document describes a platform called Kachingle that bundles and bills for software applications. It discusses trends in software toward many heterogeneous applications from multiple vendors. Current business models do not support this. Kachingle's solution involves flexible bundling of applications, one-click licensing, usage-based payments to vendors, and micropayments to build bundles with thousands of apps. Live demos showcase bundling apps for MRI solutions and using Pivotal Tracker. The goal is to benefit both subscribers and app vendors.
Monetization platform for cloud, pc, mobile apps and content that includes virtual partnering, subscription management and billing, bundling and co-marketing. Based on our patent-pending micropayment engine.
Kachingle combines the three key technology inflection points occurring today in software:
- monolithic apps giving way to inter-connected specialized mini- and micro-apps,
- licensed "shelfware" software replaced by cloud-based business process subscriptions,
- purchasing and management of these services now in the hands of the users rather than the IT department,
...in a elegant easy-to-use platform that enables business users - from individuals to departments to enterprises - to build and manage their own tailored, flexible subscription-based app bundles maximizing their value from each app that they actually use.
Kachingle's target customers are the "owners" of cloud/mobile/IoT software platforms, ecosystems, and marketplaces, who can integrate Kachingle with their platform, offerings, such that their business customers can easily assemble, subscribe, and manage a plethora of apps and other related services across multiple public and private clouds.
This ease-of-use drives adoption and revenue for both the owners of the platforms and the app vendors.
Screen shots from two demos are included:
- MRI Neuro Imaging Apps for Radiology/Radiologist
- SaaS Apps
Gone are the days where marketers can only measure customer satisfaction. In today’s world, marketers need to make a business impact at every touchpoint. During this presentation, you’ll learn how to automate and leverage feedback at different stages of the customer life cycle. This session will dive into various topics, such as automatically triggering tasks for CRM account owners to follow up on answers and leveraging Marketo to set up all of your marketing survey needs.
You’ll leave with:
- Understanding various customer feedback scenarios so you can trigger follow-up
- Addressing a customer's lifecycle stage in Marketo
- Being able to impact customer satisfaction throughout their lifecycle
Gone are the days where marketers can only measure customer satisfaction. In today’s world, marketers need to make a business impact at every touchpoint. During this presentation, you’ll learn how to automate and leverage feedback at different stages of the customer life cycle. This session will dive into various topics, such as automatically triggering tasks for CRM account owners to follow up on answers and leveraging Marketo to set up all of your marketing survey needs.
You’ll leave with:
Understanding various customer feedback scenarios so you can trigger follow-up
Addressing a customer's lifecycle stage in Marketo
Being able to impact customer satisfaction throughout their lifecycle
APIdays Singapore 2019 - The Dark Side of Managing APIs as a Product, Martin ...apidays
Martin Buhr discusses the challenges of managing APIs as they grow in adoption and popularity. As APIs become more widely used, there is pressure to standardize them which can limit flexibility over time. There is also a risk of interface theft as happened in the Oracle v. Google case. API providers must consider how to protect proprietary functions, data, and competitive advantages while encouraging adoption and usability. The focus should be on using API data to improve products rather than just growing usage for its own sake.
The document outlines the process for working on a project with Hitori, including 4 main steps:
1. Wireframes - creating initial designs and getting client approval
2. Design - further developing the user interface design and getting additional approval
3. Development - coding and testing the technical aspects
4. Project - completing development, providing support, and closing out the project. Each step involves collaboration with clients to ensure their needs are met.
The intersection of Design Thinking and Agile - Talk at Academy Xi by Eryk Ko...Eryk Korfel
This document discusses how Design Thinking and Agile can be integrated. It provides tips for combining the two approaches, including investing in user research, basing user stories in user needs rather than implementations, using a Sprint 0 to build empathy, integrating designers into sprint teams, transferring knowledge between teams, and testing ideas with customers throughout the process. The goal is to apply human-centered design to problem solving while also adopting the Agile approach of iterative development.
The document discusses ensuring accessibility is considered throughout the agile process. It emphasizes including accessibility specialists and success criteria in the definition of ready and done to ensure user stories and features meet accessibility standards before being marked complete. It provides examples of how accessibility input and testing can be incorporated into artifacts like user stories, wireframes, and development tasks.
Similar to Digital Accessibility: Tips From the Met App Case Study @ MCN 2015 (20)
RPWORLD offers custom injection molding service to help customers develop products ramping up from prototypeing to end-use production. We can deliver your on-demand parts in as fast as 7 days.
Digital Accessibility: Tips From the Met App Case Study @ MCN 2015
1. Accessibility for Digital Products:
Tips from the Met App Case Study
Sina Bahram
President, Prime Access Consulting
@SinaBahram
Liz Filardi
Producer, The Met
@LizFilardi
4. @sinabahram @lizfilardiAccessibility for Digital Products / Met App Case Study
DO
…Research and define
objectives upfront.
…Include specific features
in your vendor contract.
…Test accessibility features
when approving the work.
DON’T
…Let your developer make
the decisions alone.
…Be afraid to make
accessibility a requirement.
…Wait until the end to test
all accessibility features.
7. @sinabahram @lizfilardiAccessibility for Digital Products / Met App Case Study
DO
…Define scope and
process before you start.
…Factor in time to do skill
building with your team.
…Test with experienced
usability testers.
DON’T
…Wait until the usability
testing to determine scope.
…Pressure your developer to
add accessibility at the end.
…Test with any random
person with disabilities.
8. @sinabahram @lizfilardiAccessibility for Digital Products / Met App Case Study
The Met app launches.
SEP 2014
Version 1.1 is released
with support for accessibility.
JAN 2015
10. @sinabahram @lizfilardiAccessibility for Digital Products / Met App Case Study
DO
…Discuss the ROI of
acquiring universal design
skills.
…Share goals and progress
with stakeholders.
…Challenge each other to
do better next time!
DON’T
…Describe accessibility as
another pesky task.
…Assume stakeholders
wouldn’t understand or don’t
need to know.
…Get discouraged if you
miss the mark.
11. @sinabahram @lizfilardiAccessibility for Digital Products / Met App Case Study
“Establish common standards and
guidelines for products and activities
across the department … will include …
Accessibility Guidelines.”