Collaged sketchnotes of Whitney Hess' keynote at Drupalcon LA
Langs de lijn
Utrecht – Hilversum
Soms kom je ze nog tegen, mensen die de bliebjes van bediening van hun telefoon nog aan hebben staan.
View from the window upstairs.
Leonardo, de mens en zijn kunst
Melle maakt z’n werkstuk over Da Vinci. Wat materialen geleend bij de bibliotheek, deze van Bramly bij de grotemensenboeken. Wat een tragische held. Zijn tijd zo ver vooruit, zo'n diep en breed talent en toch (of juist daarom) erg weinig werken tot een goed einde gebracht. Die onrust van het altijd maar zoeken en onderzoeken wordt heel invoelbaar gepresenteerd.
Ik herinner me een titel uit de bibliotheek in Rotterdam van tijdens m’n academie: I Leonardo, een zeer vrije interpretatie van Da Vinci’s leven door Ralph Steadman. Ook daar herinner ik me vooral die voortdurend onrustige geest en de machteloosheid tegenover duizenden ongeorganiseerde pagina’s aantekeningen, studies, schetsen.
Leonardo, de mens en zijn kunst is zeker een aanrader om eens voorbij de Mona Lisa te gaan en echt kennis te maken met een waar genie.
Expositie = ingericht
Afgelopen dagen het werk ingelijst en opgehangen. Sorteren, groeperen, passen, meten. Bijzonder om je eigen werk zo terug te zien. Inlijsten is ook een onderdeel van de prent zelf. Geeft nog weer meer definitie, letterlijk inkaderen van waar het werk begint en eindigt. Dan de collectie groeperen. Wat hoort bij elkaar, wat zet je tegen elkaar af? Welke volgorde creëert het beste ritme, in welke onderlinge groepering komen de werken het best tot hun individuele recht?
Superveel dank aan Martijn van der Blom die met zijn poëtisch timmermansoog en tomeloze inzet enorm geholpen heeft om van een stapel werk een heuse expositie te maken.
Ik ben blij met het resultaat. En met resultaat bedoel ik niet alleen de prenten zelf. Maar vooral de hele route er naar toe. Het maken, uitkiezen, inlijsten, presenteren. Wat ik zie is dat het werk die investering kan dragen. Ik sta er volledig achter. Natuurlijk, morgen opening en ik ben benieuwd naar de reacties en natuurlijk, het werk is te koop. Maar dat het een succes is staat voor mij al vast. En dat ik dat hier zo stellig durf op te schrijven is de echte winst.
Hier, dit heb ik gemaakt. Ik zou het leuk vinden als je kwam kijken. Grafisch Atelier Hilversum aan de Noorderweg 96b in Hilversum, vanaf 15.00 uur. Van harte welkom!
Links for week 6, 2015
A good and good looking checklist for producing good digital design. With 3 activities for each of the stepsResearch, Plan, Communicate, Create, Give feedback, Finalise, Delight, Analyse. Good links to all over the internets for more detail. Via @Una
“Somebody gets into trouble, then gets out of it again. People love that story. They never get tired of it.”
ScientiaMobile has published MOVR to provide the mobile Web community with timely information on mobile Web device usage.
Bringing together designers and open source projects.
Sign your PDFs from within Preview on OS X
You can sign PDF documents from within the Preview application on OS X.
1. Make the tool visible by choosing View > Show Markup Toolbar
2. Find and click the squiggly icon. You can then choose how to create your signature. You can use the trackpad directly or write your signature on a piece of white paper and use the built in camera to take a picture of it.
3. Your digital signature is now available from the squiggly icon. Choose it and it will be added to your PDF.
4. You can then scale and move it to the right spot. Handy!
The Preview app has more useful features like this. You can add text, draw free form lines or smooth arrows, add some basic shapes and notes. Explore that Markup Toolbar.
Join open source design
One of the challenges in getting open source projects and designers to find each other is that communication channels for each of the two seem to have very little overlap.
The best bet from the open source project perspective is probably Github. If you’re interested in whatever intersection of design and open source, (create your Github account and) come on over and say hi.
What would be a similar starting point from the design community perspective?
What kind of design?
It helps to be specific about what kind of design expertise your open source project would benefit most from.
- Branding? For when you want a more focussed, professional, appearance. Update the logo, define identity guidelines, design the project website.
- Interaction design? Improve the workflows in your app. Optimise form layouts, decide what goes on each screen and how you get from one to the other.
- Information architecture? Structure information, reorganise the (marketing, documentation, forum) sections of the website, define a content strategy and maybe some copy writing.
- Interface design? Bootstrap only gets you that far. Bring the interaction design to life with clear and consistent styling.
- …and then some, but these four make for a good first check.
Start tagging issues that you think would benefit from design input with a general “design” tag. You can then point the designer to those issues. This makes it a lot easier for the designer to tell where to start with what kind of design work to make a useful contribution.
This post triggered by Garth who did this quick check with somebody while chatting in the #opensourcedesign channel on IRC, which you should join too.
FOSDEM 2015 slides
The first open source design room at FOSDEM was a big success!
Thank you to all who attended my talk about bootstrapping ux design in your open source project. We did’t get the streaming setup working until later that day, but Lewis posted his notes. My notes from some of the other sessions are here.
Pablo Cúbico – Every Pixel Hurts
Is there even such a thing as open source ux? How can we open up the processes of design to open source.
Pablo bravely goes on to define what UX is. Obviously, it’s about the user. UX is the experience a user has while using a product. It can be measured, it can be improved and it can be developed and designed.
Then there is also good user experience, like with swimming flippers: symbiotic, prosthetic, uninterrupted, continuous.
- UX itself is not a process, but it is an attribute of your product. UX design is a process.
- UX is not (just) beauty
- UX is not (just) UI. Visual, interaction design, user testing, performance, etc.
- UX is not: dropping in an asset library and Bam: UX!
Open source UX sucks, why?
- Only few designers participate
- No clear path for contribution
- Developers don’t know where to start
- Disconnected lone rangers
- (Visual) style differences
- “Can I haz” feature requests
- Everyone is a designer
- Customise all the things
- No proper tools
- No T-shaped devs/designer hybrids
- Code health (messy front end code)
- No room for you
- No visibility
- Assumptions, assumptions
- Resistance to change
Getting involved is mostly a social thing
- Invite yourself to the party
- Identify some measurable problems
- Do some work to show your expertise
- Be bold, we can always do less
- Be humble
- Start small
Jan Holesovsky – LibreOffice Design Team
LibreOffice UX team doesn’t have a rigid structure. Channels are mailing lists, IRC, issue tracker and the git repository. The team has defined some concepts they strive to adhere to:
Provide a platform for conflict resolution
Consider all the different views that people have about what is “better”. First step is to try and find consensus. If that fails, search for usage statistics or existing patterns. Working on a HIG, documenting user interface standards. Using the Gnome HIG as the basis. In the end, a decision will be made and reverted if it really doesn’t work
The task is finished only when it gets included in the git repository. Implementation is key. Ideally, people push those code changes themselves. There is Gerrit, a code review system to help automate some of the work.
Avoid bike shedding. Most discussions start in the bug tracker. When a discussion gets out of control the discussion is moved to a faster, more realtime channel like IRC or G+ Hangout. There are also weekly G+ hangouts for two or three hours (6–7 participants).
Maybe you don’t even know you are already part of the design team. Weekly reports on UX changes that were implemented. Highlighting those efforts is very much appreciated.
Open to change
Changing or removing user interactions is hard, have to be careful about breaking existing workflows. Ongoing refinements and cleanups are very important to keep doing.
New in LibreOffice 4.4
- Complete overhaul of the 1000+ icons. It’s the new default for OS X, available on other platforms as well
- New approach to templates, now part of the start center.
- Improved color selector and toolbars, style dropdowns
Michael Demetriou – The challenges of open mobile design
Michael starts out with the famous “a camel is a horse designed by committee” analogy. But a camel is not a broken design, it is perfectly fit for the environment it lives in. Committee designs are usually more broken than the average camel.
The most iconic designs are works of a single person dictating what the end result is going to be. How does that apply to the open source bazaar? Have a grand vision to work towards, an idea for what the ideal, perfect version of your project looks like. Make decisions that work toward that vision. Some trade-offs have to be made to keep the community engaged, but as a designer you have to defend your right to reject seemingly good ideas that do not work towards the vision.
Make sure that the whole team speaks the same (design) language. New people will get the same advice, even if the lead designer is not around at that specific moment.
Michael then demonstrated the Nemo Mobile OS that can be installed on Android devices. A main feature is the configurable, app specific header bar. One of the apps functioned as a style guide showcasing available interaction design patterns.
Hollie Lubbock – UI design for open data
How design can help communicate open data
If you’re not good at number crunching, open data is not easy to interpret and learn from. Visualising it with maps and graphs makes it much more accessible. The data has to be good from the start though.
Can infographics save lives? Probably yes. Florence Nightingale mapping causes of death. London Underground map…
- Strive for simplicity and clarity
- Allow users to make up their own mind
- Inspire people to create something with the data
Who is using open data?
Cultural sector is a big adopter of open data and semantic web technologies. For example museums, they have a responsibility to not only store the data somewhere, but to also make it accessible to a larger audience.
The data sets drive the collections searches on their own sites. Social media integrations make for fun interactive applications. For example, see Dimensions of art by @jradavenport.
Common thesauri being developed. Hack days to get more people involved within limited budgets. Considering to make open data a requirement for government funding.
Museums typically create guided tours, which are pre-selected and pre-arranged. This was not always the case. In earlier times, the walls were full with a lot of paintings all over the place and you get to . Open data allows to recreate some of that choose-your-own-adventure approach.
Hollie then showed some of her work. A museum project where the whole team worked in an open, glass space at the museum where the audience could see how a web team worked. Even posting the designs up on the pinboards for everybody to look at and give feedback on.
We should be helping people to engage with open data and data a in general as much as possible. Design can help lower the barriers.
Björn Balasz – The problem of representativity, challenges of user centred work in FLOSS projects.
Björn discusses some of the issues he sees in open source design work and will propose a way to fix.
You want to create great products? Then focus on your users. Problem is there is no one single typical user to make happy. There are many different people with different expectations. So you can’t ask them directly. Instead we introduce an abstraction in the form of personas and other artefacts (vision pieces, testing results, style guides). These abstractions are necessary because otherwise you’d be solving a problem with too many variables.
What’s the problem in open source here? There is no research data on the users! If you don’t know who your users are, you can’t abstract them into personas and thus you cannot create an optimised product for them.
An idea for a solution. Because IRC, bug trackers are not the right tools for taking care of your relationships with your users.
Introducing User Relationship Management.
You need to seduce people to participate in improving open source software. What if your software would actively thank you for using it and provide a link to find out why you are thanked. This would start a quick survey that asks people to rate the software. A quick initial round of feedback is achieved.
Offer adequate options for participation. After the first single input feedback, after some time add another prompt asking to fill out maybe a 5 question survey.
It’s about slowly turning a passive user into an active participant.
There would also have to be a backend to this to analyse and review the input and use it to model your personas and evolve them over time.
Sign user-rights.org and help this become real!