Yeah, I understand that everything can’t be loaded at the sam time, but this is not the solution. The reason to browse by chronological order, from oldest to newest, is so that I don’t miss posts. But on everey single microblogging app, decentralized or ran by a lunatic wit too much money, there is the barrier between the last few new posts, and where you last left reading.

The eorst part: this loads the newest first, and prefers to push you to the top, requiring you to search where you actually left off.

How about we just have a button to “go to the newest” that throws you to whatever has been published within the 5 minutes, and assume if you’re browsing from bottom to top, you want more to be shown, but properly chronologically.

  • AnalogyAddict@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    11 months ago

    As a UX designer, the first part is part of the reason. Companies actually “want” you to continue to scroll and to click the view more button. Every time you view more, they get more ad revenue and more data.

    Endless scrolling is an accessibility and data conservation nightmare. It’s also arguably grey UX, as it encourages scrolling addiction. Having the user have to make a decision to load more saves the user data, and keeps the page from shifting context without user input. Global apps should consider the needs of the bulk of the world, which is still on pay-for-data plans.

    The answer tends to be to also implement server-side sort and filtering that includes “show new.”