Home Creators Posts Import Register Favorites Logout

Content

Another small batch of fixes and tweaks. Thanks so much to everyone that's sent in feedback from the open beta. Please keep it coming!

Next up, I'll be posting a detailed write-up on what to expect with your data migrating over to the remake from the current site (not the demo) at launch.

There's a few more bugfixes in the pipeline too.

---------------------------------------------------------

New to the Patreon? Everyone can check out the open beta at backloggery.club. The beta's data is not connected to the current site and will not carry over to the public release. You can see current plans and known issues on Trello.

---------------------------------------------------------

v0.13.2 Patch Notes

Improvements

  • Notifications: when clicking the notifications bell, removed the pop-up notification list with limited functionality in favor of redirecting directly to the Multitap notifications tab. Added unread marks to notifications and a "Mark All As Read" button.
  • Fixed various typos, outdated terms, alignment issues, etc. from open beta feedback. Too much to list!

Bug Fixes

  • Backlog: removed placeholder Challenge Runs button. (mastered games will instead be put into a list during the data migration)
  • Profile: hide block button on user's own profile
  • Add Games: going from another user's profile to the Add Game page no longer breaks the page

Comments

Aaron Mood

A little UX annoyance I've run into. After you select a system on the main backlog tab it doesn't auto-scroll you to the top of the list. Kind of annoying on its own, but when the console has only a few games it can be especially disorienting. Here's what I see when selecting Sega Genesis: https://imgur.com/a/0awUXwc The two games are above the fold, so it looks like the page went blank. Excited for the migration! EDIT: I'm just realizing why this is an issue. lol My bio is so long that expands the screen. If my bio is collapsed, selecting a low count console obviously readjusts the window to fit the little information that is displayed.

eishiya

I was thinking of having a look at the beta, but it requires Javascript to display *anything*. One of the things I really liked about Backloggery was that it displayed fine without JS, even if some non-critical features didn't work. It looks like the new one relies on JS for *everything*, even its basic HTML. That's a shame - it messes with indexing/searchability, makes it harder to save a snapshot of a given page, and doesn't play well with some more basic browsers. I consider JS used this heavily to be an accessibility issue. I know there are some good reasons for this (such as lighter load on the server), and that it's probably too late to "fix" this, but I'd be remiss not to complain about it anyway xP --- Something odd I noticed on the demo profile: When going back and forth between pages, the "2023 backlog ^ 9" bit on the "backlog" page takes a moment to fill in, while everything else seems to display immediately. The loading circles also flash briefly as data is loaded on other pages, which looks odd when the data actually loads quickly. If possible, consider having the loading circles appear after 50ms or so, or fade them in gradually, so that they only really display when the data is taking a while to load, rather than appearing for a single frame and looking weird.

Joe Murray

Yeah, I don't disagree with any of that. As you alluded, the benefits just made it too hard to pass on the modern JS frameworks, especially for a one-man team on very limited resources. I don't really care about the SEO, but I do hate the hit to accessibility and compatibility. Nice idea on the loading spinner. I'll do that.