UI / UX, Security, and Documentation Issues

[7Hemant]

1. Prompts/Review Page – Dropdown Loader Issue

On the Prompts/Review page, in the Reviewing dropdown field, when selecting any value, the screen goes blank for a brief moment (milliseconds). During this time, no loader is shown in the UI. After the blank screen, the loader starts displaying.

2. Review Flow & Feedback Management Issue

• On the Review screen, there is a Skip option to skip a prompt. However, if a user clicks the Good Prompt or Bad Prompt button instead of Skip, there is no way to undo or remove that feedback.
• On the My Activity page, users who want to remove a previously submitted feedback do not have any option or button to do so.

3. Security – OpenRouter API Key Storage

Is it safe to store the OpenRouter API Key in localStorage?

4. Layout Issue – Screen Height Overflow

On both the Home page and the Prompt/Review page, the screen height is overflowing even when there is no content. There is a lot of unnecessary empty space visible at the bottom of the page.

5. Pagination Issues

The pagination does not include a page number dropdown, so direct navigation (e.g., from page 1 to page 5 and vice versa) is not possible.
Only Previous and Next buttons are available. When clicking the Next button, the page changes, but the new page remains scrolled to the bottom instead of scrolling back to the top.

6. Codebase Documentation

The codebase lacks proper documentation. Due to this, it is difficult to study for user, understand, and execute the project locally.

[anushabukke]

Re: Issue 1 - The millisecond delay is negligible, and we already have skeleton loading right after, which doesn't impact UX. I don't see this as something that needs fixing.

Re: Issue 2 - Valid concern. Once feedback is submitted (Good/Bad Prompt), users can't undo it. Adding an undo/edit option would improve the experience and prevent accidental submissions from being permanent

Re: Issue 3 - Confirmed that the API key is stored in localStorage, which is a security vulnerability. We should migrate to a more secure storage method. This is a valid security concern that needs to be prioritized.

Re: Issue 4 - Confirmed. There's excessive empty space at the bottom of both Home and Prompt/Review pages, even without content, causing unnecessary overflow. Valid UI issue.

Re: Issue 5 - Confirmed. Two issues here:
Missing direct navigation - No page number dropdown/input makes jumping between pages inefficient
Scroll position bug - Pages don't scroll to the top after navigation, leaving users at the bottom
Both impact UX. The scroll-to-top issue should be a quick fix, while adding page number navigation would be a nice enhancement.

Re: Issue 6 - We have documentation and .env.example, but agree it could be clearer for new contributors. The setup steps need better explanation.

[reisepass]

on 3 , the system is designed for users to put their own keys hence its fine if they see it in local storage. Right now when someone makes an account AND validates uni email we auto generated an isolated openrouter key just for them with 1$ budget on it. So I think this is acceptable design.

Remember that peerbench is designed to be decentralized so others can run a version of the same code as well. Everything is client side such that the peerbench server operator it self does not have control over people's data or results

[anushabukke]

on 3 , the system is designed for users to put their own keys hence its fine if they see it in local storage. Right now when someone makes an account AND validates uni email we auto generated an isolated openrouter key just for them with 1$ budget on it. So I think this is acceptable design.

Remember that peerbench is designed to be decentralized so others can run a version of the same code as well. Everything is client side such that the peerbench server operator it self does not have control over people's data or results

Got it! Makes sense given the decentralized, client-side architecture and the isolated $1 budget keys. The localStorage approach aligns with the design philosophy of keeping control with users rather than the server operator. Thanks for clarifying - not a security concern in this context.

[7Hemant]

Thanks for the information.