# Example: Piper Redesign

**URL:** <https://discourse.opensourcedesign.net/t/example-piper-redesign/986>\
**Category:** Interaction design\
**Created:** [March 30, 2019, 6:29pm UTC](https://discourse.opensourcedesign.net/t/example-piper-redesign/986 "2019-03-30T18:29:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdittrich](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/jdittrich/32/42_2.png) [@jdittrich](https://discourse.opensourcedesign.net/u/jdittrich)\
**Post date:** [March 30, 2019, 6:29pm UTC](https://discourse.opensourcedesign.net/t/example-piper-redesign/986/1 "2019-03-30T18:29:00Z")

</div>

I just came across this [example for the user friendly redesign](https://www.hjdskes.nl/blog/gsoc-part-15/) of a tool, [piper](https://github.com/libratbag/piper), which allows users to configure gaming mice (with sometimes elaborate functionality).

Design-wise, the sections on the [buttons-page](https://www.hjdskes.nl/blog/gsoc-part-15/#the-buttons-page) and the [welcome screen](https://www.hjdskes.nl/blog/gsoc-part-15/#the-welcome-and-error-screens) are most interesting.

It also is an example for the principle, that design changes in open source projects are easiest/most likely to succeed if one does _design and code_, as the coder/designer in this project. (Which @htietze once described to me as design in open source is DIY and which fits some of the [problems of open source design](https://discourse.opensourcedesign.net/t/difficulties-of-design-in-open-source/787/3?u=jdittrich). )