I am proud to announce iFixit Answers, a collaborative repair community of people helping people make devices work longer. We are launching the private beta today, but we will be inviting more people throughout the testing period. To get an invite, add your name to our list (we’ll be sending out invites to people on the list as we have room) or, if you want to be bumped to the front of the list, write a teardown!
The world has a problem with rapidly consuming devices and tossing them aside, ignoring long-term environmental impact. With your help, we are going to change that. I’m confident that we can change our culture of ephemeral ownership.
iFixit has helped hundreds of thousands of people fix Apple hardware. Just last month we shared our repair knowledge with over a million people in 175 different countries. Our internet-scale troubleshooting and repair documentation has made electronics repair accessible to people all over the world. In this new and exciting time, you can leverage your knowledge about hardware to make a difference not just to people next door, but to communities halfway around the world.
Answers is a natural progression from our successful forums. The community will have complete control over the content on Answers, and the system will be collaboratively managed by you, and other people like you. Every question and answer can be voted on by anyone and edited by members of the community.
As we were designing Answers, we had four guiding imperatives:
- It’s important that posts get more useful over time. It’s not uncommon for a traditional repair forum response to become the canonical source for an answer to a problem, only to get outdated and stagnant as technology changes.
- It’s important that we recognize expertise. It matters if the author of an answer is a professional technician, or has helped 200 people fix their problems.
- It’s important to make helping people fun. There’s a rush that comes from helping someone solve a tricky problem, being recognized by people for the research you put into a question before asking it, or testing your hardware diagnosis mettle against others.
- And most important, we need to close the feedback loop between the people answering questions and those asking them. Repairing things is uniquely tangible — when you use a solution proposed by someone, you know for a fact whether or not it worked. Finding out that the answer you gave someone actually fixed their problem is one of the greatest feelings in the world.