[06:18:38] [1/12] Assorted feedback and some nits on the reviewer, not from a reviewer point of view but a designer. Overall I like this! [06:18:38] [2/12] - Review link is a bit hard to hit, maybe it could be blown up to the entire cell size? In addition, the loading doesn't have instant feedback. A way of doing this could be having a loading bar, or potentially easier, making the link/button greyed out immediately after the press during the lod. [06:18:39] [3/12] - The dropdowns could be blown up a lot (see Material 3 selects) so that it's easier to hit with the mouse fast. Maybe it shouldn't be going at such a fast pace you'll be flicking a lot, but it definitely reduces mishits [06:18:39] [4/12] - Dropdowns could always be below labels, so they're in a consistent spot and easier to hit, because clicking on the label doesn't open the dropdown [06:18:39] [5/12] - The Discard and Save Draft buttons are a bit small. Maybe they could be blown up to something like 36dp, then have a touch target inflating them to 48dp? [06:18:40] [6/12] They could also just be made bigger, because they are often used buttons. [06:18:40] [7/12] - The discard button might be more glanceable as a destructive action if the background is red, with white text on top. An icon may also help differentiate them. [06:18:40] [8/12] Sidenote, likely out of scope and more relevant to the actual review system, I'm wondering if there is enough vertical space to always show the reason field, and remove a click from Accept/Deny? I attached a mockup of what I mean. [06:18:41] [9/12] - On the line of what Carrots said, I propose hiding the comments section before "Action (ignoring comments):" and it's reason are filled in, or explicitly marked as N/A. [06:18:41] [10/12] Reviewer flows I see: [06:18:42] [11/12] - Reviewer reads request, reads comments, accepts ignoring comment (one click instead of two), types a reason, then chooses Interrogate for action including comments, types a reason, copies. The 2x2 grid also minimizes the amount of fine aiming needed to hit the menu items when going through this fast. [06:18:42] [12/12] https://cdn.discordapp.com/attachments/1225560610628964423/1565248472679186554/Untitled-2026-07-24-1012_2.png?ex=6ae436bc&is=6ae2e53c&hm=66d8a39b6fe28b497e08a57ce883a2091e59e4c0e90a076e4ce731a7253f7973& [06:21:33] [1/2] Forgot to mention, maybe increasing spacing each individual control may help the increase scanability. When I initially looked at this, I got confused whether reason was for the above or below dropdown. [06:21:33] [2/2] https://cdn.discordapp.com/attachments/1225560610628964423/1565249212508016650/Screenshot_20261029-002003.png?ex=6ae4376d&is=6ae2e5ed&hm=efd842de222dc853cee71404eba74b3e95f4e7237452bfd5ab82de4059b9d67d& [06:22:32] That mockup is an interesting idea, but I don’t think I can feasibly do it because those choice are just from my default template. Users are very much encouraged to make their own templates that fit them better [06:22:53] I still think interrogate is quite a hostile word, inquire might be better. [06:24:14] I agree inquire is better, I used interrogate in the sense that I’d use an interrogative because I couldn’t think of a better word at the time [06:25:38] I really appreciate the feedback too btw [06:27:24] In terms of making things faster to interact with I’m somewhat torn. You probably didn’t notice but there’s actually no way to load another page of requests, and I’ve done that intentionally because doing more that 50 practice reviews in a day is definitely excessive. I want to encourage people to take their time and give the reviews the care and intentionality they deserve. [06:29:36] The reason discard looks that way is because I stole the styling from the cancel button in the source editor, which I figured would have the benefit of consistency, but I’ll experiment with it [06:41:40] [1/4] Hmm... in that case, if the intent is to want people to not rush, I have this idea? It's inspired off some text examination experiences. It's theoretical, and I also don't know how it would work with the template system. Maybe the reviewer can customize their flow somehow. [06:41:40] [2/4] When starting a review, the full area is taken up by the request for you to review. There is nothing else in the area, except for a Next button, but at the very bottom after you finish scrolling. This is to incentivize reading the entire thing carefully, also used in things like Terms of Service dialogs. [06:41:41] [3/4] Next button brings you to a split pane view of the request on the left, and the act-nocom, reason-nocom on the right. The reviewer can refer back to the request for citations or specific examples when making their verdict or writing a reason. [06:41:41] [4/4] After that, all three panes are displayed. To avoid skipping or overlooking of the lower down comments below the fold, maybe comments could be "collapsed" with a maximum character count by default, then you click to expand them? Then the other comments that are not from CreateWiki AI are visible above the fold. [06:43:36] Maybe what's making it harder to tell for me is the 3D bevel style borders combined? Maybe it'll be easier to see using the Codex CSS button classes. [06:45:57] That’s a pretty neat idea. For my template in particular having comments hidden is kinda awkward of you then realize that the request was edited and you can’t review as though the comments weren’t there. I’m currently working on some other things but I’ll look into adding this flow [14:50:00] What about "question" or "clarify"? [15:05:07] Any such word would work, it honestly doesn't matter that much. [16:22:52] alright, you guys caught me at 2:30 am when this happened, but the change has been made now