Getting started and progressing with design is intimidating but it need not be, talk will guide listeners to apply design thinking and make their FOSS projects better.
If a developer / product owner searches for design help today, they are likely to get "help" that complicates the basics. Blogs and other materials will miss the original context of the problem. Context is very important because design solutions are specific. There is a world of difference in designing an app like NAMMA YATRI v/s BHIM UPI.
While volunteering with FOSS United I've noticed a huge interest towards design, FOSS projects maintained and contributed by our community could also be made better with design thinking. This talk aims to nudge listeners to hopefully apply design thinking to their projects. The structure of the talk is as follows:
Product design another loaded term with changing responsibilities depending on who you ask. The introduction will ease our audience to an accessible version of it.
UX / UI / AI - we'll cut through all jargon to focus on the most important bit- people using software.
We'll go over ordering a product online, tracking an order, getting the product , dealing with customer support, setting up a return etc...
finally concluding with the various ways design thinking has helped shape up the shopping experience.
We'll go over 4-5 examples of applying improvements. This will be of increasing complexity:
- Starting with a good readme file, commenting inside code, applying design basics
- Moving to UI -following basic accessibility guidelines ( ACPA, WCAG ),
- Taking advantage of templates, using a standard design grid, and how to use the best of resources available to the listener.
- Seeking and filtering the 'right' feedback.
Questions will be highly encouraged and taken in person, after the talk.
____
Reference:
Sample deck -
https://www.figma.com/proto/jiIJzW51tz9F4NLvlRGHBG/Everybody-Can-Design-(-sample-deck-)?page-id=0%3A1&node-id=13-73&viewport=-939%2C195%2C0.22&t=rZRyEzHwS1hl8syR-1&scaling=min-zoom&starting-point-node-id=13%3A73
Session reference does not allow more than 140 characters, so I pointed it to my linkedin page, sorry for that :)