# UI Feedback

By [Lenson](https://paragraph.com/@lenson) · 2022-05-24

---

As a frequent user and a manager of a snapshot space from a small community, I’m very pleased to see my previous suggestions are being realized gradually by the amazing team and how snapshot keeps contributing to the success of DAO governance.

From the times I can tell, it’s getting better and better in its **optimized creation flow**, **new** **quick access sidebars**, **notification dropdown**, **enhanced hovertips** and my favorite **personal profile** feature showing one’s voting history that I’ve never expected to launch this soon!

I want to write this feedback as a follow-up of what I’ve submitted earlier this year before, from the voice of a long-term user, and also from my community members, sincerely wish these ideas will help snapshot go better in the coming future.🌟

* * *

### 1\. Add a voting status in the proposals page

The counter in the right corner of a space shows the number of proposals that have recently entered into the active state, so I guess it’s not possible to make them disappear once a voter casts all the existing votes.

However, is it possible to doing a workaround by adding a voter’s voting record at the bottom of **an active proposal item**, just like the “majority choice“ of a closed proposal, indicating that the user has voted this proposal. It can simply be a similar version of what’s inside the proposals votes list.

It will be of a great help since we often encounter situations where we have to load a series of proposals at consecutive intervals, and members may forget to pick each one of them or double vote on the same proposal since they can’t just remember each of their voting behavior in such situations. By enabling this improvents, people won’t need to click in to check their status, this helps much in governance efficiency.

![](https://storage.googleapis.com/papyrus_images/fbb9f68f0c5c3a2083f1c7109dbcb45f68ab0c69dabfa340e295348b0ecf2dd4.png)

### 2\. Default starting time to “Now” when duplicating a proposal

In most cases, we don’t duplicate a proposal simply because of a typo or something like that. Rather, it’s when we find a mistake in our strategy or the proposal doesn’t meet our quorum due to special reasons, we have to do so since once the proposal is posted, it becomes immutable and we can’t revoke it.

Most importantly, the snapshot of the proposal is based on the creation time of itself, not the starting time we set. It doesn’t make a lot of sense that the duplicated proposal still inherits the previous one, especially a very old one with which date we will just **post a closed state** **of proposal** at the current time.

![](https://storage.googleapis.com/papyrus_images/55715c58295f73c1cb960376a123177f79ad0eedc1267024bc9970239a891411.png)

### 3\. Unify the interaction dynamics on the creation process

It’s a typical thing mentioned by our authors, that sometimes they just cannot find the “Back“ button to navigate to the last page.

We found out that most likely it’s because of **the inconsistency** of the backward logic.

The current creation process is split into 2 pages: the main body of proposal, and the Choice form. While the interface has a different logic in these 2 consecutive pages, it can create kind of loss in user’s consciousness.

In my humble opinion, we should **add the “←Back“ button** to each of the creation page to bridge that inconsistency.

![Inconsistency: Proposal Form](https://storage.googleapis.com/papyrus_images/38e2401bfbcd12e97fb7244df688c8b0a06d751d1abc21e119cd9e6ec70a15ec.png)

Inconsistency: Proposal Form

![Inconsistency: Choice Form](https://storage.googleapis.com/papyrus_images/0d4858f6c14b34ff2495512c94cdec9cb707a5b5c55988ba44f7243c6c72cac5.png)

Inconsistency: Choice Form

### 4\. Integrate notification bells into one within the app

I noticed that Snapshot now has a full list of notification methods we can choose from: HAL, discord bot, epns, webhooks… The notification bell within the space page seems a little outdated, and our members are often confused at what these two bells represent for respectively.

It spent me a while to get to understand that they actually control different ways of notification, but this also creates a sort of fragmentation within UI. Imagining one wants to turn off notification messages from a specific space he joins in the upper right dropdown list, there’s no way to do so, and the bell below the space name won’t work either, but to switch to another notifiation type.

IMHO, we can make this page much neater by **integrating** the left notication bell with the newer one, and after that it will only point to one type of notification where user can actually control to accept a specific range of space messages.

![two similar bells](https://storage.googleapis.com/papyrus_images/60994f8ef97c009f5ca26b5bc0ff5b4e5890a4cb2279e5396af906365bcaafd2.png)

two similar bells

### 5\. Highlight voting types

Pastachiodao is a very good example that I use it every time when I try to teach new members who are going to cast their first votes.

But sometimes when new members flood in, it’s inevitable someone doesn’t fully comprehend the meaning of the voting system or just neglect the voting type the proposal is using since it’s just placed in the upper right corner of the page.

I’m thinking of a way just like what Pastachiodao did. But differently I want the ‘‘demo’’ directly embedded within a proposal in the simple form like **a short explained hint**, to remind the users which voting type they are acting on, to let them know they can actually choose one more options in an “approval voting” type. I can’t help thinking it because it would be a great attempt to further ‘‘educate’’ our users the knowledge of snapshot in a very practical way.

It can be in the choice form section **beside ‘“cast your vote“**, indicating a voting type.

![a hint beside "Cast your vote"](https://storage.googleapis.com/papyrus_images/2acb32039c1594a7674ead7ec4f1c9da65aa9df0ce4a8da6876a96787812345c.png)

a hint beside "Cast your vote"

### 6\. Make visible the bottom bar in the homepage

The bottom bar provides essential information like official contact, display mode, language setting and official tutorials.

These elements are highly useful and should be **available at anytime** at least in the homepage. (experience from other well-known projects)

However, if one hits the “load more” button, it just keeps loading down forever until all spaces will show up, and the bottom bar containing these information just keep **“blipping“** on each loading. One has to refresh the page to get it back to the original state.

To keep the bottom bar at a certain visibility level, I can think of 3 options:

1.  Pin the bottom bar like “freeze panes” in an excel, so loading will not break its existence.
    
2.  Add a load limit, like 50 spaces/load, after that, one has to retrigger the load manually.
    
3.  Keep it as it was. But after one hits the “load more” button and the load starts looping, one will be able to return back the state by hitting “snapshot“ in the top bar or “⚡“ in the sidebar.
    

![Blip on each "load more"...](https://storage.googleapis.com/papyrus_images/fbf82fbbb40fbd0290e0cf025d0cc90744363b4b2846407d3cf967b0d586d46d.png)

Blip on each "load more"...

### 7\. Optimize the experience of edit box

We usually tweak our strategies in the UI, its original edit box. But the experience is not good, especially for a long code, every time an input will **bring the whole page to the top**, again and again, it brings us headache since we just **lost** where we were in the middle of job. I believe the issue also happens in any edit box like a plugin modal, or the playground…

![](https://storage.googleapis.com/papyrus_images/a9d04073ec5cb9fa51fa107f8b40303018d8b8045ff9dbb490320c944dafb6e6.png)

### 8\. Strategy reuse

For different proposal types, we have different strategies to apply.

We know snapshot doesn’t allow the author to choose arbitrary strategies at his will. We successfully manage it at the admin level, to centralize the use of strategies.

But as such, we’re also considering for a DAO which has a pool of 10 strategies (and we use it on rotation like 3-4 strategies a time), if we can make things more efficient by keeping those **strategies temporarily not in use** in an “**inactive state”** rather than just deleting them and re-adding them back when it comes to use again?

Therefore we don’t bother to write them again and can bring them back with just a click, which provides much more flexibility.

![Adding a disable button besides delete?](https://storage.googleapis.com/papyrus_images/2962b3b72bf78726bd7b3d1e80e07b692b176dd9ad682503e1eca35e09816c28.png)

Adding a disable button besides delete?

### 9\. Preserve the input state of the keywords on strategies section

The number of snapshot’s strategies is exploding, which is good! However sometimes we can hardly tell the exact function of a strategy by its name and have to click in and run a test one by one.

It’s somewhat inconvenient when we click the return button, and it brings us to the whole list of strategy after we find out it’s not our strategy, we have to **input the keywords again** to filter to the target lists.

I wish the app can remember the state of our input keywords when we return to the page.

![](https://storage.googleapis.com/papyrus_images/391b5e179242def7d1f526f20b4064b119b33bb568fc469805f66440bdad81d9.png)

### 10\. Bridge between strategy settings and playground

This initiative is supposed to leverage the playground feature (a test environment for strategies)

Many users don’t know there is a strategy playground where they can utilize to test strategies before put into real use. This approach can save a lot of effort from creating a whole test space. All we need is some visual guidance to nagivate users to notice this feature, it also brings benefits for it will bring them to the strategy page which explains to them how this strategy works. (If there’s a README file)

I think snapshot can put an icon (or any like) that links to the playground for each strategy in settings, for the “settings” will always be the first experience a user has with snapshot. It makes sense to do such inbuilt navigation.

![somewhere in strategy settings can be added with brief instruction(hovertips) or an icon link to playground](https://storage.googleapis.com/papyrus_images/c376cf4fe4662bef797b9a4050eed35437ed98037ddb86b0a04a9c3339bf5628.png)

somewhere in strategy settings can be added with brief instruction(hovertips) or an icon link to playground

---

*Originally published on [Lenson](https://paragraph.com/@lenson/ui-feedback)*