HackerFriction Feedback

Products · Product

TechCrunch

Raised as a usability problem by 123 people on Hacker News over 17 years (2008–2024), in 110 threads.

Ranked by people · period

No issue was raised by at least 3 people in 3 threads this year.

No issue was raised by at least 3 people in 3 threads in the last 5 years.

  1. 1
    Back button is hijacked, so going back doesn't workUnreviewed

    13 people since the beginning · 10 threads

  2. 2
    Scrolling an article redirects reader to the homepageUnreviewed

    12 people since the beginning · 10 threads

  3. 3
    Pages take ages to loadUnreviewed

    11 people since the beginning · 7 threads

  4. 4
    Opt-out options in consent pop-up are hard to findUnreviewed

    7 people since the beginning · 7 threads

  5. 5
    Articles split across single pages, forcing extra clicksUnreviewed

    4 people since the beginning · 4 threads

  6. 6
    Reaching page bottom loads next story and blocks scrolling upUnreviewed

    4 people since the beginning · 4 threads

  7. 7
    Giant header image pushes article content out of viewUnreviewed

    3 people since the beginning · 3 threads

  8. 8
    Text vanishes and reappears, disrupting readingUnreviewed

    3 people since the beginning · 3 threads

  9. 9
    Article text is too small and thin to read on phoneUnreviewed

    3 people since the beginning · 3 threads

Every issue, all time, most people first

  1. Back button is hijacked, so going back doesn't workUnreviewed

    13 people since 2019, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 3 people2020: 10 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  2. Scrolling an article redirects reader to the homepageUnreviewed

    12 people since 2018, in 2 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 7 people2019: 6 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  3. Pages take ages to loadUnreviewed

    11 people since 2010, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 5 people2011: 5 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  4. Articles split across single pages, forcing extra clicksUnreviewed

    4 people since 2011, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  5. Reaching page bottom loads next story and blocks scrolling upUnreviewed

    4 people since 2018, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 2 people2019: 1 person2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  6. Giant header image pushes article content out of viewUnreviewed

    3 people since 2013, in 4 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 1 person2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 1 person2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  7. Text vanishes and reappears, disrupting readingUnreviewed

    3 people since 2012, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  8. Article text is too small and thin to read on phoneUnreviewed

    3 people since 2011, in 3 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?

This list counts all time; the period switch above only changes the ranking. Each issue is a group of similar complaints raised by at least 3 people in 3 different months and threads. Each line under an issue is Claude Haiku's summary of one of its latest comments, not a quote; follow it to read the comment on Hacker News.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 50 complaints